jobtrackingapp/docs/redesign/phase-5/p5-15/README.md

P5-15 — Phase 5 final acceptance

Current final scoped acceptance — P5-15-06

The owner's latest instruction authorises continuous bounded repairs and independent acceptance work through Phase 6 preparation; earlier checkpoint stop instructions remain historical. Native file selection, hidden preview layout, drawer focus, source navigation and report targets are separately repaired, validated and pushed. Their original 02 failures are retained, not relabeled as passes. CV/document qualification is conditional for its measured local scope. Final regression and decision: backend1,033/frontend498/browser148/diagnostics3, sidecar49/focusedAI108/HTTP2/revision5, standard16/16(36=36), settings8/8(24=24), security/config9/6/1/3 and static/build/hygiene gates pass fresh after the last application change.

Implemented scope: CONDITIONAL GO for Phase 6 review planning. Full originally planned Phase 5: NOT COMPLETE. Production: NO-GO. Fresh312axe scans retain39all-enabled violation-node occurrences and2,367incomplete occurrences; automated success is not full accessibility acceptance. Targeted debt disposition retains contextual rule warnings, historical preference500 causes, the CV Unsaved incident and O(N) Board capacity. Twelve concurrent preference rounds and exact200/1,000-job Board membership pass locally without closing those production/manual obligations. Commit ledger records independently pushed units; no production action follows.

Phase6 review planning now uses final acceptance baseline 9528504866054da10e20d5196e65de536c4c9499, retaining conditional implemented scope, original scope NOT COMPLETE and production NO-GO. Next review checkpoint: P6-01. No Phase7 migration or P5-13 activation begins.

The 57-group matrix now records 0 PASS / 56 PARTIAL / 0 FAIL / 1 DEFERRED =57. Whole-group acceptance remains incomplete. Postponed human screen-reader acceptance is NOT COMPLETE / NOT VERIFIED; physical devices/software keyboards, incomplete axe triage and deployed font/portrait qualification remain open. P5-13 remains deferred/unqualified/Production-withheld, 0/366 calls, no human semantic review or review UI. P5-05 and followMode reviewed compose remain explicitly deferred.

Production assessment: NO-GO, main unchanged. F04, current complete backup/isolated restore, deployed configuration/schema/secrets, rollback and smoke/monitoring evidence are still required. Phase 6 planning does not waive them or declare the original full Phase 5 scope complete.

Historical P5-15-02 — Responsive/accessibility audit successor

Owner update —2026-10-10: screen-reader operator testing will be revisited later. It is logged as NOT COMPLETE / NOT VERIFIED in the manual packet, with mandatory acceptance retained. This scheduling decision does not change the audit NO-GO, production NO-GO or57-group preservation totals.

02 audit, native coverage, findings, reflow measurements and manual packet now supersede the prior “02 not started” statements. Application/API/renderer behavior is unchanged. Actual Chromium100/200/400 zoom is measured separately from touch emulation, screen-reader speech and physical-device/software-keyboard acceptance. Owner reports a reader operator available; actual results remain NOT VERIFIED until supplied.

P5-15-02: NO-GO for P5-15-03 on confirmed P1 keyboard upload/import failure and initial mobile CV content clipping. That fixture's page count matches its PDF, but its visible content flow remains zero-width; no false page-count claim is made. Reduced-motion drawer return, source-editor404 and small report targets also need bounded disposition. 57-group matrix now reconciles 0PASS/50PARTIAL/6FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED while retaining every historical status column. Separate UI-rule warnings/manual gaps are not automatically failures. Known failures are neither skipped nor expected-failing.

Fresh complete results: backend1,033 / frontend490 / main browser139pass+4fail across143cases, plus the separately added native mobile/PDF diagnostic 0pass+1fail; unique ordinary union 139pass+5fail=144, not one144-case full execution. All134 inherited browser cases pass, including saved searches, Rules and AUTH-01. Separate diagnostics2, realHTTP2, sidecar49, focusedAI108, revision5/5, standard fidelity16/16(36=36), settings8/8(24=24), security/config9/6/1/3 and static/build/hygiene checks pass. The finite renderer corpus does not qualify the failed hidden mobile visible-page lifecycle. Final evidence preserves command/results and the ordinary failures.

