Skip to content

v22.0 Gate 0 Wait Maintenance Bundle

Summary

This archive records a bounded maintenance bundle completed while v22.0 Gate 0 remained blocked on user-owned legal and partner evidence.

The work stayed inside the "parallel maintenance while Gate 0 waits" lane and focused on repo-local quality, governance enforcement, and documentation alignment rather than new pilot-facing scope.

Completed Outcomes

  1. Closed the public search explainability follow-through:
  2. added normalized, deduplicated match-reason handling
  3. surfaced match reasons on result cards
  4. preserved match reasons into linked detail pages
  5. Enforced stale-data runtime governance:
  6. local and server search now exclude records beyond the 180-day visibility window
  7. freshness badges now distinguish expired records
  8. direct-linked detail pages now show an explicit stale-record warning when the listing is outside the governance window
  9. Reconciled active CI/runtime docs with the live workflow stack:
  10. release docs now use gh release create
  11. load-testing docs now reference current GitHub Action majors and Node 22
  12. documentation hygiene coverage now guards those active references
  13. Calibrated active governance/planning docs for a solo-operable operating model:
  14. 180 days is the hard visibility cutoff
  15. 90 days is the target re-verification window for pilot / priority services
  16. the v22 90-day cycle is documented as a dependency-contingent decision checkpoint rather than a guaranteed build schedule
  17. Added focused automated coverage for:
  18. match-reason normalization and routing
  19. stale-data filtering in local search and the search API
  20. freshness helper behavior and expired UI states
  21. active documentation alignment around workflow/runtime and freshness policy

Canonical References Updated

  1. Roadmap
  2. Architecture
  3. Governance Standards
  4. Verification Protocol
  5. Planning README
  6. Project README
  7. Docs Index
  8. Testing Guidelines

Verification Snapshot

Validated during the 2026-04-05 maintenance pass:

  1. npm test -- --run tests/lib/freshness.test.ts tests/lib/search/index.test.ts tests/api/v1/search-api.test.ts tests/components/services/ServiceDetailPage.test.tsx tests/components/ui/FreshnessBadge.test.tsx
  2. npm test -- --run tests/components/ServiceCard.test.tsx tests/components/services/ServiceDetailPage.test.tsx tests/lib/search/match-reasons.test.ts
  3. npm test -- --run tests/unit/documentation-hygiene.test.ts
  4. npm run ci:check

What Remains Open

This archive does not unblock v22.0 Gate 0 or close the remaining bounded maintenance backlog.

Still-open follow-through remains on the main roadmap:

  1. A1 Gate 0 partner/legal evidence closure
  2. bounded A6 / A16 pilot-readiness follow-through based on real evidence inputs
  3. client/server ranking unification behind a shared scoring engine
  4. Docker-capable regeneration of types/supabase.ts plus the remaining typed notification_audit path cleanup