Keep route-separated workflow state synchronized

Route-separated multi-step workflows should derive the visible step labels, completed/current state, page heading, document title, and active navigation tab from one route-mode model. This applies when a single user task spans multiple pages or hash/query submodes: matching labels alone can still leave the interface contradictory. The method is to define one canonical step order, map each route mode to presentation state, add structural tests for order and accessible state, then run a real-browser smoke test because DOM unit fixtures can miss page-shell inconsistencies. Its limit is that presentation synchronization does not validate backend persistence or cross-route draft restoration; those need separate behavioral checks.

Evidence/example — 2026-09-09

In ender-inference PR #173 for COR-4113, automated workflow tests passed while a manager browser smoke test still found the creation route showing the history heading and active tab. Adding a route presentation synchronizer plus assertions for heading, description, document title, and aria-current fixed the inconsistency. The full suite passed (2166 passed, 5 skipped), deployment workflow run 34316623574 succeeded, and live staging verification confirmed the synchronized state.

Source provenance: GitHub PR https://github.com/e3-solutions/ender-inference/pull/173 and Linear COR-4113.