egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
7cb0985b1228dcb69f33c865827658605a843cac
DashBoard/openspec/changes/archive/2026-02-12-modernization-hardening-follow-up/specs/unified-shell-route-coverage/spec.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.2 KiB
Raw Blame History

ADDED Requirements

Requirement: Frontend and backend route-contract inventories SHALL be cross-validated

Route-governance checks SHALL verify that frontend shell route contracts and backend route contract artifacts describe the same governed route set and scope classes.

Scenario: Cross-source contract parity gate

  • WHEN modernization governance checks run in CI
  • THEN mismatches between backend route contract JSON and frontend routeContracts.js route inventory SHALL fail the gate

Scenario: Scope classification drift detection

  • WHEN a route has inconsistent scope classification between frontend and backend contract sources
  • THEN governance checks SHALL report the specific route and conflicting scope values

Requirement: Legacy contract-source fallback SHALL emit operational warning

When contract loading falls back from the primary modernization contract artifact to a legacy artifact path, the service SHALL emit explicit warning telemetry.

Scenario: Legacy contract fallback path selected

  • WHEN the primary contract artifact is unavailable and a legacy contract file is loaded
  • THEN the system SHALL log a warning that includes the selected legacy source path