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/frontend-platform-modernization-governance/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.3 KiB
Raw Blame History

ADDED Requirements

Requirement: Operator-facing environment defaults SHALL be onboarding-safe

.env.example SHALL prioritize local onboarding safety while clearly documenting production hardening recommendations for modernization controls.

Scenario: Local bootstrap from .env.example

  • WHEN a developer initializes .env from .env.example in a local non-production environment
  • THEN startup-critical modernization flags SHALL default to onboarding-safe values that do not fail boot solely because dist readiness gates are strict by default

Scenario: Production recommendation visibility

  • WHEN operators review .env.example for deployment configuration
  • THEN production-recommended values for shell-first and modernization-hardening flags SHALL be explicitly documented in adjacent comments

Requirement: Policy cache refresh model SHALL be explicit in governance docs

Governance-owned policy artifacts that are loaded with in-process caching SHALL document runtime refresh behavior and operator expectations.

Scenario: Cached policy artifact behavior documentation

  • WHEN maintainers read modernization governance artifacts
  • THEN they SHALL find explicit guidance on whether policy JSON updates require process restart, cache clear, or automatic reload