7cb0985b12
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>
1.6 KiB
1.6 KiB
MODIFIED Requirements
Requirement: Major Pages SHALL be Managed by Vite Modules
The system SHALL provide Vite-managed module entries for all in-scope modernization routes under shell-first governance, including admin surfaces /admin/pages and /admin/performance as governed targets. Deferred routes (/tables, /excel-query, /query-tool, /mid-section-defect) are excluded from this phase's required module-governance completeness.
Scenario: In-scope module governance completeness
- WHEN modernization route coverage is validated for this phase
- THEN every in-scope route SHALL have deterministic module-governance metadata and ownership mapping
Scenario: Deferred route exclusion in this phase
- WHEN completeness validation executes for this phase
- THEN deferred routes SHALL be excluded from mandatory pass criteria
Requirement: Build Pipeline SHALL Produce Backend-Served Assets
Vite build output for in-scope modernization routes MUST be emitted into backend static paths and validated at release time. Missing required in-scope assets SHALL fail release gates instead of relying on runtime fallback behavior.
Scenario: Build artifact readiness for in-scope routes
- WHEN frontend build is executed for release
- THEN required in-scope route artifacts SHALL be present in configured backend static dist paths
- THEN missing required artifacts SHALL fail readiness checks
Scenario: Deferred route fallback posture unchanged in this phase
- WHEN deferred routes are evaluated in this phase
- THEN existing fallback posture SHALL not block this phase's completion