Fresh 312axe scans comprise267retained-rule scans(0reported violations,2,038incomplete nodes) and45all-enabled/target-size scans(47violation-node occurrences,374incompletes). Per-rule triage separates repeated nodes, best-practice warnings, confirmed native defects and required human review. Actual Chromium200/400zoom adds bounded geometry evidence; no spoken reader/physical-touch/software-keyboard acceptance is claimed. CV Unsaved intermittence remains OPEN. Completed logical checkpoints are individually committed/pushed; no application repairs are hidden in this audit.

P5-13 remains deferred/unqualified/Production-withheld0/366,0human semantic reviews, UI unimplemented. Production main remains unchanged/NO-GO; F04, current complete backup/tested restore, configuration/schema/secrets, rollback and deployed acceptance remain open. No automatic P5-15-03/04, P5-13, B07 or deployment follows from this audit.

Historical P5-15-01R-03 — Bounded Analytics authentication successor

Analytics authentication repair closes AUTH-01 for the verified full internal return-path/security scope. The unchanged original failure is RED→GREEN; native period/encoding/history/expiry/logout/foreign-resource/tampering journeys pass. The reproducer c37cab560afa2d94cc4244c09dfa7aa720563bbf and bounded implementation 68437671762aa9a4d93036a23a06810f1f47dd57 are separately committed and pushed. R-03: GO for the bounded repair, with final documentation/hygiene evidence in its own immediate commit/push checkpoint. Original audit findings and earlier repair results remain historical.

Fresh complete results: backend1,033 / frontend490(+18) / ordinary browser134pass,0fail / separate diagnostics2pass,0fail. Five browser cases are added; the former AUTH-01 failure becomes an actual pass. All117 inherited cases, five audit cases, three saved-search and four Rules repair cases pass; P2-D01 stays ordinary passing. Sidecar49, focusedAI108, realHTTP2, revision5/5, standard fidelity16/16(36=36), settings8/8(24=24), security/config9/6/1/3, TypeScript, lint and both builds pass. Portable results distinguish subsets and retained RED/harness attempts. Full267axe scans report0violations and2,041incomplete node occurrences; manual accessibility is not accepted.

PRES-E02 moves FAIL→PARTIAL; all57 groups are 0PASS/56PARTIAL/0FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED. No incomplete whole group is promoted to PASS. All three originally reproduced functional defects have scoped repair proof, while provider/human/device and recorded debt remain open. The CV intermittent observation is still OPEN. Production main remains unchanged and NO-GO; P5-15-02 is not started and needs a separate owner instruction. P5-13 stays deferred/unqualified/Production-withheld with0/366 calls,0human reviews and no review UI. F04/current backup-restore/configuration-schema-secrets/tested rollback remain release blockers.

Historical P5-15-01R-02 — Bounded Rules successor

Rules draft repair and native evidence closes SETTINGS-01 for verified internal session retention, Save/readback, validation, failure/retry, Discard and account disposal. PRES-S03 moves FAIL→PARTIAL; current57 totals are 0PASS/55PARTIAL/1FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED. AUTH-01 Analytics query loss remains open/failing. The prior audit/R-01 records below remain historical; other Settings reliability and human/provider acceptance remain open.

Completed repair commit 30f513d0c993800ec5d5583329ed65dc7ec9a8d4 is independently pushed. R-02: GO for the bounded Rules repair. Fresh backend1,033 / frontend472(+8) / ordinary browser128pass+1fail(+4cases) / standalone diagnostics2pass+0fail. All117inherited, four Rules and three saved-search repair browser cases pass; AUTH-01 remains the one ordinary failure. Sidecar49, focusedAI108, realHTTP2, revision5, standard fidelity16/16(36=36), settings exports8/8(24=24) and security/config9/6/1/3 pass. Exact results and limits distinguish subsets and local proof. Full267axe scans have0reported violations and2,040incomplete node occurrences; human/device acceptance remains open. Intermittent CV observation remains OPEN despite fresh passing frontend/native runs. Final documentation/repository check evidence is retained with the repair.

