docs(roadmap): add recovery and localisation findings

docs(roadmap): record verified publication and partial research checkpoints
docs(phase10): record continuation and repeated publication blocker
2026-11-02 11:42:02 +01:00 · 2026-11-02 06:09:44 +01:00 · 2026-11-02 01:16:25 +01:00 · 2026-11-02 01:02:03 +01:00 · 2026-11-02 01:00:58 +01:00
11 changed files with 430 additions and 0 deletions
@@ -0,0 +1,95 @@
 # P10-00 — Baseline and deletion eligibility assessment
 > **Direct-chat review, 2 November 2026:** this draft is preserved below as historical worker evidence. The completed direct assessment is [P10-00](../../../redesign/phase-10/P10-00.md), with [continuity and the next gate](../../../redesign/phase-10/HANDOFF.md). Its current Git observations, evidence checks and narrowly nominated `App.css` candidate supersede this draft's unavailable-Git and no-candidate conclusions. Controller-specific claims below are historical, not verified authority in this chat. The owner authorised direct P10-00 assessment only; the orchestrator remains paused and untouched. No P10-01 implementation is authorised.
 Date: 1 November 2026. Scope: read-only assessment and this Markdown report only.
 ## Decision and authority
 P10-00 worker handoff is ready for independent controller checks. This is not checkpoint acceptance or full Phase 10 completion. No deletion is eligible on the evidence inspected. Recommend no P10-01 implementation scope at present. Stop at the protected `candidate-specific-cleanup-scope` gate.
 The active checkpoint and supplied verified owner decisions supersede the older handoff's unconfigured-adapter/unsigned-entry statements only for this restricted assessment. They authorize inspection and Markdown reporting at proposed integration baseline `fc5b9d377199ce51f480a920a3772108094929e3`; they do not authorize product changes, later checkpoints, security waivers or production. Active manifest identity supplied by the controller is `51e12f29078c420ac4ebd10127c8b7f7ba3cd73eac09dcbb4d47da1fe88fbeaf`. Private receipts and credentials were not accessed.
 The current control contract prohibits worker branch changes, commits and pushes. Consequently the controller must verify the current branch, clean immutable candidate, ancestry, source correspondence, normal publication and exact remote readback. No network query was made. Attempts to obtain Git identity failed because the worktree Git metadata was inaccessible. The shell started at `C:\` despite requested working directory; changing directory failed at the denied ancestor. Direct absolute-path reads of permitted repository files succeeded. This limits identity verification, not the authority of the supplied baseline. No alternate Git directory or permission bypass was used.
 ## Entry evidence reviewed
 Read repository `AGENTS.md` and `docs/redesign/IMPLEMENTATION_PLAN.md`, especially its requirement for unused-route proof, passing tests and preserved functionality before removal. Reviewed acceptance introductions and relevant evidence sections in:
 | Authority | Retained decision |
 | --- | --- |
 | `docs/redesign/phase-9/p9-requal-01/ACCEPTANCE_ADDENDUM_2026-10-24.md` | Historical Phase 9/10 NO-GO; RD21 resolved only in tested scope; hosted MariaDB blocked. |
 | `docs/redesign/phase-9/p9-sec-02/ACCEPTANCE_ADDENDUM_2026-10-25.md` | Later Phase 9 CONDITIONAL GO for qualified development; incomplete vendor Torch advisory response and release limitations retained. |
 | `docs/cv-redesign/ACCEPTANCE.md` | CV-UX-01 automated development PASS; overall CONDITIONAL GO; human/model/release limitations remain. This is the actual CV-UX report location. |
 | `docs/cv-import/ACCEPTANCE.md` | CV-IMPORT-01 CONDITIONAL GO for supported model-independent workflow; optional model adapter disabled/disconnected. |
 | `docs/cv-integration-qa/ACCEPTANCE.md` | CV-QA-01 CONDITIONAL GO; assessment/planning only, not cleanup authority. |
 | Supplied final entry, ready-to-run, protected request, acceptance, blockers, gates and entry proposal | Frozen tested application `ba04d817fed26d659bfa2a56b089d6cac851dc34`; published proposal `fc5b9d3`; PDF visual/S01 development approval does not establish physical printing or entry authority. |
 | Supplied active checkpoint and verified owner decisions | Assessment entry/evidence-reuse/runtime applicability granted; independent canaries pending; protected stop after P10-00. |
 The supplied original 19-entry inventory and prior CV-QA handoffs are carried forward below, with newly inspected source observations explicitly distinguished from inherited findings. These reports are not independently rehashed native evidence in this worker turn. No old conditional decision has been promoted to unconditional acceptance.
 ## Candidate inventory
 All entries have action **retain** unless stated otherwise. Historical purpose and current consumer are combined in the second column. An active consumer defeats a deletion proposal; it does not require proving exhaustive non-use. No entry below asserts absence of runtime consumers. Group mappings are affected groups, not new PASS claims.
 | ID / file or area | Historical purpose / current consumers and evidence | Preservation / proposed tests / risk |
 | --- | --- | --- |
 | CLEAN-01 `src/views/CvBuilderEditor.tsx` | CV authoring owner. Directly observed `App.tsx` lazy import and `/career/builder/:id` registration; not superseded merely by new library UI. | C05–C10; blank/inherited CV, undo/history/save/recovery/browser; HIGH. |
 | CLEAN-02 `src/components/CvTemplateThumbnail.tsx` | Template preview. Directly observed `CvTemplateGallery.tsx` import and render. Inherited inventory identifies sandboxed server sample HTML/cache/error paths. | C05/C08/C12; gallery/sample error/iframe/PDF checks; HIGH. |
 | CLEAN-03 `src/components/CvTemplateGallery.tsx` | Selection/library with explicit Apply and entitlement semantics; thumbnail composition directly inspected, no duplicate implementation established. | C05/C08; selection/legacy design/entitlement/browser; HIGH. |
 | CLEAN-04 `src/views/career/CvImportReview.tsx`, `CvImportMappingEditor.tsx` | Source correction/review owner. Directly observed `CareerProfilePage.tsx` renders review for pending/applied `docling-v1` runs; mapping responsibility inherited from CV-QA. | C01–C03; PDF/DOCX correction/assignment/duplicates/provider rollback; CRITICAL. |
 | CLEAN-05 legacy `CareerProfilePage.tsx` / `ProfileCvController.cs` | Historical non-Docling review. Directly observed non-Docling diff condition, POST `/profile-cv/runs/${runId}/accept`, and `[HttpPost("runs/{id:int}/accept")]`; a paired UI/API consumer exists. | C01–C03; old-run fixtures, accept/discard/conflict/replay; CRITICAL. |
 | CLEAN-06 `src/components/DashboardLayoutEditor.tsx` | Show/hide/save/reset/conflict/navigation owner. Directly observed `components/DashboardView.tsx` imports and renders both editor and grid. Grid is not its replacement. | M01–M06/E07/E08; preferences/keyboard/navigation/conflict/responsive; HIGH. |
 | CLEAN-07 `src/dashboardLayout.ts`, `hooks/useDashboardLayout.ts` | Persisted layout migration/CAS and hidden/future widgets per inherited inventory; hook directly imported by DashboardView. | M01–M06/S01–S05; v1/v2 migration, stale save, account disposal; HIGH. |
 | CLEAN-08 `src/views/AdminProcessingPage.tsx` | Current owner-scoped operation monitor; direct lazy import and `/admin/processing` registration in App. Audit/users/system routes remain separately registered. | A01–A03/E09/W12; authorization/redaction/rate/polling/browser; CRITICAL. |
 | CLEAN-09 redirects in `src/App.tsx` | Historical bookmarks/extensions. Directly observed `/kanban`, `/correspondence/review`, `/applications/:id` use compatibility redirect elements. | E07/J04/J07/W01; query/hash/navigation/ownership contracts; HIGH. |
 | CLEAN-10 `Models/CvTheme.cs`, `Services/ThemedCvRenderer.cs` | Historical document design. Directly observed version-sensitive theme resolution and multiple `DesignVersion == 2` layout branches; new appearance does not retire old settings. | C05–C12/W06/W07; unchanged Windows/Linux CV/letter goldens and frozen archives; CRITICAL. |
 | CLEAN-11 `CareerProfileMapper.cs` and import mapping/interpreter owners | Canonical persistence versus source interpretation/review translation; inherited CV-QA distinguishes side effects. No duplicate owner proved. | C01–C03/W05; provider transactions/rollback/replay/stale revision; CRITICAL. |
 | CLEAN-12 `ApplicationAssetsService.cs`, versioned writers | Inherited application/CV/letter/frozen submission contracts include null/no-op and RD21 behavior. No obsolete writer established. | W05–W07/C10; all writer, ownership, retry/conflict/frozen-byte tests; CRITICAL. |
 | CLEAN-13 migrations/context/provider helpers | Existing installation adoption and provider compatibility; staged retirement report explicitly withholds deletion. | All groups with persistence; migration/populated startup/parity/backup-restore; CRITICAL. |
 | CLEAN-14 `tools/summarizer/parser_child.py`, legacy extraction, Docling runtime | Inherited attachment/text consumers differ from structural CV conversion. Full runtime/route/image consumer census still needed. | C03/W08/W03; legacy extraction, parser security, actual Docling; HIGH. |
 | CLEAN-15 `tools/summarizer/cv_import_ai.py`, `CV_IMPORT_AI_ENABLED` | Disabled optional capability with contract tests, not obsolete functionality. Retain disabled; no activation. | C11/C03; disabled transport/schema/grounding/failure tests, separate model qualification; HIGH. |
 | CLEAN-16 shared styles/tokens/fonts/accessibility utilities | App theme and physical document/iframe/export styles have distinct owners; no asset/token unused proof. Dynamic names/embedding/locales remain unresolved census requirements. | E08/C08/C09/C12; type/lint/build/theme/EN/NB/axe/native PDF; HIGH. |
 | CLEAN-17 package/lock dependencies | Directly inspected `package.json` runtime/test/build scripts. `DashboardGrid.tsx` imports `react-grid-layout` and its CSS. No dependency removal justified by age or dependency section. | All affected groups; runtime/tool/script/Docker/platform census, reproducible lock/build/security/provider checks; HIGH. |
 | CLEAN-18 tests/goldens/historical reports | Regression and audit consumers, including original failures. Do not discard fixtures or assertions because newer paths pass. No obsolete fixture demonstrated. | All 57; discovery membership/oracle hashes/evidence integrity; HIGH. |
 | CLEAN-19 shell/dashboard reminder reads | Inherited P9-PERF-01 measurement candidate only; current duplicate request count not measured. Proposed action: retain, consider separately bounded measurement before consolidation. | W11/M01–M06/E09; loading/error/refresh/account disposal and before/after network counts; MEDIUM. |
 Frontend paths in this table are relative to `job-tracker-ui`; backend paths are relative to `JobTrackerApi` unless otherwise qualified. Preservation prefixes are `PRES-`.
 ## Census coverage and limitations
 Direct source inspection covered outer/public and shell route registrations, lazy imports, paired historical import UI/API consumers, design-version branches, dashboard ownership, gallery composition and dependency scripts. This uses several independent kinds of evidence; no safety conclusion rests on a single negative search. `rg` was unavailable, so bounded PowerShell reads and searches were used. No repository-wide zero-reference claim is made.
 Old pages/layouts/editors/import screens/document components are retained by the candidate register. Styles/tokens/hooks/utilities/dialogs/accessibility helpers have no proven unused candidate. Frontend routes and API endpoint compatibility have positive active examples; exhaustive external API-consumer absence is not established. Feature-flag inactivity is not obsolescence. Localisation keys, deprecated fixtures and dead assets need dynamic-key, bundle/export, test-discovery and historical-reference checks before any nomination. Dependency census must additionally cover conditional imports, build/test tooling, scripts, Docker and platform-specific paths; inspection of package metadata alone cannot prove non-use. Persisted-data inventories were not queried and no user data was opened. This is a bounded assessment, not a completed exhaustive dead-code proof.
 ## Historical data, SQLite and architecture
 Retain canonical Career Profile separately from CV overrides, inherited settings, historical versions, frozen submitted HTML/binaries, letters and application associations. Retain historical extraction runs and review/accept DTOs. No migration, data rewrite, route alias removal or renderer replacement is proposed. Actual old-document load/export verification is NOT RUN in this turn.
 Read `docs/database/mariadb-standardisation/README.md`, `ACCEPTANCE.md` and `SQLITE_RETIREMENT.md`. Retirement remains PLAN READY / REMOVAL NO-GO. The six gates require operator installation inventory, complete consistent export plus isolated restore, full-fidelity copied-data transfer, MariaDB coverage parity including direct SQLite harnesses, approved cutover with rollback after new writes, and retention-window sign-off. Existing partial export cannot establish lossless migration. No evidence reviewed closes those gates. Keep SQLite packages/helpers/provider branches and historical migrations. Track retirement independently; it does not block unrelated safe Phase 10 assessment or future qualified cleanup.
 Architecture improvements delivered here: none to product code. The report clarifies ownership and deletion boundaries. Removed files/dependencies: none. Performance/build-size differences: NOT MEASURED; no claimed improvement. Rollback for this assessment is removal/reversion of this report only, with no data or product rollback needed. Any future implementation requires its own exact reversible patch and compatibility strategy.
 ## Preservation and validation handoff
 Read Phase 9 preservation Markdown and parsed `p9-requal-01/preservation.json`. Carry all 57 IDs: E01–E09, J01–J10, W01–W12, C01–C12, M01–M06, S01–S05, A01–A03. Retain 56 PARTIAL / C11 DEFERRED, not PASS. Original 33-route register plus admin processing remains the 34-route preservation scope; wildcard/root routing must not be confused with independently accepted capabilities. App registration inspection is not end-to-end verification of every route.
 Worker product tests, browser/visual checks, MariaDB, sidecar/Docling, PDF fidelity, types, lint, build, security, accessibility, EN/Bokmål and historical-document runtime checks: **NOT RUN**. No fresh test counts are claimed. Supplied prior full-suite evidence remains historical: backend 1448, frontend 1031, affected Windows browser 51, separate import 8/MariaDB 90+3/RD21 6/admission 1/Linux 8, Python 83 + Docling 14, and both-platform exports, each retaining original execution identity and limitations. Original S01 28/20 failures remain historical; approved metric requalification 36/36 per platform is not a new export or physical print test.
 Controller must independently execute approved fixed suite IDs against the immutable handoff candidate: `backend-canary`, `frontend-canary`, `typecheck`, `lint`, `build`, `browser-canary`, `mariadb-canary`, `rd21-canary`, `python-canary`, `parser-security`, `docling-canary`, `pdf-linux-canary`. Require exact nonempty membership, process exits, source/freshness binding, no concealed failures/skips/retries, and cleanup evidence. No representative canary result can be reported as a fresh complete regression. Controller owns private receipt verification, publication and checkpoint acceptance. If identity/source correspondence fails, do not reuse historical evidence or advance.
 ## Decisions and next protected boundary
 | Decision | Status |
 | --- | --- |
 | P10-00 report handoff | Complete for independent checks; acceptance pending controller verification. |
 | Phase 10 overall | NO-GO for completion/implementation beyond assessment; no removal eligibility or P10-01 scope approved. |
 | Redesign development completion | CONDITIONAL GO remains limited to inherited development/preparation acceptance; final cleanup completion not established. |
 | Product review readiness | NO-GO for post-Phase-10 acceptance handoff; this is a preparatory debt/ownership report only. |
 | Production release | NO-GO. |
 Remaining debt: human physical-device/AT/contrast/EN-NB/printing checks NOT TESTED; real CV AI BLOCKED and disabled; deterministic recall/review burden and canonical-only generic-AI context limitations retained; Python vendor advisory incompleteness, hosted CI isolation, production TLS/advisories, native processing, filesystem/off-disk backup/restore and deployed identity remain separately unresolved. No risk acceptance, model activation, provider activation, schema change, main merge or deployment occurred.
 PRODUCT-REVIEW-01 preparatory handoff: preserve all contracts and individual debt dispositions, review canonical-only generic-AI context separately, and do not infer production readiness from UI/PDF appearance approval. Final phase-10 deliverables under `docs/redesign/phase-10/`, full regression reconciliation and post-redesign acceptance remain future work outside the current writable/approved report scope.
 TODO: controller verifies candidate/Git identity and independent checks; owner reviews this no-removal recommendation at the protected stop. A later request must name exact symbols, callers/routes/dynamic exports, old-data consumers, affected preservation IDs, compatibility transition, rollback and focused/full applicable tests. No P10-01 work should begin without that signed candidate-specific scope. If no candidate gains proof, retain it rather than invent cleanup work.
@@ -0,0 +1,21 @@
 # Blockers
 2 November 2026. Severity describes impact/gate importance, not an invented vulnerability rating.
 | ID | Feature / description and known cause | Severity / dependency | Required action | Elsewhere / gate scope / status |
 | --- | --- | --- | --- | --- |
 | B01 | P10 publication: Gitea pre-receive SIGSEGV rejected prior pushes | Mandatory checkpoint; external server fault | Normal push and exact readback | RESOLVED: remote `1692142295950e390a4cf807d9df86cc5cf96290`; no server repair performed |
 | B02 | P10-01 candidate approval absent; addendum explicitly retains this gate | Mandatory owner decision D01 | Approve/reject exact CLEAN-20 scope | Independent authorised planning allowed; blocks cleanup implementation; AWAITING_APPROVAL |
 | B03 | Ordered roadmap implementation lacks accepted predecessor phases | Mandatory dependency | Complete/accept predecessors and stage-specific scopes | Explicitly independent planning allowed; blocks dependent development; BLOCKED |
 | B04 | Physical device/AT/contrast/native-language/actual print qualification missing | Release qualification | Human review with actual evidence | Unaffected planning can proceed; production and affected acceptance; NOT_TESTED |
 | B05 | Real CV-model compatibility/semantic quality unqualified; adapter withheld | High activation gate | Separately approve safe immutable model qualification; retain disabled state | Model-independent work allowed; AI activation/claims; BLOCKED |
 | B06 | Hosted CI/isolation, production TLS/advisories, native parser/image isolation, backup/restore and deployed identity lack current qualification | High release gate; inherited evidence limits | Operator/isolated release evidence and scoped security disposition | Unrelated planning allowed; production; BLOCKED/NOT_TESTED by lane |
 | B07 | SQLite retirement lacks complete transfer, restore, parity, cutover and retention evidence | High data-preservation gate | Separate approved staged retirement | Unrelated cleanup/planning allowed; SQLite removal; BLOCKED |
 No material security risk or missing test is accepted by this register. Current dependency advisory status has not been refreshed; historical findings are not claims about a new scan. Additional source-specific entry decisions are recorded after eligibility review.
 Execution interruption: the three delegated workers hit a service usage limit. Parent continued and published partial I18N, homepage and release discovery checkpoints. Remaining audit/context/legal/rendered work is IN_PROGRESS/PENDING, not falsely classified as an external blocker. Resume locations are in NEXT_ACTIONS.md. No workers are running in the background.
 Security entry: the master prompt's `DO NOT START THIS NOW!` and feature-completion dependency remain unresolved; conflicting README immediate-review wording does not authorise a formal scan. No new vulnerability findings or material risk acceptance are claimed.
 RR-11 adds a reproduced deployment-backup parser compatibility defect (proposed P2); RR-12/13 document unqualified rollback/restore/encryption boundaries. See FINDINGS.md and the release branch recovery report. These do not block independent research or authorise deployment changes. I18N's remaining 80 dynamic calls and broader census are unfinished eligible work, not external blockers.
@@ -0,0 +1,33 @@
 # Direct roadmap checkpoint - 2 November 2026
 This is a consolidated progress report, not a final declaration that eligible work is exhausted. Independent research remains available. Product implementation is unchanged; the orchestrator remains paused and untouched.
 ## Completed and published
 P10-00 assessment is complete and published; candidate-specific P10-01 scope is recorded as D01. Normal Git publication now works. Existing GJ-00 planning publication is independently verified. Detailed exact commits are in WORK_COMPLETED.md.
 ## Partial work
 - I18N: source audit and machine-readable message inventory; initial Europe matrix and schema-validated planned locale catalogue. Dynamic/hardcoded/backend text, full contextual/legal review and final compatibility decision remain. No additional language translated or released; all 60 candidates remain planned.
 - Homepage: source audit identifies sign-in versus registration CTA mismatch, conceptual SVG previews, client-only rendering, generic metadata and missing footer legal links in the component. These are documented observations, not fixes. Four viewable concepts, genuine captures, imagery licensing, rendered accessibility/performance/SEO and owner design choice remain.
 - Release: preliminary architecture and failure-boundary inventory, ten historical blocker reconciliations and 18 mandatory gate rows. Five offline guard tests passed. No release candidate qualified.
 ## Decisions and dependencies
 Approve or retain only CLEAN-20 (`job-tracker-ui/src/App.css`, exact blob and verification scope in OWNER_DECISIONS.md). Generic continuation is not approval. Product Review prioritisation, provider agreements, I18N implementation/native release, homepage visual design, security entry/risk and production release each retain their separate gates. Later decisions will be presented with concrete evidence, not blanket permission requests.
 ## Security and AI
 Formal Security Audit has not started. Historical advisory/TLS/parser/image/operator qualifications remain unresolved, with no new vulnerability scan or waiver. Real CV-model compatibility and semantic accuracy remain blocked; deterministic extraction evidence does not establish model quality. No models or production services were started or accessed.
 ## Global Jobs
 GJ-00 planning at `0ec9f98e6ed4a646fc5e017d8eb6fade07653f37` is remotely verified. No new country/provider integration implemented in this continuation. Existing NAV/source behavior is not evidence that the planned global feature set is live. GJ-01 requires accepted predecessors, exact implementation authority and provider rights.
 ## Release and preserved evidence
 Latest scoped PDF metric/visual acceptance remains preserved; no affected renderer/font/fixture change justified reopening it. Physical print/device/AT/native-language checks are separate. Hosted MariaDB isolation remains explicitly blocked in source. Backup existence is not restore proof; final CI, recovery, migration, provider, production-equivalent identity and rollback evidence remain missing. Production is NO-GO.
 ## Next work
 Resume the precise eligible tasks and isolated worktrees in NEXT_ACTIONS.md. Delegated work stopped at a service usage limit; the parent salvaged, corrected and extended it. No background execution is running. Ordinary independent research does not require a new blanket prompt; the remaining P10 decision does require explicit approval under the user's addendum.
@@ -0,0 +1,20 @@
 # Continuing findings list
 2026-11-02. Observed defects, source limitations and planning work are separate. This list does not approve implementation, accept risk or close mandatory gates. Exact branch evidence is in WORK_COMPLETED.md.
 | ID | Finding | Evidence / current state | Next action |
 | --- | --- | --- | --- |
 | RR-11 | Deployment backup parser fails to extract the documented `Host=` alias; uppercase `SERVER=` also fails | REPRODUCED with shell-native synthetic positive control; canonical `Server=` works. Proposed P2 compatibility defect, no production impact inspected | Minimal parser/contract remediation in authorised release scope; alias/case/quoted separator/redaction checks |
 | RR-12 | Core-image rollback lacks post-rollback health check and does not reverse database/schema or AI changes | VERIFIED SOURCE LIMITATION; runtime recovery NOT TESTED | Isolated post-migration/post-write rehearsal; distinguish image-only and data recovery |
 | RR-13 | Backup format checks and off-host messages do not prove restore consistency or encryption | QUALIFICATION GAP; no actual recovery performed | Verify database/files/keys/tombstones together, off-host retrieval/decryption and agreed RPO/RTO |
 | I00-13 | Session-invalidated alert is hardcoded English | SOURCE VERIFIED, `App.tsx:488` | Localise without retaining old session tree or relying on discarded provider state |
 | I00-14 | Workflow overline `Flow` bypasses catalogue | SOURCE VERIFIED, `JobFlowBar.tsx:147` | Extract controlled UI label in approved I18N implementation |
 | I00-15 | Attachment iframe accessible title is only `pdf` | SOURCE VERIFIED, `Attachments.tsx:361` | Descriptive localised title; exclude private filenames from translation exports |
 | I00-16 | `EN`/`NO` and `English`/`Norsk` do not express planned locale/variant contract | SOURCE VERIFIED, `AppShell.tsx:692` | Native/English names, Bokmal/Nynorsk distinction and legacy nb preservation |
 | I00-17 | Attachment size uses fixed decimal formatting | SOURCE VERIFIED, `ApplicationAssets.tsx:360` | Locale-aware numeric display; preserve bytes and filename |
 | I00-18 | Language-save failure/retry reads catalogue directly | ACTIVE CONTRACT, `I18nProvider.tsx:43`; not a defect by itself | Preserve same-language retry/stale-save behavior; include in migration inventory |
 | I00-19 | Homepage framework/provider-name list is poor user-value copy | SOURCE VERIFIED, `LandingPage.tsx:133`; design recommendation | Coordinate with Launch Site concepts; no unapproved copy or feature claims |
 I18N progress: 108/188 dynamic calls resolved to finite literal branches; 240 existing-key references validated; 80 calls remain. Four direct reads and 26 reviewed JSX/accessibility candidates recorded. These are inventory counts, not translation completeness or runtime test passes.
 Earlier homepage and qualification findings remain in their branch reports. Add new findings with stable IDs and evidence status; do not rediscover unchanged items on each continuation.
@@ -0,0 +1,12 @@
 # Next eligible actions
 2 November 2026.
 1. D01/CLEAN-20 is presented in chat and awaits precise owner approval. Do not delete `App.css` beforehand. When approved, recheck source identity and perform only its documented implementation/verification/publication scope.
 2. Continue I18N-00 in `C:/Users/Connor/.codex/worktrees/i18n-00-audit/Job tracker` at `55adc1db`: follow `docs/i18n/00/HANDOFF.md`. Resolve the remaining 80 dynamic calls and computed/frontend/backend text, real translator context/sensitivity, territory legal records and library compatibility. This is eligible research, not an external blocker.
 3. Continue LAUNCH-00/01 in `C:/Users/Connor/.codex/worktrees/launch-site-planning/Job tracker` at `756ab616`: rendered homepage/signup audit, pattern research, genuine synthetic captures, then four actual desktop/mobile concepts. No final design choice or implementation before owner review.
 4. Continue release Stage 1 in `C:/Users/Connor/.codex/worktrees/release-readiness-discovery/Job tracker` at `653f8d04`: complete endpoint/environment/failure-boundary census; recovery source inspection and rehearsal specification are now saved. Do not rerun unchanged full suites or touch live services.
 5. Provisional independent Product Review research is eligible, but must remain clearly provisional until accepted Phase 10. Existing GJ-00 publication is verified; reuse its 23-document planning pack and frozen subordinate prompts rather than recreating it. GJ-01 implementation remains blocked.
 6. After each completed independent task, update blockers and identify newly eligible work. Unaccepted research cannot satisfy a prerequisite requiring accepted implementation. The session has unfinished eligible work; this checkpoint is not an exhaustion-of-roadmap declaration.
 Use `ROADMAP_STATUS.md` and the branch-specific handoffs to resume. Never use the autonomous backlog orchestrator. Keep pre-p10-ux and unrelated work intact; no main merge or production deployment. Git is currently operational; avoid repeating the resolved server investigation.
@@ -0,0 +1,16 @@
 # Owner decisions
 2 November 2026. The Continuous Progress Addendum explicitly says P10-01 remains blocked until precise approval. It supersedes the earlier handoff's interpretation of “continue” as permission. No signed approval or controller state is created here.
 ## D01 — P10-01 / CLEAN-20
 **AWAITING_APPROVAL.** Choose:
 - Approve removal of only `job-tracker-ui/src/App.css` (recommended), under the exact verification and rollback scope in [P10-00](../redesign/phase-10/P10-00.md).
 - Retain the file and request a revised/no-removal checkpoint disposition.
 The file is 38 lines of unimported original CRA styling, Git blob `74b5e053450a48a6bdb4d71aad648e7af821975c`. No callers, routes, persisted data or replacement are expected. Verify source identity, types/lint/build and the specified existing EN/NB/theme/browser cases; restore the exact file by reverting the implementation commit if verification fails. Accepted PDF evidence remains unchanged. Approval covers only CLEAN-20 plus necessary evidence/verification, not another removal or later initiative. Publication of the assessment is now verified; implementation approval is the remaining immediate gate.
 ## Later decisions — not requested prematurely
 Product-ranked scope, Global Jobs implementation and provider licences, I18N implementation and human language release, homepage design selection, security target/environment and material-risk disposition, and final release approval retain their own concrete review gates. Research does not grant these decisions. Do not ask for generic blanket approval or treat this list as completed sign-off.
@@ -0,0 +1,25 @@
 # Direct roadmap status
 Updated 2 November 2026. This is documentation, not an executable queue. The Continuous Progress Addendum controls direct-chat work; the autonomous orchestrator remains paused and untouched.
 | Workstream/checkpoint | Status | Dependency and evidence |
 | --- | --- | --- |
 | PHASE-10 / P10-00 assessment | COMPLETED | Report in `../redesign/phase-10/P10-00.md`; assessment `7ba1367`, publication receipts `8cdff28`/`1692142`. Remote exactly `1692142295950e390a4cf807d9df86cc5cf96290` on 2 November |
 | P10-01 / CLEAN-20 | AWAITING_APPROVAL | Delete only unused `job-tracker-ui/src/App.css`; precise owner decision D01 below. Addendum explicitly withholds implementation |
 | P10-02 CV/documents | BLOCKED | Preceding cleanup checkpoint and any exact candidate approval; retain historical documents |
 | P10-03 backend/dependencies/config | BLOCKED | Predecessors; no proven removal currently approved |
 | P10-04 functional/data verification | BLOCKED | Defined and accepted cleanup scope; fresh affected verification required |
 | P10-05 full acceptance | BLOCKED | P10-01–04 and complete applicable acceptance programme |
 | PRODUCT-REVIEW-01 | BLOCKED | Final audit requires accepted Phase 10. Provisional independent research is eligible; not yet performed or substituted for final acceptance |
 | INT-GLOBAL-JOBS-01 / GJ-00 | CONDITIONAL | Existing planning at `0ec9f98e6ed4a646fc5e017d8eb6fade07653f37`; exact remote reverified 2 November. No implementation authorised |
 | INT-GLOBAL-JOBS-01 implementation | BLOCKED | Accepted Phase 10/Product Review, initiative approval and provider rights |
 | I18N-01 / I18N-00 audit | IN_PROGRESS | Partial source-bound audit published at `55adc1dbd742a570d55d3a4d13f5613a7ed2ab25`; 3,119 messages, 60 planned locale candidates; 108 conditional calls resolved, 80 remain. Contextual/legal/library review incomplete |
 | I18N-01–08 implementation/acceptance | BLOCKED | I18N-00 and stage prerequisites plus documented implementation authority; no locale publication approved |
 | LAUNCH-SITE-01 / LAUNCH-00 audit | IN_PROGRESS | Source audit and claim boundaries published at `756ab616a22746a9bafa9830afd4f8efbb085794`; rendered audit still pending |
 | LAUNCH-01 four desktop/mobile concepts | PENDING | No viewable concepts produced; eligible independent task after completing audit inputs |
 | LAUNCH-SITE final design/implementation | AWAITING_APPROVAL | Four concrete concepts must be delivered before owner selection; no final design auto-selection |
 | SECURITY-AUDIT-01 / stages 00–16 | BLOCKED | Master begins `DO NOT START THIS NOW!` and requires finished feature development/baseline tests; README's immediate-review wording does not silently override that gate. No formal scan started |
 | RELEASE-READINESS-01 / Stage 1 discovery | IN_PROGRESS | Preliminary inventory, blocker reconciliation and 18-gate matrix published at `653f8d04d469dcd52c883d4b98bea76b8adacada`; five runner guards and four workflow guards passed in separate checks; recovery review and RR-11 reproduction saved; full discovery incomplete |
 | Release stages 2–7 baseline, qualification, remediation, requalification, rehearsal, final acceptance | BLOCKED | Final release candidate/prerequisites not accepted; each stage needs actual applicable environment and source-bound evidence |
 Implemented, tested, accepted, published and production-ready are separate. Production is NO-GO. Historical counts are not fresh executions. See [blockers](BLOCKERS.md), [owner decisions](OWNER_DECISIONS.md), [completed work](WORK_COMPLETED.md) and [next actions](NEXT_ACTIONS.md).
@@ -0,0 +1,33 @@
 # Work completed
 2 November 2026.
 | Work | Commit / evidence | Limits |
 | --- | --- | --- |
 | Direct P10-00 assessment, preserved prior draft, candidate inventory, rollback/verification proposal | `7ba1367fd2e84375b3065eeedf9176a34996f77b` | Markdown only; no P10-01 deletion |
 | Publication failure/continuity receipts | `8cdff28f0781e4c99efd06079149d9933e01cd4e`, `1692142295950e390a4cf807d9df86cc5cf96290` | Earlier server failures remain historical |
 | Restored normal publication | Push succeeded; independent `ls-remote` exactly `1692142295950e390a4cf807d9df86cc5cf96290` | No server repair, hook bypass, force push, main merge or deployment |
 | P10 evidence integrity/source applicability | 263 indexed hashes; 1,280 source files; 7 verifier sources; 57 groups/34 routes | Previous direct-assessment checks; not freshly rerun product suites in this continuation |
 | Lightweight direct-roadmap register | This documentation checkpoint | No runner, scheduler, approval service or replacement orchestrator |
 The application baseline remains source-equivalent to accepted `ba04d817`. Historical PDF metric/visual acceptance is preserved. Current continuation product suites: NOT RUN. Models/production services: NOT ACCESSED.
 ## Published partial research checkpoints
 All three branches start at accepted conditional handoff `5cb903b989742b7a96cb22ddf4c0e24993b18980`; no unaccepted Phase 10 changes were integrated. Normal pushes succeeded and each remote ref was independently read back exactly.
 | Branch | Exact remote commit | Actual output / limits |
 | --- | --- | --- |
 | `feature/i18n-00-audit` | `138d8fbb6da51141b50f2acb3979458ce173a6c3` | Ten research files; 3,119 English entries, 3,164 static calls, 134 files; 188 dynamic/unknown calls unresolved; initial 59-territory matrix and 60 planned locales. Existing Ajv/Intl checks passed, including rejection of released status. Full audit NOT COMPLETE |
 | `feature/launch-site-redesign` | `756ab616a22746a9bafa9830afd4f8efbb085794` | Three source-audit/claims/handoff documents. No mockups or final implementation; rendered audit NOT RUN |
 | `planning/release-readiness-discovery` | `edd2aa9ae428435773e5cf48167af4e0db1ef36a` | Five preliminary discovery/evidence/matrix/handoff documents; 5 existing offline MariaDB runner guards passed. No real DB/hosted/production qualification |
 Global Jobs planning remote independently verified at `0ec9f98e6ed4a646fc5e017d8eb6fade07653f37`. This resolves publication uncertainty, not GJ-01 entry gates.
 Delegated workers hit a service usage limit. Parent continued, reviewed and corrected incomplete draft claims, then produced and published these partial checkpoints. No worker remains active. No partial stage is promoted to completed merely because its documents exist.
 ## Further continuation - published and remotely verified
 - Release discovery `653f8d04d469dcd52c883d4b98bea76b8adacada`: complete deployment-script source inspection, recovery review and isolated rehearsal specification; RR-11 synthetic parser reproduction and RR-12/13 qualification gaps. Four existing workflow-quarantine tests PASSED, shell syntax PASSED. Initial direct Windows/sed harness failed its positive control and was discarded; shell-native rerun established the three-case result. No deployment/restore/database activity.
 - I18N research `55adc1dbd742a570d55d3a4d13f5613a7ed2ab25`: records for 188 dynamic calls; 108 finite conditional calls resolved with 240 verified key references, 80 remaining; four direct catalogue reads; 26 individually reviewed literal candidates; seven stable findings. No application/test implementation changes.
 - FINDINGS.md consolidates ten new observations/contracts/qualification gaps with precise next actions. These remain separate from implementation acceptance.
@@ -0,0 +1,45 @@
 # Direct-roadmap continuity
 2 November 2026. Worktree: `C:\Users\Connor\.codex\worktrees\p10-assessment\Job tracker`. Branch: `feature/phase10-cleanup`. Initial HEAD: `fc5b9d377199ce51f480a920a3772108094929e3`; reported handoff `5cb903b989742b7a96cb22ddf4c0e24993b18980` is an ancestor and matched its original branch's live remote readback. Frozen application source remains `ba04d817fed26d659bfa2a56b089d6cac851dc34`.
 ## Completed and current gate
 **Latest authority, 2 November 2026:** the owner's Continuous Progress Addendum explicitly retains precise P10-01 approval as outstanding, superseding the earlier interpretation of “continue” below. P10-01 is AWAITING_APPROVAL. Git publication is now resolved: normal push succeeded and independent remote readback matched `1692142295950e390a4cf807d9df86cc5cf96290`. Earlier failed attempts remain historical. Continue explicitly eligible independent planning under [the direct-roadmap register](../../direct-roadmap/ROADMAP_STATUS.md); do not use the former blanket conclusion that every later planning task is blocked. The I18N-00 source explicitly permits an audit while earlier gates remain blocked.
 Continuation, 2 November 2026: the owner instructed “continue as far as you can” in response to the specific CLEAN-20 proposal. This is taken as permission to continue that nominated scope, not approval of additional candidates or later initiatives. Implementation still cannot begin across the mandatory publication gate. A normal push of clean local `8cdff28f0781e4c99efd06079149d9933e01cd4e` was retried once and again failed with the same remote SIGSEGV/pre-receive rejection. Independent remote readback again returned only the original handoff branch at `5cb903b`; the Phase 10 ref is absent. No server repair or hook bypass was attempted. The approval-pending statements below describe the preceding checkpoint; this continuation supplies the latest chat instruction, while publication remains BLOCKED.
 Dependency disposition: P10-01 waits for required publication; P10-02–05 wait for their preceding checkpoints and applicable candidate decisions; PRODUCT-REVIEW-01 waits for accepted Phase 10; Global Jobs, I18N, Launch Site, Security Audit and Release Readiness wait for their ordered predecessors and entry gates. None is an independent next item that can be started by skipping this failure. The remaining external action is operator resolution of the Git-server hook fault, followed by normal push and exact remote verification. Preserve local work and stop at this boundary.
 - Completed [P10-00](P10-00.md); preserved the existing staged worker draft with a dated review note. Only Markdown changed.
 - Fresh checks: 263 indexed evidence hashes, 1,280 current frozen source files and 7 verifier-source entries all match; 57 groups retain 56 PARTIAL/C11 DEFERRED; 34 distinct routes match the preserved register. Product suites were NOT RUN. Historical results remain historical.
 - Sole proposed candidate: **P10-01/CLEAN-20**, delete the unimported original CRA `job-tracker-ui/src/App.css`, blob `74b5e053450a48a6bdb4d71aad648e7af821975c`. Exact callers/data/routes, required checks, rollback and stop conditions are in P10-00. All other assessed compatibility code remains retained.
 - **Await explicit candidate-specific owner approval in this chat and successful required publication. No implementation is authorised yet.** Do not treat approval of this stylesheet as permission for P10-02 or another initiative.
 - Assessment checkpoint: **`7ba1367fd2e84375b3065eeedf9176a34996f77b`**, `docs(phase10): complete direct P10-00 assessment`. Four Markdown files, 258 inserted lines including the preserved staged draft. Documentation links, original-draft preservation, candidate hash and no-product-change assertions passed; staged `git diff --check` passed. Working tree was clean after that commit.
 - **Publication FAILED / advancement BLOCKED.** Normal `rtk proxy git push -u origin feature/phase10-cleanup` exited 1: remote `fatal error: fault`, `SIGSEGV`, `github.com/go-enry/go-enry/v2/data.map.init.6()`; final result `pre-receive hook declined`. Independent subsequent `git ls-remote origin refs/heads/feature/phase10-cleanup refs/heads/test/pre-phase10-ux-acceptance` returned only `5cb903b989742b7a96cb22ddf4c0e24993b18980` for the handoff branch. No Phase 10 branch was published. No infrastructure repair, hook bypass or force push was attempted.
 - The documentation-only commit containing this publication receipt is also local; resolve its exact SHA with `git rev-parse HEAD`. It changes no product source. Do not describe either local checkpoint as remotely verified.
 After the Git-server operator resolves the hook fault independently, normal publication and exact remote readback remain required. Do not retry indefinitely or repair the server in this task. Owner approval of CLEAN-20 can be recorded while publication is blocked, but implementation must wait until both gates are satisfied. Assessment content completion is not published checkpoint acceptance.
 ## Resume without repeating the assessment
 Read any newer owner reply and this handoff. Inspect current Git state and the candidate/source identity. Reuse the source-bound accepted evidence if unchanged. If CLEAN-20 is approved, perform only its documented patch/verification/publication, updating evidence and this handoff. Do not reinstall/retest unchanged product scope merely to restart this chat. Significant or affected changes require fresh applicable checks. Missing dependencies/graph/build/runtime prerequisites must be reported accurately, without modifying another worktree or inventing results.
 No autonomous controller commands or state, keys, signatures, approvals, configuration or queue may be used, repaired or changed. It must remain paused. Do not modify `C:\Users\Connor\.codex\worktrees\pre-p10-ux\Job tracker`. No main merge, production deployment, production services, application AI models or deferred CV-import overhaul/personal portfolio work is authorised.
 ## Authoritative order after Phase 10 acceptance
 All seven source files exist; their bytes were fingerprinted during P10-00. Only the active Phase 10 source was read as execution requirements here. Before entering each later workstream, read its complete source and every required linked/subordinate prompt, recheck dependencies and obtain its applicable entry decisions. Do not substitute this order table or old orchestrator records for those requirements.
 | Order | Workstream / source below `E:\Storage\Projects\Active\temp docs\final\` | Source SHA256 observed |
 | --- | --- | --- |
 | 1 | PHASE-10: `Prompt 5 — Phase 10.txt` | `f3d5d183a1cd653aac2207a8435ba95fbb74ef4bb8cc91d605edd959f9f4ec72` |
 | 2 | PRODUCT-REVIEW-01: `Prompt 6 — PRODUCT-REVIEW-01.txt` | `544d11a2d1e9a913397766c7e475f63338f0b735d2bb26dcabdedb6fe9e25a58` |
 | 3 | INT-GLOBAL-JOBS-01: `done\Prompt 7 — INT-GLOBAL-JOBS-01.txt` | `c67c70862eecf677e1f2944fd0e17799068c054738d520513955fcf6542c52ce` |
 | 4 | I18N-01: `I18N\00_MASTER_ORCHESTRATOR.md`, including its entire linked prompt pack | `6365901a0521d603f8059de31492bc6353229c684da23b8553df49b4844fd330` |
 | 5 | LAUNCH-SITE-01: `Prompt 10 - homepage.txt` | `f1d2b143796725e37b9a86643975a716f0be2109687fc772c6e26dae5172eaa0` |
 | 6 | SECURITY-AUDIT-01: `jobjakt-security\MASTER_PROMPT.md`, including its entire linked prompt pack | `37bec461f84df60b787bda45db3bd9af1a6c836c6c023f3ab6dd7dc4beb2c6db` |
 | 7 | RELEASE-READINESS-01: `prompt 11 - release readiness.txt` | `12c846d754b170c2e767db05816f4053d9e8c4cf58a2349121b2de91875beaf2` |
 Phase 10 checkpoints remain P10-00 baseline, P10-01 frontend, P10-02 CV/document compatibility, P10-03 backend/dependencies/config, P10-04 data/functional verification, P10-05 full acceptance. Subsequent scopes require evidence and the applicable candidate gates. If nothing is safely removable, say so; never invent a deletion to complete a checkpoint.
 Human/device/language/printing, AI semantics, provider licences, hosted CI, security and production decisions remain separate. SQLite retirement stays a separately gated initiative. Production NO-GO does not prohibit an otherwise authorised bounded assessment.
@@ -0,0 +1,120 @@
 # P10-00 — Direct assessment and deletion eligibility
 2 November 2026, Europe/Paris. **Assessment complete and published; P10-01 awaits candidate-specific owner approval.** Normal publication subsequently succeeded at `1692142295950e390a4cf807d9df86cc5cf96290`, independently read back from the remote. The Continuous Progress Addendum explicitly retains the owner gate. No application/test/dependency/schema change or deletion was performed. One narrowly bounded frontend stylesheet is nominated below; the other assessed areas remain retained. Phase 10 completion and post-redesign product-review acceptance are not established. Production remains NO-GO.
 ## Authority, baseline and draft review
 The owner's direct-chat instruction authorises repository inspection and Markdown assessment only, then requires a stop for approval of the exact P10-01 scope. It explicitly prohibits using, repairing or activating the autonomous backlog orchestrator. Its old adapter, policy, signing and queue requirements describe autonomous execution; they are not prerequisites for this separately authorised direct assessment. No controller command, key, receipt, configuration or queue was accessed or changed. Future source-defined product, security, provider and human gates remain mandatory in their applicable scopes.
 Read the complete external `Prompt 5 — Phase 10.txt`, including its prerequisites, fifteen inventory categories, checkpoint order and acceptance requirements, and the original [implementation plan](../IMPLEMENTATION_PLAN.md#phase-10--cleanup). External source SHA256: `f3d5d183a1cd653aac2207a8435ba95fbb74ef4bb8cc91d605edd959f9f4ec72`. [AGENTS.md](../../../AGENTS.md), its RTK instructions, the [current architecture pointer](../../architecture/current.md), [overview](../../architecture/overview.md) and linked frontend/backend/data/integration/schema/deployment descriptions govern ownership.
 | Identity | Fresh observation |
 | --- | --- |
 | Worktree | `C:\Users\Connor\.codex\worktrees\p10-assessment\Job tracker` |
 | Branch / initial HEAD | `feature/phase10-cleanup` / `fc5b9d377199ce51f480a920a3772108094929e3` |
 | Initial changes | Only staged `docs/automation/stages/PHASE-10/P10-00.md`, 93 lines; no unstaged or unrelated files |
 | Reported handoff | `5cb903b989742b7a96cb22ddf4c0e24993b18980`, verified ancestor of initial HEAD |
 | Remote handoff readback | `git ls-remote origin refs/heads/test/pre-phase10-ux-acceptance` returned exactly `5cb903b989742b7a96cb22ddf4c0e24993b18980`; the Phase 10 branch did not yet exist remotely |
 | Frozen tested application | `ba04d817fed26d659bfa2a56b089d6cac851dc34`, ancestor of HEAD; all subsequent committed differences are inside `docs/automation/handoffs/pre-phase10/` |
 | Final assessment/publication identities | Recorded in [HANDOFF.md](HANDOFF.md); resolve current branch HEAD, never infer publication from an older readback |
 Reviewed and preserved the [existing draft](../../automation/stages/PHASE-10/P10-00.md). Original staged content SHA256 was `55afecbcb09d91762fdddb2670c409566bf58f9fce6c2a705627e9fcfb8e10d0` (16,809 bytes). Only a dated review notice is added; its original text remains intact. Its positive active-consumer findings are useful. Its supplied manifest identity, asserted verified owner/controller decisions, Git-access failure, required controller canaries and prohibition on worker commits are historical context, not independently verified facts or direct-chat requirements. Its no-candidate conclusion is superseded only by the additional stylesheet investigation below. A worker's completion statement does not establish acceptance.
 Graphify query was attempted before source searches. It failed because this worktree has no `graphify-out/graph.json`; no graph was created and no other worktree's graph was used as current proof. Source inspection used RTK-wrapped `rg`, Git, bounded file reads and assert-based integrity checks. No dependency installation or infrastructure repair occurred.
 ## Accepted evidence and its applicability
 Reviewed the [Pre-Phase-10 acceptance](../../pre-phase10-ux/ACCEPTANCE.md), [CV-QA handoff](../../pre-phase10-ux/CV_QA_HANDOFF.md), [integration QA acceptance](../../cv-integration-qa/ACCEPTANCE.md) and [Phase 10 handoff](../../cv-integration-qa/PHASE_10_HANDOFF.md), [CV-UX acceptance](../../cv-redesign/ACCEPTANCE.md) and [compatibility handoff](../../cv-redesign/CV_IMPORT_HANDOFF.md), [CV-import acceptance](../../cv-import/ACCEPTANCE.md), and [Phase 9 security/requalification addendum](../phase-9/p9-sec-02/ACCEPTANCE_ADDENDUM_2026-10-25.md). Their conditional development decisions remain limited to their stated scope.
 The later [final development-entry review](../../automation/handoffs/pre-phase10/FINAL_DEVELOPMENT_ENTRY.md), [authority reconciliation](../../automation/handoffs/pre-phase10/AUTHORITY.md), [baseline](../../automation/handoffs/pre-phase10/PHASE10_BASELINE.md), [handoff](../../automation/handoffs/pre-phase10/HANDOFF.md), [reproduction contract](../../automation/handoffs/pre-phase10/REPRODUCE.md), [ready-to-run conditions](../../automation/handoffs/pre-phase10/READY_TO_RUN.md) and current acceptance/evidence index distinguish historical statements from later decisions. Read the linked [PDF report](../../p10-entry-final/REPORT.md), review guide, owner-review requirements and [S01 disposition](../../automation/handoffs/pre-phase10/S01_APPROVAL.md). The 30 October owner metric/visual records supersede earlier metric/visual-pending statements only for their approved development scope. Physical printing/device/AT/language checks are still unperformed. No accepted PDF criterion was reopened or changed.
 Fresh checks against the current worktree:
 | Check | Result / exact boundary |
 | --- | --- |
 | Indexed compressed evidence hashes | **PASSED: 263/263** SHA256 values match `TEST_EVIDENCE.json`; this does not rerun their producers |
 | Application source-before/source-after manifests | **PASSED: identical**, with **1,280/1,280** current file hashes matching; zero mismatches |
 | Handoff verifier-source identity | **PASSED: 7/7**, both worktree bytes and the committed `39bf430401d86f894277fdd78e7eb88c58d81e8b` objects match the indexed manifest |
 | Preservation classification | **PASSED membership check: 57 unique groups**, retaining **56 PARTIAL / C11 DEFERRED**; no promotion to PASS |
 | Route census | **PASSED: 34 distinct application routes**, exactly the original 33 plus `/admin/processing`; outer/shell wildcard infrastructure and duplicate `/` are not extra capabilities |
 | Product suites, typecheck, lint, build, browser and visual runs | **NOT RUN in P10-00**; assessment changed Markdown only |
 | Full package semantic/schema/native-membership verifier | **NOT RUN**; its entry contract requires the original handoff branch and restricts all descendants to the handoff directory. No verifier was changed or bypassed to make this direct assessment appear accepted |
 The hash/source checks support reuse, not a new full regression or independent security attestation. The historical package retains 1,448 backend / 1,031 frontend cases, 51 affected Windows browser cases, separate import 8 / MariaDB 90+3 / RD21 6 / admission 1 / Linux 8, Python 83 offline +14 real Docling, and native exports with their actual source/runtime/process identities. These lanes are not added into one total. Older broad browser evidence remains historical. The approved S01 36/36 per platform re-evaluated existing documents; original Windows 28/Linux 20 failures are preserved. No new PDF was generated.
 ## Inventory and retained compatibility
 The [nineteen-entry inventory](../../automation/handoffs/pre-phase10/CLEANUP_INVENTORY.md) and preserved draft remain the detailed retain register, including historical purpose, consumers, preservation IDs, proposed tests and risks. The table below reconciles every external inventory category and records the additional concrete candidate. An active consumer defeats deletion eligibility; no exhaustive repository-wide absence claim is made for the retained areas.
 | Required category | Current evidence / disposition |
 | --- | --- |
 | Old page components | CLEAN-01/08: `App.tsx:61,67,441,446` lazy-loads the current CV editor and admin processing page. **Retain**; names/age do not establish supersession |
 | Superseded layouts | CLEAN-06/07: `DashboardView.tsx:20–22,333,367` uses layout state, editor and grid together. **Retain** show/hide/save/reset/conflict/navigation and persisted schema-2 geometry |
 | Old CV Editor implementations | CLEAN-01/03: builder routes and gallery/customisation consumers remain active. **Retain** blank/inherit, history, undo, settings and entitlements |
 | Obsolete CV Import screens | CLEAN-04/05: `CareerProfilePage.tsx:410,447,868` separates old-run review/accept from Docling review; `ProfileCvController.cs:270` still exposes the paired accept action. **Retain** both paths |
 | Unused document components | CLEAN-02/10/12: thumbnail is imported/rendered by gallery and library; renderer design-version branches and `ApplicationAssetsService` revision-aware writers remain active. **Retain** |
 | Duplicated styling | CLEAN-16: app MUI styling, fixed document CSS, sandboxed previews and RGL CSS have distinct consumers. No duplicate consolidation is proven. **Retain** |
 | Unused design tokens | CLEAN-16: `ThemeProvider.tsx` uses `CssBaseline`/`getTheme`; no unused-token proof. **Retain** |
 | Dead hooks/utilities | CLEAN-07/19: dashboard layout hook is imported; duplicate reminder-read optimisation remains unmeasured. **Retain**, no performance change nominated |
 | Unused frontend routes | CLEAN-09: all 34 remain registered; `/kanban`, `/correspondence/review`, `/applications/:id` retain explicit redirect behavior. **Retain** bookmarks, query/hash/state and owner boundaries |
 | Unreferenced API endpoints | CLEAN-05/11/12: paired legacy accept UI/API, canonical mapper and revision-aware document service remain. External-consumer absence is unproved. **Retain** endpoints/services/DTOs/mappings |
 | Obsolete feature flags | CLEAN-15: `cv_import_ai.py:20` reads `CV_IMPORT_AI_ENABLED`, default false; accepted optional adapter is disabled/disconnected. Withholding is not obsolescence. **Retain disabled** |
 | Unused dependencies | CLEAN-13/14/17: RGL JS/CSS imports at `DashboardGrid.tsx:4,7–8`; existing provider/parser/runtime/tooling consumers remain. No package removal nominated; runtime/test/scripts/Docker/platform census would be required for one |
 | Old localisation keys | CLEAN-16: `I18nProvider.tsx:67` indexes `translations[language][key]` with fallback. Dynamic-key absence is unproved. **Retain** EN/Bokmål catalogues |
 | Deprecated test fixtures | CLEAN-18: Jest roots/transform and Playwright `testDir` remain configured; historical PDF/old-run/provider/revision fixtures are acceptance consumers. No fixture is nominated |
 | Dead asset references | CLEAN-16/18: layout references favicons/manifest; manifest references both logo sizes; landing page references all three mockups. **Retain** those assets. Additional unreferenced stylesheet candidate CLEAN-20 below |
 ### CLEAN-20 — Original CRA `job-tracker-ui/src/App.css`
 **Nominate for P10-01 only; do not remove during assessment.** Historical purpose: initial Create React App demonstration styling, present since `2e8a29b` (first commit). Contents: `.App`, `.App-logo`, `.App-header`, `.App-link`, reduced-motion-aware logo animation and `App-logo-spin`; 38 lines / 602 current worktree bytes. Git blob: `74b5e053450a48a6bdb4d71aad648e7af821975c`. Worktree SHA256: `61f6c43a638172676cd2813c94dc4db88f6cf73faec19d0cd116b1ff19e46efc`.
 Unused evidence uses several independent boundaries:
 1. Case-insensitive `rg` across frontend, API, scripts, sidecar and deploy sources finds the distinctive selectors/keyframe only inside this file, and no `App.css` consumer. A separate tracked `git grep` likewise finds no filename consumer. There are no application-local unstaged/untracked additions at entry.
 2. Inspected actual build entry chain: `app/page.tsx` → `app/[[...slug]]/ClientShell.tsx` (literal dynamic import) → `src/ClientApp.tsx` → `src/App.tsx` → current views/layout. `app/layout.tsx:4` imports **`index.css`**, which is retained. `ThemeProvider.tsx` owns active MUI/CssBaseline styling. App source and shell do not use the CRA root classes.
 3. Inspected `next.config.js`: static export plus development rewrite, no source-directory/glob CSS loader or additional injection. Script/config searches show no `require.context`/`import.meta.glob` CSS ingestion. Jest mocks explicitly imported styles; it does not load this file itself. Package scripts invoke the current Next/Jest/ESLint/TypeScript tools.
 4. Inspected delivery boundaries: frontend Dockerfile builds then copies only `/app/out` to nginx; nginx serves that output, and the local export server resolves only `out/`. `src/App.css` is outside public assets and has no exported/source-file URL contract. It is not document CSS, an API payload, font or stored settings format. No database inventory is required to remove this unserved source stylesheet; no persisted record is modified.
 Current consumers/replacement: **none found; no replacement needed**. Preserve the already-active `index.css`, `theme.ts`, `ThemeProvider.tsx`, RGL styles, renderer styles and licensed fonts. Affected preservation review: PRES-E01–E09 (shared UI/theme/responsive/accessibility assurance); all other 48 groups and all 34 routes remain unchanged. Removal risk: **LOW**, contingent on unchanged candidate/entry/config identity and successful affected checks. Runtime/build-size improvement is **NOT MEASURED**; an unbundled source file does not imply a smaller runtime bundle.
 ## Data, backend and SQLite implications
 Career Profile remains canonical. Preserve CV overrides and null-as-inherit, explicit blank flags, current-master history semantics, old stored CV formats/design-version-1 rendering, submitted/frozen CV/letter HTML/settings/binaries and application associations. Cover-letter writers continue under `JobApplication.Version` and `ApplicationAssetsService`; retain generic null-clear versus draft null-unchanged, no-op, restore-as-new, attachment flags, owner filtering and transaction/RD21 stale-write/rollback/retry protections. Keep historical extraction runs and paired review/accept DTOs. No data migration, schema change, writer consolidation or route transition is proposed.
 Reviewed MariaDB standardisation [README](../../database/mariadb-standardisation/README.md), [acceptance](../../database/mariadb-standardisation/ACCEPTANCE.md) and [six-stage SQLite retirement](../../database/mariadb-standardisation/SQLITE_RETIREMENT.md). Actual MariaDB coverage does not establish installation inventory, full-fidelity export/isolated restore/transfer, complete harness parity, approved cutover/rollback-after-writes or retention sign-off. **SQLite retirement remains REMOVAL NO-GO as a separate initiative.** Keep provider packages/helpers/branches, partial export tools and immutable migrations. It is not a prerequisite for unrelated stylesheet cleanup. No MariaDB upgrade is proposed.
 ## Proposed P10-01 scope — CLEAN-20 only
 Approval requested for this exact candidate at application baseline `fc5b9d377199ce51f480a920a3772108094929e3`, plus this Markdown-only assessment descendant. Before acting, require a clean published assessment checkpoint, unchanged application/build/test inputs and the exact candidate blob above. If a consumer/config/source change appears, stop and reassess rather than broadening approval.
 Allowed implementation after explicit approval:
 - Delete only `job-tracker-ui/src/App.css` with the patch workflow. Update this phase's evidence, TODO and continuity Markdown. No caller, export, fixture, configuration, dependency, API, route, data, renderer, font or localisation change is expected or approved.
 - Recheck filename/selectors, static/dynamic entry and delivery boundaries, 57 IDs/34 routes and exact diff scope. Run existing frontend `typecheck`, `lint` and `build` using the unchanged lockfile and an isolated local dependency/build tree. Dependencies are absent in this worktree today; restore only the existing lock if needed in the authorised implementation, without upgrades or shared-worktree edits.
 - Run existing `landing-presentation.spec.ts` (both EN/NB cases cover light/dark at 320/390/768/1440) and focused `smoke.spec.ts` cases `public plans stay honest, responsive and keyboard accessible`, `login establishes an authenticated session`, and `Career Workspace loads from the authenticated application shell`, with zero retries, exact discovered membership, fresh isolated fixtures/static output and native exits. This is a candidate regression sample, not a full suite or human accessibility acceptance. Do not run model/provider operations or additional PDF-producing smoke cases.
 - Reuse unchanged backend/provider/sidecar/PDF evidence with source checks. Do not rerender PDFs, reopen approved metrics or rerun thousands of tests for this unimported file. Broader phase acceptance still requires the complete applicable P10-04/P10-05 programme; significance or affected-source changes require appropriate full suites.
 - Run `graphify update .` as required after a code change, with AST-only/local operation. Graph absence is a known tooling limit: if the installed update cannot operate without a graph, record its actual result and the maintenance limitation; do not rebuild another worktree, fetch an extractor or add graph/orchestration infrastructure under this approval. Graph maintenance is not product-regression evidence.
 - Commit the validated candidate checkpoint, normally push `feature/phase10-cleanup`, and independently compare its remote SHA. Publication failure is a real gate, not permission to repair Gitea or bypass hooks.
 Rollback: revert the single implementation commit, restoring the exact original stylesheet blob; documentation records the reversal. No database restore, data rewrite, redirect or compatibility migration is needed. Failed build/browser/source-scope evidence prevents acceptance. Do not waive failed assertions, remove fixtures or extend the patch to make unrelated checks pass.
 This approval would cover **P10-01/CLEAN-20 only**. It would not authorise P10-02, further removals or later initiatives. Subsequent candidate-specific implementation gates remain. When no additional safe candidate is proven, report that result and retain the code.
 ## Limitations, decisions and stop
 This is a bounded cleanup inventory with one positively analysed stylesheet nomination, not exhaustive dead-code/package/API/locale-key/asset non-use proof. Historical CV/old-run/provider runtime behavior was not freshly executed. No source/data loss or performance improvement is claimed. Native package schemas/counters were not freshly re-parsed by the full branch-specific handoff verifier; fresh checks above cover byte integrity, source identity, group states and route membership only.
 Retained independent debt: physical device/AT/contrast/proficient EN-NB/printing **NOT TESTED**; CV-model qualification **BLOCKED**, adapter disabled; deterministic PDF recall and source-review burden **PARTIAL**; canonical-only generic-AI context limitation retained; Python vendor advisory coverage **INCOMPLETE/CONDITIONAL**; hosted CI/isolation **BLOCKED/UNVERIFIED**; MySqlConnector/TLS, native image/parser production isolation, filesystem/off-disk backup/restore and deployed identity remain release qualifications. No fresh advisory search, live AI, licensed-provider or production access occurred.
 | Decision | Current result |
 | --- | --- |
 | P10-00 direct assessment | **COMPLETE** within the authorised documentation/inspection scope |
 | P10-00 checkpoint publication | **PASSED**: subsequent normal push and independent readback at `1692142295950e390a4cf807d9df86cc5cf96290`; previous pre-receive failures remain historical |
 | CLEAN-20 static deletion eligibility | **NOMINATED**, with exact implementation verification and owner gate above |
 | P10-01 implementation | **AWAITING_APPROVAL** of the exact candidate scope; publication prerequisite satisfied |
 | Phase 10 complete acceptance | **NO-GO / NOT YET ESTABLISHED**; P10-01–05 not complete |
 | Redesign development completion | Existing **CONDITIONAL GO** remains scoped; final cleanup acceptance not established |
 | Post-Phase-10 PRODUCT-REVIEW-01 readiness | **NO-GO** until Phase 10 is accepted and applicable entry conditions are satisfied |
 | Production release | **NO-GO** |
 **STOP here. Request approval of P10-01/CLEAN-20 only.** The orchestrator must remain paused. The deferred CV-import overhaul and personal portfolio website remain outside this roadmap execution task. [HANDOFF.md](HANDOFF.md) records continuity, exact checkpoints and the later source order; later prompt packs must be read completely before their workstream is entered.
@@ -1,3 +1,13 @@
 ## Direct Phase 10 — 2 November 2026
 - [x] P10-00: preserve/review the staged draft, verify baseline/evidence applicability and complete the [direct assessment](../redesign/phase-10/P10-00.md).
 - [x] Publication gate: normal push and exact remote readback succeeded at `1692142` after the earlier Gitea failure; no hook bypass or server repair. Further progress is tracked in [the direct-roadmap register](../direct-roadmap/ROADMAP_STATUS.md).
 - [ ] Owner gate: explicit approval of P10-01/CLEAN-20 only (`job-tracker-ui/src/App.css`), with the assessment's exact verification/rollback boundaries.
 - [ ] After approval only: implement and qualify that candidate; commit, publish and independently verify the checkpoint. Stop at subsequent candidate/entry gates.
 - [ ] P10-02–05 and later roadmap: preserve contracts and follow authoritative order from [continuity](../redesign/phase-10/HANDOFF.md). No later implementation is currently authorised.
 The autonomous backlog orchestrator remains paused and untouched. Earlier TODO entries retain their historical dates and decisions.
 ## Phase7 final acceptance — 21 October 2026
 P7-00–P7-12 implemented scope complete, CONDITIONAL GO; full1060backend/899frontend/351browser plus23contracts/56offline-sidecar passing. See [final report](../redesign/phase-7/p7-12/FINAL_ACCEPTANCE.md). Retain manual/provider/output/reliability qualifications and production NO-GO. Phase8 planning handoff conditional; implementation not started.
Author	SHA1	Message	Date
cesnimda	36a355ea54	docs(roadmap): add recovery and localisation findings	2026-11-02 11:42:02 +01:00
cesnimda	c2ef6320e3	docs(roadmap): record verified publication and partial research checkpoints	2026-11-02 06:09:44 +01:00
cesnimda	1692142295	docs(phase10): record continuation and repeated publication blocker	2026-11-02 01:16:25 +01:00
cesnimda	8cdff28f07	docs(phase10): record blocked checkpoint publication	2026-11-02 01:02:03 +01:00
cesnimda	7ba1367fd2	docs(phase10): complete direct P10-00 assessment	2026-11-02 01:00:58 +01:00