egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
5b358d71c1bd2344ec57c0c50c65c69cf42893de
DashBoard/docs/migration/full-modernization-architecture-blueprint/observability_checkpoints.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

924 B
Raw Blame History

Modernization Observability Checkpoints

Route Governance Signals

  1. navigation_contract_mismatch_total
  • Source: /api/portal/navigation diagnostics.
  • Alert condition: non-zero for in-scope routes.
  1. route_contract_missing_metadata_total
  • Source: route governance CI script.
  • Alert condition: >0 in block mode.

Quality Gate Signals

  1. quality_gate_failed_total{gate_id}
  • Source: quality gate report.
  • Alert condition: any mandatory gate failed.
  1. manual_acceptance_pending_routes
  • Source: manual acceptance records.
  • Alert condition: cutover attempted with pending sign-off.

Fallback and Rollback Signals

  1. in_scope_runtime_fallback_served_total
  • Should remain zero after fallback retirement milestone.
  1. content_cutover_flag_rollbacks_total
  • Track frequency and route impact.
  1. legacy_bug_replay_failures_total
  • Any non-zero indicates carry-over risk and blocks sign-off.