fix(ui): reconcile shared accessibility and read recovery

This commit is contained in:
cesnimda
2026-10-20 20:26:48 +02:00
parent bba52af4b8
commit d8c0187305
25 changed files with 802 additions and 25 deletions
+30
View File
@@ -0,0 +1,30 @@
# P7-11 — Residual integration
Entry: P7-10 System `d824f59d2b3e9b680bee5952802aa3c0453aee03`, normally pushed/directly verified with a clean checkout20October13:40:25UTC. CI-only main continuation was merged and pushed as `6db62095c6dc6f7e8275447827c62b09f9b2d2e3`, clean13:40:41UTC. The approved handoff requires responsible-owner repairs, not another migration of completed pages.
## Recorded baseline and bounded owners
| Finding | Impact / responsible boundary |
|---|---|
| Roleless version badge and disabled-control tooltip spans carry unsupported names | Accessibility; shared shell, Checklist and Interview owners |
| Add Job and Strategy headings skip semantic levels | Accessibility; existing form owners |
| Strategy GET failures become an apparent absent plan | Usability; existing Match-tab Strategy read owner; exact `strategy_not_generated` remains intentional emptiness |
| Known template, generated reason/tailoring and history metadata remain English in Bokmål | Localisation; existing gallery/reminder/application/history owners; user and unknown metadata remain verbatim |
| Resumed-draft fallback freezes opening language; singular counts use plural English | Localisation; existing correspondence presentation without draft/save protocol changes |
| CV private-source failures show raw `Not Found`, lack contextual heading and read retry | Usability; existing CV entry owner, private identifiers and server authorization unchanged |
| Unknown route has generic shell title and h4 owner heading | Accessibility/context; existing wildcard route, Home and Back actions retained |
| Documents action splits the last letter at1024px | Responsive usability; existing table and action sizing, metadata/query/download contracts unchanged |
These findings were carried from implemented checkpoints and verified in source, unit regressions and/or browser reproduction. Cosmetic preferences are not additional scope. Analytics already uses the approved DashboardView report owner; it is reused with unchanged periods, cohorts, source links and statistics. Shared loading/feedback and existing confirmations remain; no duplicate framework is introduced.
## Execution boundaries
1. [Shared accessibility and forms](SHARED.md), including the paired translation foundation used by the following owners.
2. Generated-label localisation follows separately, preserving all stored metadata and user text.
3. Documents and error navigation follows separately, including CV history display in its existing owner.
The independently authorized release repair is separate: development `bba52af4b8724f1a5c74013ce1476a20ca3972c2` was pushed/directly verified18:05:08UTC. Main contains equivalent fixture/focus repair `3e1057d` and Qwen compatibility `f7dc22e`, normally pushed and directly verified20October18:05UTC. Run833 is testing; deployment/model activation are unverified. [Release evidence](../../../infrastructure/2026-10-20-browser-fixture-and-focus-contracts.md) retains run832's314passing/16failed/oneflaky outcome and the two demonstrated causes. No failed assertion was hidden or timeout relaxed.
## Acceptance boundaries
P7-11 implementation and publication are in progress. Full integrated acceptance belongs to P7-12. All57 preservation groups retain56 PARTIAL/C11 DEFERRED and33 routes; no capability or route is removed. Manual reader/device/software-keyboard/zoom, production output/provider, reliability and release requirements remain. P5-13 stays withheld; followMode remains deferred. No Phase8 implementation or new dashboard customization. Production readiness remains NO-GO independently of the owner's authorization to release main.