Production remains NO-GO; main unchanged. P5-15-02 is neither started nor cleared. No Analytics, P5-13, Docker, B07 or deployment work. P5-13 remains deferred/unqualified/Production-withheld:0/366qualification calls,0human reviews, no review UI.

Historical P5-15-01R-01 — Saved-search successor

Saved-search repair and evidence resolves the native SQLite GET500 and hidden error. PRES-J02 moves FAIL→PARTIAL; totals at R-01 were 0PASS/54PARTIAL/2FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED. The01 audit remains historical below. AUTH-01 Analytics query loss and SETTINGS-01 Rules draft loss remained open/failing at R-01; no automatic P2 repair or P5-15-02 progression was authorized. Production remains NO-GO; main is unchanged. P5-13 stays deferred/unqualified/Production-withheld with0/366calls,0human reviews and no review UI.

R-01 fresh results: backend1,033 / frontend464 / ordinary browser124pass+1fail / separate diagnostics1pass+1fail. All117 inherited browser cases pass; three new repair cases pass and the original normal/admin saved-search failures are resolved. Sidecar49, focusedAI108, realHTTP2, revision5, fidelity16/16(36=36), settings8/8(24=24) and security/config9/6/1/3 pass. Fresh251axe scans have0reported violations and1,880incomplete node occurrences; no human/device acceptance is implied. Current evidence and limits supersede only the named outcomes, not mandatory acceptance scope.

Historical checkpoint: P5-15-01 functional/preservation audit

NO-GO for P5-15-02 under its current entry criteria; Production remains NO-GO. Phase5 is not complete. Audit from 932b962b9038ddb5ad59b982c0199475bfb50454 on the development branch,2026-10-09. Final01 report, all57 before/after results, 32-route native census, journeys/control limits and defects supersede the verification status, not the original contracts or historical evidence, below.

Exact PRES totals at the01 audit: 0PASS /53PARTIAL /3FAIL /1DEFERRED /0BLOCKED /0NOT VERIFIED =57. FAIL:E02 sign-in return query loss;J02 saved-search SQLite read500/silent empty list;S03 unsaved Rules draft loss on tab change. These were native failures at that checkpoint, not56 assumed defects or an assertion that the audit introduced them. R-01 supersedes J02; R-02 supersedes S03 for its verified bounded scope. Other groups retain evidenced sub-behaviors plus explicit long-tail/human/provider gaps.

All32patterns reached expected entry/refresh states for three identities (192observations);188route observations satisfy all asserted conditions/4fail on Discover. Of98selected native GET observations,94meet expected statuses/4fail;94route observations have no selected GET. Broader route workflow disposition30PARTIAL/2FAIL includes Login query return. A route/header is not full workflow acceptance. P1 DISCOVERY-01 blocks dependent progression until a separately authorized, individually pushed owner repair/native regression. P2 AUTH-01/SETTINGS-01 need their own remediation dispositions. No repair is hidden in01.

Fresh baseline: backend1,023;frontend459/82suites;117inherited browser cases all pass. Five new ordinary audit cases yield2pass/3genuine failures after harness correction: latest unique result119pass/3fail/122, combined across declared full/owning-suite runs. Separate preference diagnostics1pass/1fail. Sidecar49;focusedAI108/revision5(backend subsets);realHTTP2;security/config9/6/1/3;standard fidelity16/16,36=36;settings8/8,24=24. Builds/type/lint green. Fresh reports retain failures/provenance; no skip/expected-failure masking. P2-D01 remains an ordinary pass.

Three concurrent language/notification save rounds persist/reload successfully; prior intermittent500 not reproduced, still OPEN. Five Dashboard visibility flags are owner-local, not that failing server-language path. Fresh242axe scans have0violations and1,834incomplete node occurrences; neither incomplete nor unperformed human/device checks are passes. Production backup/restore/F04/config-schema-secrets/rollback remain unverified release blockers. P5-13 remains deferred,unqualified,Production-withheld,0/366calls/0human reviews/UIunimplemented; no qualification/Docker/UI work occurs. No application/CI/schema/config or main change/deployment occurs.

