egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
c38b5f646a46239b1701cac82a6ab30463088336
DashBoard/docs/migration/deferred-route-modernization-follow-up/pre_change_confirmation_template.md
egg c38b5f646a feat(modernization): promote deferred routes to in-scope and unify page header styles 
Promote /tables, /excel-query, /query-tool, /mid-section-defect from
deferred to full shell-governed in-scope routes with canonical redirects,
content contracts, governance artifacts, and updated CI gates.

Unify all page header gradients to #667eea → #764ba2 and h1 font-size
to 24px for visual consistency across all dashboard pages. Remove
Native Route-View dev annotations from job-query, excel-query, and
query-tool headers.

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

1.6 KiB
Raw Blame History

Pre-Change Confirmation Template (Deferred Route)

Rule

Before any implementation work begins on a deferred route, a route-scoped pre-change confirmation MUST be recorded and approved. Implementation is BLOCKED until confirmation exists.

Required Fields

  1. Route: The deferred route path (e.g., /tables).
  2. Status Snapshot: Current route status in page registry (e.g., dev, released).
  3. Scope Boundary Check: Confirmation that the route is listed in route_scope_matrix.json as in-scope for this change.
  4. Contract Baseline Refs: References to existing route contracts and content contracts that define expected behavior.
  5. Known-Bug Baseline Ref: Reference to known_bug_baseline.json entry for this route (or confirmation that baseline is initialized).
  6. Rollback Flag Plan: Planned feature flag key and rollback strategy for this route's cutover.
  7. Owner: The person/team responsible for this route's modernization.
  8. Date: Date of confirmation.
  9. Approved By: Reviewer who approved the pre-change confirmation.

Template

Route: /<route-name>
Status Snapshot: <dev|released>
Scope Boundary Check: confirmed in route_scope_matrix.json as in-scope
Contract Baseline Refs:
  - Route contract: route_contracts.json#/<route-name>
  - Content contract: route_content_contracts.json#/<route-name>
Known-Bug Baseline Ref: known_bug_baseline.json#/<route-name>
Rollback Flag Plan:
  - Feature flag: modernization_feature_flags.json#/<route-name>.content_cutover_enabled
  - Rollback strategy: fallback_to_legacy_route
Owner: <owner>
Date: <YYYY-MM-DD>
Approved By: <reviewer>