chore(phase10): remove approved unused CRA stylesheet

This commit is contained in:
cesnimda
2026-11-02 21:44:05 +01:00
parent 36a355ea54
commit 78f7396adb
7 changed files with 95 additions and 38 deletions
+10
View File
@@ -0,0 +1,10 @@
# Direct execution continuation
2 November 2026. Latest owner authorisation permits independent ordinary application work, preserves genuine gates, and explicitly approves CLEAN-20 only. Older statements requiring that approval are superseded.
- Phase 10: CLEAN-20 implemented and verified, see ../redesign/phase-10/P10-01.md. Publication pending exact receipt. P10-02–05 remain open; no extra cleanup approved.
- Release readiness: backup connection-parser fix published and read back at `f19e7ebf4aeae350b43fa84cf115c393030280f0` on codex/release-backup-parser, in release-readiness-discovery worktree. 31 offline tests passed; no live restore/deployment qualification.
- Product modernisation: isolated codex/product-modernisation worktree, latest local checkpoint `192095b8`; design prototypes and user choices retained under docs/product-modernisation. A1 dashboard + D1 foundation + B1 tracking, CV editor left/preview right, context right; overview-first Career Profile; agenda/month calendar including application deadlines; automation under Settings. No final full-application implementation approval. Prototype commits not remotely published.
- I18N: codex/i18n-accessible-labels branch created from `55adc1d`; implementation pending. Earlier translation audit counts remain historical; do not claim all dynamic calls fixed.
Next authorised work: publish validated CLEAN-20 normally and independently verify ref, then P10-02 retained-compatibility review and eligible independent fixes. Preserve primary/pre-P10 worktrees and all source-defined gates. No orchestrator commands, keys, configuration or queue changes; no main merge, models or production deployment. Full security/product/release acceptance remains incomplete.
+4
View File
@@ -1,5 +1,9 @@
# Direct-roadmap continuity
## Latest checkpoint — CLEAN-20 explicitly approved and verified
Owner replied **"Approve CLEAN-20 only"** in this chat. This supersedes historical approval-pending statements below, without authorising any other deletion. [P10-01](P10-01.md) records the exact one-file removal, fresh typecheck/lint/build and 5/5 browser results, preserved 34 routes/57 groups, and 1,279 unchanged source files. Publication receipt follows in the next checkpoint. No final Phase 10 or production acceptance implied. Resume with this latest section, not the superseded controller/publication history below.
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
+2
View File
@@ -1,5 +1,7 @@
# P10-00 — Direct assessment and deletion eligibility
**Subsequent implementation:** owner explicitly approved CLEAN-20 only. The approved candidate has now passed its required checks; see [P10-01](P10-01.md). Approval-pending descriptions below are retained as assessment history, not the latest state.
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
+39
View File
@@ -0,0 +1,39 @@
# 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.
@@ -0,0 +1,40 @@
{
"scope": "P10-01 CLEAN-20 only",
"approval": "Owner chat: Approve CLEAN-20 only",
"baselineCommit": "36a355ea54a2357907ac5a5bf655d6946388b202",
"deletedPath": "job-tracker-ui/src/App.css",
"deletedBlob": "74b5e053450a48a6bdb4d71aad648e7af821975c",
"sourceManifestFiles": 1280,
"sourceManifestMatched": 1279,
"sourceManifestMissing": [
"job-tracker-ui/src/App.css"
],
"sourceManifestMismatched": [],
"routes": 34,
"preservationGroups": 57,
"checks": {
"typecheck": "PASSED exit 0",
"lint": "PASSED exit 0",
"frontendBuild": "PASSED exit 0",
"apiBuild": "PASSED exit 0, 0 warnings/errors",
"browser": "PASSED 5/5, zero skips/retries/flaky"
},
"browserStats": {
"startTime": "2026-11-02T20:41:52.224Z",
"duration": 44532.167,
"expected": 5,
"skipped": 0,
"unexpected": 0,
"flaky": 0
},
"browserMetadata": {
"isolatedDataRoot": "C:\\Users\\Connor\\AppData\\Local\\Temp\\jobtracker-e2e-4580-mvzq5nbx",
"actualWorkers": 1
},
"nativeReportSha256": "3b051b65fccbb79b298989ad52987c6e1c4c9fe60ff4e7d8796a40ca2e060bd1",
"compressedReportSha256": "baf659c51c4f412f30b8971588ef84c3863830b64afd5cbc874800172f95c3c0",
"limitations": [
"candidate regression sample, not full Phase 10 acceptance",
"no new PDF/model/provider/production qualification"
]
}
-38
View File
@@ -1,38 +0,0 @@
.App {
text-align: center;
}
.App-logo {
height: 40vmin;
pointer-events: none;
}
@media (prefers-reduced-motion: no-preference) {
.App-logo {
animation: App-logo-spin infinite 20s linear;
}
}
.App-header {
background-color: #282c34;
min-height: 100vh;
display: flex;
flex-direction: column;
align-items: center;
justify-content: center;
font-size: calc(10px + 2vmin);
color: white;
}
.App-link {
color: #61dafb;
}
@keyframes App-logo-spin {
from {
transform: rotate(0deg);
}
to {
transform: rotate(360deg);
}
}