Every completed01logical unit is independently committed/pushed; see checkpoint ledger. Stop before02/P5-13/B07/production. The following00material remains the original planning record; its inherited-only baseline and future wording do not override01's fresh failures/results.

P5-15-00 — Historical acceptance-planning checkpoint

Planning only — Phase 5 is not complete; Production remains NO-GO. Reviewed 2026-10-09 from 46a0c0c6d23464869f50c0d88552963c29cfdacf on codex/ui-redesign-phase4. Actual production branch is main, with automatic deployment on push; its inspected revision is 27657f31131cd95d42f0e1290853ec9c9b3959a4. No application/test/CI/schema/configuration changes, deployment, production access, provider qualification, Docker recovery, P5-13 UI or B07 work belongs to this checkpoint.

This package audits the implemented product and prepares the remaining acceptance work. It does not rerun the application baseline or turn the P5-14 conditional verdict into full acceptance. Static source/commit/evidence checks and documentation hygiene are new planning evidence; reported regression/visual results below remain explicitly inherited.

Acceptance package and authority

Record	Purpose
Slice inventory	Every planned slice, verified implementation commit/current capability/test presence, readiness successors and plan discrepancies
57-group acceptance matrix	Complete original contracts, implemented touch, automated/manual/visual/responsive/localisation evidence, remaining action, severity and owner
Route and navigation acceptance	Original 31 patterns versus current 32, compatibility/query/permission/entry limits and runtime audit tasks
Manual accessibility/responsive script	Actual axe incomplete categories, practical human/screen-reader/device/zoom tasks and evidence requirements
Debt and production-readiness register	A/B/C/D classifications, known failures, safe executable operator checklist and release conditions
Numbered execution plan	Bounded P5-15-00–06 scopes, dependencies, tests/evidence, exit criteria and immediate commit/push boundaries

Sources remain Phase 1 full functionality and routes, Phase 2 preservation and traceability, Phase 3 architecture/impact, Phase 4 completion and conditional gates, approved Phase 5 plan, visual protocol, every linked implementation/readiness successor, production assessment, P5-13 deferral and P5-14 final source/evidence. Later approved, evidenced successors govern current status; original failed/historical records remain intact.

Status meanings: PASS means only the precisely named criterion has adequate evidence at its declared source/runtime. PARTIAL means some criteria have evidence but mandatory scope/proof remains; FAIL means demonstrated behavior contradicts the criterion; DEFERRED requires an explicit approved exclusion, not merely missing evidence; NOT VERIFIED means evidence is absent or inadequate. A test file's existence is an anchor, not an execution. Missing tests do not prove failure. A successful mocked/local test cannot satisfy a human, real provider, physical-device or production criterion.

Inventory decision

Implementation checkpoints exist for P5-00, 01, 02, 03, 04a, 04b, 06, 07, 08a, 08b, 09, 10, 11 and 12; P5-14 is a completed conditional subset checkpoint for implemented P5-09–12. The exact commits and current implementations are independently reconciled in SLICE_INVENTORY, rather than inferred from chronology.

In particular, P5-11 673cff114546a0976ae01ca9ca0d1086d36fee6a changes real preview chrome/readiness/fit/return behavior and adds owner/native browser evidence; P5-12 d8d262e4d1a6223f4b6c5fa52b8419013a929d35 changes the real gallery/settings grouping, retains advanced controls and adds six frontend/four browser cases plus eight settings exports. Both commits are ancestors of this source and their components/tests/evidence remain present. Neither is accepted merely because P5-14 passed. Manual/device/font and combinatorial settings limits remain.

