Files
jobtrackingapp/docs/redesign/phase-10/P10-01.md
T

40 lines
4.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# P10-01 — CLEAN-20 implementation
2 November 2026. Owner explicitly answered **"Approve CLEAN-20 only"** to the candidate-specific proposal. Implemented only removal of the unused 38-line `job-tracker-ui/src/App.css`, blob `74b5e053450a48a6bdb4d71aad648e7af821975c`. No caller, route, dependency, lockfile, test, API, database schema, document renderer, localisation or active theme changes.
## Entry and preservation
Clean `feature/phase10-cleanup` entered at `36a355ea54a2357907ac5a5bf655d6946388b202`; independent remote readback matched. Candidate blob matched exactly. Application/build/test inputs unchanged from assessed `fc5b9d3` baseline before this deletion. Reference search found distinctive selectors only in the candidate; source entry/config/delivery boundary evidence in P10-00 remains applicable because those bytes did not change.
Fresh source-manifest comparison: 1,279 matching files, sole expected missing file App.css, zero mismatches. 34 distinct route identities match the preserved register. All 57 preservation groups remain present, with prior 56 PARTIAL / one DEFERRED states unpromoted. No CV, letter, legacy import, provider or RD21 contract changed.
## Fresh checks
| Check | Result |
| --- | --- |
| Isolated frontend dependency restoration | PASS: `npm ci --offline --no-audit --no-fund`, unchanged lockfile, 825 packages; no upgrades |
| Frontend typecheck | PASS, exit 0 |
| Frontend lint | PASS, exit 0, max warnings 0 |
| Static production frontend build | PASS, exit 0; local test API URL; fresh isolated output |
| Local API restore/build for browser fixture | PASS with existing SDK 9.0.317; Release build zero warnings/errors |
| Exact browser discovery | Five cases in two files |
| Browser execution | PASS 5/5, zero skips/flaky/retries; native exit 0; 44.5 seconds |
| Route/preservation/source scope | PASS as above |
| Graphify | AST-only update attempted/completed status recorded in handoff; generated graph untracked |
Browser cases: both EN/NB `landing-presentation` cases (light/dark at 320/390/768/1440), public-plan responsive/keyboard smoke, authenticated login, and Career Workspace shell. Existing Playwright config creates a fresh temporary SQLite fixture, disables AI/import/provider-alert workers, refuses server reuse and serves this worktree's prebuilt static export. Fixture-only schema initialisation is not a production migration. No live models/providers or PDF-producing tests were invoked.
Native browser report and source/check summary: [clean20-evidence/SUMMARY.json](clean20-evidence/SUMMARY.json), [compressed native report](clean20-evidence/browser-native.json.gz). This is a candidate regression sample, not full regression or Phase 10 acceptance. Unchanged backend/provider/sidecar/PDF evidence remains historical and source-bound; no accepted PDF criterion reopened.
## Failed setup attempts and retained limitations
System `dotnet` failed to resolve pinned SDK; used repository-documented existing `C:/Users/Connor/.dotnet/dotnet.exe` and DOTNET_ROOT. First no-restore API build failed because fresh worktree lacked assets; normal locked restore succeeded, followed by successful build. No project/runtime configuration changed. Offline npm restore emitted deprecation warnings and an unapproved optional unrs-resolver install-script notice; no install-script approval or dependency change made. Required lint/type/build/browser subsequently passed.
Fresh fixture startup emitted existing SQLite migration transaction/rebuild warnings and local DataProtection unencrypted-key warning. These were not hidden or repaired under CSS scope. They do not qualify backup/restore, provider parity, hosted CI, production secrets or deployed services. Graph tool lacks optional SQL/PDF extractors; no installation attempted.
## Rollback and remaining gates
Revert this candidate implementation commit to restore the exact original stylesheet; no data restore needed. A failing required candidate check would prevent acceptance and trigger restoration; all required candidate checks passed.
P10-01/CLEAN-20 implementation is verified. Required publication must be independently read back before published completion is claimed. P10-02–05 and overall Phase 10 acceptance remain open; no additional deletion is approved or invented. Next: retained CV/document compatibility review under P10-02, followed by the required downstream qualification programme. Orchestrator remains paused/untouched; no main merge or deployment.