Make the health endpoint factory and registry aware

[Caneryy]

Planning

• Plan ID: N4
• Depends on: Consolidate the three community registry models into one adapter #248 (H2), Centralize network and deployment capability configuration #254 (H8), Extend the testnet deploy script to deploy and configure CommunityFactory #259 (N3)
• PRD alignment: FR-2, FR-6; UJ-1, UJ-4

Problem

/api/health checks legacy global NFT/Governor configuration but not the CommunityFactory or registry read path that powers the current product.

Scope

Report separate configuration and read-probe results for RPC, CommunityFactory, registry listing, and optional legacy contracts. Keep the response credential-safe and backward compatible at the top-level healthy field.

Acceptance criteria

• Missing factory config is distinguishable from RPC and registry-read failures.
• A healthy response proves that at least the registry interface is readable.
• Logs and JSON never expose query strings, credentials, or full wallet addresses.
• Route and scheduled health-check tests cover healthy, degraded, and unhealthy responses.

Verification

npm test && npm run typecheck

[Santia2004]

Hi team! I’d love to work on this issue. I have solid experience with the tech stack, understand the requirements, and can deliver a clean implementation with full test coverage following your project guidelines. Could you please assign this to me? Thanks!