P5-05 is deliberately reserved/deferred, not a missing completed ticket: a new active quick-preview host is an unapproved new workflow. P5-13 is unfinished/deferred, despite completed deterministic safety work and release withholding. P5-15 is planning in progress, with no final acceptance verdict. Broader Career Profile, CV library, global Documents, mail, Settings/Admin and Notifications presentation migrations remain Phase 7; advanced Dashboard ordering/resizing/reset/persistence remains Phase 8. Their existing protected capabilities still require preservation review, even though this phase does not redesign those pages.

Workstream acceptance summary

This table summarizes current acceptance, not implementation percentage. The linked 57-row matrix carries the complete original sub-workflows and per-group routes/components/evidence/owners. Existing screenshot/browser evidence is finite; human/device evidence is not supplied by this planning session.

Workstream / planned criterion	Current implementation; routes/components/PRES	Automated evidence	Visual / accessibility / responsive / locale evidence	Status; remaining action, severity/owner
Five shell readiness gates and grouped navigation; all existing destinations accessible	Existing App/AppShell navigation/providers/collapse retained; /settings, Jobs and all authenticated entries; E07–E09/A01–A03/S03	P5-00/01 shell, active-nav, dirty/account/permission fixtures retained	Recorded expanded/rail/drawer, EN/NB × themes, 320px/boundary keyboard and long-admin evidence	PARTIAL full acceptance; bounded implementation proof present. Current route/control traversal plus human names/focus/zoom needed; high if navigation inaccessible; shell/accessibility owner, 01/02
Command/notification utility semantics, no unintended mutation or stale account data	QuickCommandDialog/NotificationsPopover/App; existing destinations and /operations; E07–E09/S02/W11/W12	P5-02 keyboard/IME/query cancellation/read-dismiss/no-write and account regressions	Recorded populated/empty/error/focus and phone four-pair evidence; broader spoken names/live announcements absent	PARTIAL; mandatory P5-02 manual screen-reader item, command entry timing and transient feedback review; high interaction risk, 02/04
Jobs Table/mobile, paging/saved filters/selection/Trash/density/Back	JobTable/JobsView and /jobs, /trash, /jobs/:id; J03–J07/W01/W02/S03	P5-03, density and integration cases; native Back/query/row focus; owner/server read tests	Recorded Comfortable/Compact, light/dark EN/NB, populated/empty/error, desktop/tablet/phone cards	PARTIAL full edge/AT/device acceptance; audit current saved-view/bulk failure/control actions and return semantics; high preservation risk, Jobs owner 01/02
Board native/keyboard alternatives, exact custom statuses and complete same query	KanbanBoard/shared Jobs query; /jobs?view=board, /kanban; J05–J07/W01/W02	Readiness ID-membership/owner/trash tests, native pointer/keyboard/failed move and alias integration	P5-04a/b recorded desktop/phone/theme/locale/scroll evidence; native physical touch absent	PARTIAL; larger-result request/memory review and actual device/no-drag usability; potential medium/high scale/device impact, Jobs owner 01/02/04
Personal Dashboard honest available metrics/actions/five flags	DashboardView/shared existing reports; /dashboard; S01/S02/E07–E09/W11/W12	P5-06 report/definition/error/owner-local tests and native browser readback	Real populated/sparse/empty/error, value alternatives, EN/NB/themes/desktop/tablet/phone records	PARTIAL, preference-save 500 remains a recorded failure needing provider/concurrency/root-cause triage, not cosmetic acceptance; high reliability if reproducible; report/auth-storage owner 04
Analytics existing report families, exact definitions/sample/period and safe drill-down	Shared reports + AnalyticsPage; /analytics; S01/S02/J05/J09/E07–E09	P5-07 period/query/exact-value/independent-error regression evidence	Existing 6/12/24/current/all-time distinctions, sparse/custom categories, exact tables and four-pair responsive records	PARTIAL full AT/category/provider/timezone acceptance; current metric limits retained, no invented new denominators; report/accessibility owner 01/02
Job header/Overview actions/status/dates and safe section entry	ApplicationWorkspacePage/progress/detail; /jobs/:id, /applications/:id; W01/W02/W03/J05–J07/E07–E09	P5-08a real detail/status/missing/foreign/Back plus targeted progress keyboard cases	Recorded long/sparse/custom/interview/deadline states and theme/locale/phone reflow	PARTIAL full role/long-content/menu/SR review; no new job mutation semantics; high if an existing action is lost, workspace owner 01/02
Deeper sections/native frozen packages/documents/notes/tasks/timeline/mail/interview	Seven canonical URL sections and legacy text aliases, plus numeric navigation-helper arguments; retained domain children; W01–W12/M01/M02/M04/M05/C05–C12	P5-08b readiness native ZIP/immutable/readback/ownership, current ordinary P2-D01 and section/dirty/history proof	P5-08b recorded populated/empty/frozen/document scroll/phone; generated English events in NB and manual dialog semantics remain	PARTIAL; all-child action and external/provider/AT proof; followMode metadata preserved but compose UI DEFERRED, mail owner. High package/navigation boundary, 01–03
CV frame/navigation/save/history/undo and separate named editor/preview	CvBuilderEditor, identified route /career/builder/:id; C05/C06/C10/C12/E07–E09	P5-09 frame tests + revision readiness, current P5-14 draft/focus/conflict recovery	Four-pair local native viewport/mode/long-section evidence; human/device/zoom gaps	PARTIAL complete acceptance, implemented frame proven locally; current controls/reflow/assistive technology needed, CV owner 01–03
Source/override/CV-only/omitted content, reset/order and safe revisions	Existing canonical profile plus selected CV settings lens; /career, editor; C01/C02/C06/C07/C10/W05	P5-10 source/sibling/reset/save tests; P5-14 four nested owner/default-drop cases and native persisted order	Recorded inherited/custom/hidden/edit/error states, phone named alternatives, EN/NB/themes	PARTIAL all long-tail entries/manual scope understanding; P5-10-O01 closed only for tested gesture ownership. No whole-container dimming; high data-boundary risk, CV owner 01–03
Preview chrome, independent busy/error/retry/fit/count/keyboard scroll	Existing native HTML/iframe renderer + preview pane; C06/C08–C10/C12/E08/E09	Independent P5-11 focused owner/native tests plus final fidelity/scroll suites	White output in dark surround; one/multi/long pages, fit and return captures; P5-14 shell/landscape corrections	PARTIAL complete AT/device/zoom/production qualification; no manual zoom/fullscreen workflow is implied; CV/rendering owner 02/03
Template/appearance/layout controls retain all supported IDs/fields/default/reset	CvCustomizeTab/CvTemplateGallery, same settings/renderer; C06–C10/C12/E08/E09	Independent P5-12 controls/Pro locks/reset/value-preservation tests and 8 exports/24 aligned pages	Recorded Template/Style/Layout/Advanced controls, invalid input/reset/menu focus and four theme/locale pairs at desktop/tablet/phone	PARTIAL finite combinations/AT/production fonts/photos; some saved-only dormant values are not new controls. Document controls owner 02/03
Revision/override/frozen package and authoritative PDF correctness	Current API revision/CV settings and native package/PDF owners; C01/C05–C12/W05/W07/E09	Bounded 5/5 revision; 16/16 standard, 36=36; 8/8 settings, 24=24, native package/P2-D01 and ownership	Inherited local measurements/comparisons at fixed tolerances; Linux deployment/font/photo/wrapped-line combinations unqualified	PASS for those exact local oracle cases; PARTIAL overall. Preserve historical settings semantics versus frozen archived bytes, not an invented profile snapshot; critical document correctness, CV/native owner 03
CV AI factuality, proposal/review/apply and full responsive journey	Deterministic API guards implemented; Production service withheld; review UI not migrated; C11/C07/C10/S04	108 focused backend subset, sidecar49, realHTTP2; stale/tenant/history isolation retained	0/366 real configured-model calls, 0 human reviews, semantic accuracy unmeasured; new UI/missing AI responsive evidence absent	DEFERRED / NOT QUALIFIED; full planned Phase 5 blocked. No qualification/recovery/UI/activation here; product+AI owner only after a separate instruction
P5-14 responsive implemented CV subset	Same editing/settings/preview owners; C05–C12/E07–E09/S04	+4 frontend/+5 browser journeys; retained conflict/latest source/native renderer	33 selected captures, 320–1440px and short landscape; real mouse and emulated taps, four pairs	PARTIAL / CONDITIONAL GO for P5-09–12 only; physical/software-keyboard/SR/zoom/font and missing P5-13 journey remain, 02/03
Non-migrated original auth/security/account/Career/library/mail/Settings/Admin/capture/import/export	All original entries/owners retained; remaining E/J/C/M/S/A groups in 57-row matrix	Existing unit/service/native/security suites and original route census	Shared foundations affect these surfaces; some local representative Settings/canonical/public/Admin evidence, not all journeys	PARTIAL / NOT VERIFIED where missing evidence; unchanged code is not automatic acceptance. Provider/operator/low-frequency UI audits 01/02/05
Production ingress/recovery/config/schema/rollback/CI and actual auth/tenant health	Current main and existing deployment/backup mechanisms	Local security/config tests pass historically, not deployed proof	Required current operator/infrastructure verification missing	NOT VERIFIED — Production NO-GO; release-critical high/critical, operator+release owner 05; no push/deploy

