egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
7cb0985b1228dcb69f33c865827658605a843cac
DashBoard/docs/migration/full-modernization-architecture-blueprint/governance_milestones.md
egg 7cb0985b12 feat(modernization): full architecture blueprint with hardening follow-up 
Implement phased modernization infrastructure for transitioning from
multi-page legacy routing to SPA portal-shell architecture, plus
post-delivery hardening fixes for policy loading, fallback consistency,
and governance drift detection.

Key changes:
- Add route contract enrichment with scope/visibility/compatibility policies
- Canonical 302 redirects from legacy direct-entry to /portal-shell/ routes
- Asset readiness enforcement and runtime fallback retirement for in-scope routes
- Shared feature-flag helpers (env > config > default) replacing duplicated _to_bool
- Defensive copy for lru_cached policy payloads preventing mutation corruption
- Unified retired-fallback response helper across app and blueprint routes
- Frontend/backend route-contract cross-validation in governance gates
- Shell CSS token fallback values for routes rendered outside shell scope
- Local-safe .env.example defaults with production recommendation comments
- Legacy contract fallback warning logging and single-hop redirect optimization

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 11:26:02 +08:00

1.5 KiB
Raw Blame History

Full Modernization Governance Milestones

Phase Completion Criteria

A phase is complete only when all criteria below are true:

  1. Route governance: 100% of in-scope routes in route_scope_matrix.json have valid shell contract metadata and ownership.
  2. Style governance: in-scope route-local styles do not introduce page-global selectors (:root, body) unless recorded in exception registry.
  3. Quality governance: functional parity, visual checkpoints, accessibility checks, and performance budgets pass at configured gate severity.
  4. Content safety governance: page-content parity evidence + manual acceptance sign-off exist for each migrated in-scope route.
  5. Bug carry-over governance: known-bug replay checks for migrated scope do not reproduce legacy defects.

Legacy Deprecation Milestones

  • 2026-02-20: route contract CI completeness gate enabled in warn mode.
  • 2026-02-27: route contract CI completeness gate promoted to block mode.
  • 2026-03-05: in-scope asset readiness gate promoted to block mode.
  • 2026-03-12: runtime fallback posture retired for in-scope routes in production policy.
  • 2026-03-19: unresolved style exceptions past milestone fail modernization review.

Deferred Route Linkage

Deferred routes are not pass/fail criteria in this phase and are handed over to a follow-up change:

  • /tables
  • /excel-query
  • /query-tool
  • /mid-section-defect

Follow-up change handoff is recorded in openspec/changes/deferred-route-modernization-follow-up/.