feat: wire WP1–WP5 routers into appRouter + schema declarations (integration)

[munisp]

What

Integration commit wiring the WP1–WP5 feature routers (merged in #154–#158) into appRouter and adding the matching Drizzle schema declarations. Only server/routers.ts and drizzle/schema.ts are touched (the stale repo-root routers.ts was NOT modified).

Per-WP registrations

• WP1 (entity search, feat: unified entity search + related-persons graph #154)
  • import { entitySearchRouter } from "./entitySearch";
  • entitySearch: entitySearchRouter, in appRouter
• WP2 (ongoing monitoring, feat: ongoing monitoring engine (continuous re-screening + alerts) #158)
  • import { monitoringRouter } from "./monitoring";
  • monitoring: monitoringRouter, in appRouter
• WP3 (subject portal, feat: subject portal + consumer self-check #155)
  • Imports: subjectPortalRouter from ./subjectPortal, computeDataCompleteness from ./dataCompleteness
  • subjectPortal: subjectPortalRouter, in appRouter
  • Deleted the routers.ts-local getFallbackSuggestion (now lives in server/dataCompleteness.ts — anti-drift)
  • investigations.getDataCompleteness now delegates to computeDataCompleteness(db, input.investigationRef)
  • drizzle/schema.ts: consentPurposeEnum gains "consumer_self_check"; appended subjectAccessTokenPurposeEnum/subjectAccessTokens/subjectDisputeStatusEnum/subjectDisputes declarations (verbatim from PR feat: subject portal + consumer self-check #155 body; match drizzle/0023_subject_portal.sql)
• WP4 (shareable reports + self-service billing, feat: shareable reports + self-service subscriptions #157)
  • Imports: shareableReportsRouter from ./shareableReports, selfServiceBillingRouter from ./selfServiceBilling
  • shareableReports: shareableReportsRouter, + selfServiceBilling: selfServiceBillingRouter, in appRouter
  • drizzle/schema.ts: appended reportShareLinks/planSignups pgTable declarations (verbatim from PR feat: shareable reports + self-service subscriptions #157 body; match drizzle/0024_share_links_and_plan_signups.sql)
• WP5 (reverse phone lookup, feat: reverse phone lookup (provider-adapter, fail-closed) #156)
  • lookup.phone procedure inserted after lookup.cac, using the in-scope gatewayFetch helper (verified — same helper used by cac/nin/bvn): input z.string().min(7).max(20).regex(/^\+?[0-9][0-9\s\-().]*$/), gateway path /v1/phone/:number (URI-encoded)

All patches applied via anchored exact-string replacement (each anchor verified unique before replacing); all 9 patches reported OK.

Verification (real output)

Sanity checks:

entitySearchRouter: 2        (import + registration)
monitoringRouter: 2
subjectPortalRouter: 2
shareableReportsRouter: 2
selfServiceBillingRouter: 2
getFallbackSuggestion in server/routers.ts: 0
drizzle/schema.ts: consumer_self_check @2235, subjectAccessTokens @3705, subjectDisputes @3725, reportShareLinks @3749, planSignups (appended)

Typecheck:

$ npx tsc --noEmit
TSC_EXIT=0

WP test files:

$ npx vitest run server/monitoring.test.ts server/share-subscribe.test.ts server/composePorts.test.ts server/subject-portal.test.ts server/entity-search.test.ts server/lookup-phone.test.ts
 ✓ server/share-subscribe.test.ts (19 tests)
 ✓ server/monitoring.test.ts (24 tests)
 ✓ server/subject-portal.test.ts (19 tests)
 ✓ server/entity-search.test.ts (37 tests)
 ✓ server/composePorts.test.ts (7 tests)
 ✓ server/lookup-phone.test.ts (4 tests)
 Test Files  6 passed (6)
      Tests  110 passed (110)

Registration smoke + regression:

$ npx vitest run server/smoke.comprehensive.test.ts server/aml.securityGuard.test.ts server/next-steps.test.ts
 ✓ "All domain routers are registered in appRouter" PASSED
 Test Files  1 failed | 2 passed (3)
      Tests  1 failed | 317 passed (318)

The single failure (smoke.comprehensive › creditTenantAccount rejects an unbound legacy reference when TIGERBEETLE_URL is not set — needs BIS_DATABASE_URL) was reproduced identically on pristine main (verified by stashing this branch's changes and re-running that test) — pre-existing and unrelated, as documented in #155/#157.

Notes

• No stubs/placeholders; no changes to any feature file — integration-only.
• Migration SQL (0023/0024/0025) already on main; schema declarations match it exactly (column-for-column verified against drizzle/0023_subject_portal.sql and drizzle/0024_share_links_and_plan_signups.sql).