Preservation, route and design reconciliation

All 57 original PRES groups remain required: 9 E, 10 J, 12 W, 12 C, 6 M, 5 S and 3 A. The matrix maps every group without redefining its full original row. Mapping completeness is not behavioral coverage. Account identity/Career Profile/CV/frozen package/send-attempt remain separate authorities; a scope label does not enforce ownership.

Current static routing has 35 declarations / 32 concrete patterns, preserving all 31 original patterns and adding /analytics. /kanban is now a compatible Board alias; /applications/:id and correspondence-review aliases retain their actual documented semantics. Static path presence does not prove entry/redirect/hash/dirty/history/permissions. The route audit lists explicit limitations and runtime checks. No actual /career/profile, global /documents, full /notifications or aggregate /admin destination is inferred from proposal/historical prose. Low-frequency destinations must remain reachable through existing primary/secondary/account/command/context paths.

Current known discrepancies require reconciliation, not invented features: historic blocked 04b and P2-D01 expected-failure text are superseded; followMode has an approved metadata-only exception; historical CV settings are not a full canonical Career Profile snapshot; manual preview zoom/new quick preview/global Documents/new metrics/customisation are separately proposed work. The existing P5-12 template reset/default/capability contract governs actual controls, even where a Phase 3 recommendation described different future UX.

Acceptance also compares cross-screen hierarchy, semantic surfaces/focus, P4 page widths/gutters/typography/section rhythm, table density/statuses/filters, action/menu/form/tab/dialog consistency, information density and dark mode. Retain actual useful data/actions rather than hiding controls to obtain cleaner screenshots. The visual protocol defines representative states and dimensions, not a mandate for a new component system or final branding decision.

Accessibility and responsive decision

P5-14 retains 242 axe scans, zero reported violation entries and 1,839 incomplete target occurrences: contrast 1,574; hidden-focus 34; prohibited ARIA 209; invalid ARIA values 18; table header/data association 4. These are repeated observations across states, not 1,839 distinct defects and not passing checks. MANUAL_ACCEPTANCE classifies exact rule/context handling, potentially serious traps/names/state/header failures, browser/iframe/transition limitations and required human visual/assistive-technology proof.

Existing native keyboard and screenshot review passes are evidence for their declared tasks. No suitable human screen-reader review, real-device/software-keyboard acceptance, actual 200%/400% browser zoom/forced-colours/text-spacing or production font/photo qualification is newly supplied here. Those remain NOT VERIFIED. Review commands/notifications, all mobile navigation, Board alternatives, charts/exact values, Job sections/dialogs, CV scope/settings/mode/focus/scroll/conflict and Settings, including loading/error. Emulated taps are not physical-device proof. Device/AT absence does not allow an agent to self-certify.

Production and debt decisions

Production stays NO-GO. Missing F04 actual proxy/socket peer/trust/IP/firewall/NAT/IPv6/DNS/TLS, current complete backup/isolated restore, real provider/config/schema/keys and tested rollback are A-class release blockers. Protected remote CI/deployment revision/authenticated owner smoke and operational monitoring/failure recovery also require actual proof. Read-only preparation or scripts' presence does not establish verification. READINESS_DEBT assigns A/B/C/D classifications, severity/owner/evidence to every retained issue and gives an executable operator sequence. No production endpoint is contacted by this plan.

Preference-save HTTP 500, SQLite concurrent saves, silent language-save failure, company-modal inaccessible feedback and dialog/command focus observations need bounded impact/root-cause investigation; this plan does not close them after a successful rerun. Board scaling/native touch, calendar/DST, startup fallback/worker containment, billing/deletion/provider delivery and all other recorded debt retain their specific enablement/release boundaries. P2-D01 is closed/ordinary passing. Tested shell/tooltip/toast/nested drag fixes remain scoped closures, never universal certification.

P5-13 remains DEFERRED — BLOCKED / NOT QUALIFIED. The frozen 32-case corpus/rubric and 366 required uncached generation/evaluation calls stay unchanged; configured deployed identity and semantic correctness remain unverified, zero human reviews, review UI unfinished. Deterministic grounding/source-version/tenant/no-write/history guards protect the authoritative API; they cannot replace model/human qualification. Production 503 cv_ai_unavailable withholding before provider/write stays active, and unrelated AI remains subject to its existing operational/privacy boundaries. Future qualification/UI/activation each needs its separate instruction/decision; none starts during P5-15-00.

Execution and verdict rules

The proposed checkpoints are 00 inventory → 01 functional/preservation → 02 responsive/accessibility → 03 CV/document correctness → 04 debt triage/individual remediation → 05 production evidence → 06 final regression/decision. Their entry/exit criteria, dependencies, test commands, reviewer/operator tasks and immediate commit/push boundaries are in EXECUTION_PLAN. Infrastructure/manual packet preparation can proceed independently; missing evidence cannot be recast as a pass. Each completed logical fix/evidence checkpoint is separately pushed and its SHA recorded before proceeding.

• Implemented product scope receives its own explicit PASS/PARTIAL/NO-GO decision, describing finite coverage and approved exclusions.
• Original full Phase 5 acceptance cannot be unconditional GO with mandatory P5-13 and human/device/other acceptance requirements incomplete. Deferral records obligations; it does not fulfill them.
• Production receives a separate NO-GO until actual A-class evidence passes. A later GO assessment and separate owner authorization are required before any production merge/push/deployment.
• Any demonstrated preservation/security/revision/frozen-output regression blocks its affected scope and release as appropriate. Missing evidence stays NOT VERIFIED; do not average it away or mask it with retries, tests or screenshots.

Baseline and planning validation

Inherited from P5-14: 1,023 backend; 459 frontend; 117 actual browser; 49 sidecar; 108 focused AI and 5 revision cases (backend subsets); 2 real HTTP; 9/6/1/3 rate-limit/ingress/PDF/config; 16/16 with 36=36 pages; 8/8 settings with 24=24 pages. App/E2E TypeScript, lint, frontend production/API/test Release builds, security/secret/whitespace/document checks have inherited passing records. No application suite, new rendered UI inspection, live-model test or production verification is claimed fresh for this planning-only checkpoint. Count changes: zero application/test changes and no new cases.

Planning validation checks exact source ancestry/path/test/evidence presence, all 57 unique IDs, original/current routes, inherited axe/fidelity/count reconciliation, local links/anchors, Markdown tables/fences, source-tree unchanged, staged secret/whitespace and development remote/tree state. Its sanitized planning check record distinguishes these new static checks from inherited regressions. The SHA is the commit introducing this package, obtainable from the command in the execution plan and the checkpoint's final report; no self-referential fabricated hash is stored.

Stop after committing and pushing P5-15-00 for review. No P5-15-01 implementation, production deployment, P5-13 work, B07 or next redesign phase starts automatically.