docs(cv): publish qualified acceptance and import handoff
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# CV-UX verification execution plan
|
||||
|
||||
**Final status, 26 October:** execution completed. [ACCEPTANCE.md](ACCEPTANCE.md) and [EVIDENCE.json](EVIDENCE.json) are authoritative for current results. The prospective instructions below and dated checkpoint notes are retained for provenance; statements that a feature adapter or collector is not yet implemented are historical. Current helper: `linux-run.py`; offline checks: 11/11; actual successor: `linux-final-02`. All shell reproduction examples use `rtk proxy`. Live-model checks remain BLOCKED at the owner's explicit instruction.
|
||||
|
||||
Prepared 25 October 2026 from the existing Phase 9 reproduction instructions and runners. This document is a prospective execution plan, not passing evidence. The parent owns the final source freeze, serial execution, reconciliation and publication. Do not execute while workers are changing backend/frontend sources. Preserve every failed or superseded attempt.
|
||||
|
||||
## Fresh identity and lifecycle
|
||||
@@ -37,8 +39,8 @@ The model-disable variables retain the established local application regression
|
||||
Root cwd:
|
||||
|
||||
```powershell
|
||||
rtk C:/Users/Connor/.dotnet/dotnet.exe test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --configuration Release --no-restore --logger 'trx;LogFileName=backend.trx' --results-directory "$cvUxRoot/backend"
|
||||
rtk C:/Users/Connor/.dotnet/dotnet.exe build JobTrackerApi/JobTrackerApi.csproj --configuration Release --no-restore
|
||||
rtk proxy C:/Users/Connor/.dotnet/dotnet.exe test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --configuration Release --no-restore --logger 'trx;LogFileName=backend.trx' --results-directory "$cvUxRoot/backend"
|
||||
rtk proxy C:/Users/Connor/.dotnet/dotnet.exe build JobTrackerApi/JobTrackerApi.csproj --configuration Release --no-restore
|
||||
```
|
||||
|
||||
The backend test build also creates the Release PDF process stub required by the separate admission config. If locked restore is actually required, record that separate command/outcome; never treat a restore-only exit as a test result.
|
||||
@@ -46,10 +48,10 @@ The backend test build also creates the Release PDF process stub required by the
|
||||
UI cwd `E:/Storage/Projects/Active/Job tracker/job-tracker-ui`:
|
||||
|
||||
```powershell
|
||||
rtk node node_modules/jest/bin/jest.js --runInBand --json "--outputFile=$cvUxRoot/frontend.json"
|
||||
rtk node node_modules/typescript/bin/tsc --noEmit --incremental false
|
||||
rtk node node_modules/eslint/bin/eslint.js . --max-warnings=0
|
||||
rtk node --max-old-space-size=4096 node_modules/next/dist/bin/next build
|
||||
rtk proxy node node_modules/jest/bin/jest.js --runInBand --json "--outputFile=$cvUxRoot/frontend.json"
|
||||
rtk proxy node node_modules/typescript/bin/tsc --noEmit --incremental false
|
||||
rtk proxy node node_modules/eslint/bin/eslint.js . --max-warnings=0
|
||||
rtk proxy node --max-old-space-size=4096 node_modules/next/dist/bin/next build
|
||||
```
|
||||
|
||||
Record fresh native totals rather than fixing expected counts to the historical backend 1130/frontend 935. Compare discovery/membership with baseline; every added/removed/renamed case needs an explicit source-backed explanation. Do not add earlier focused worker checks to the full-suite totals.
|
||||
@@ -60,7 +62,7 @@ Keep UI cwd and the environment above. First retain ordinary discovery:
|
||||
|
||||
```powershell
|
||||
$env:PLAYWRIGHT_JSON_OUTPUT_NAME = "$cvUxRoot/discovery.json"
|
||||
rtk node node_modules/@playwright/test/cli.js test --list --retries=0 --reporter=list,json
|
||||
rtk proxy node node_modules/@playwright/test/cli.js test --list --retries=0 --reporter=list,json
|
||||
```
|
||||
|
||||
Execute four complete shards **one at a time**, with process metadata/logs and a separate native JSON for each:
|
||||
@@ -79,7 +81,7 @@ Execute each configuration below separately using this exact command pattern, se
|
||||
|
||||
```powershell
|
||||
$env:PLAYWRIGHT_JSON_OUTPUT_NAME = "$cvUxRoot/$cvUxLane.json"
|
||||
rtk node node_modules/@playwright/test/cli.js test --retries=0 --reporter=list,json "--output=$cvUxRoot/$cvUxLane-results" "--config=$cvUxConfig"
|
||||
rtk proxy node node_modules/@playwright/test/cli.js test --retries=0 --reporter=list,json "--output=$cvUxRoot/$cvUxLane-results" "--config=$cvUxConfig"
|
||||
```
|
||||
|
||||
| Lane | Configuration relative to UI cwd | Historical expected membership (verify fresh) |
|
||||
@@ -102,7 +104,7 @@ The six contract lanes historically total 23; RD21/diagnostics/volume lanes rema
|
||||
The letter-persistence worker owns provider qualification. Its earlier 47-case all-writer gate predates document design/migration; it is not the final additive-schema gate. Its later checkpoint at `.artifacts/cv-ux-01/letter-design-mariadb` reported 56/56 passing with the additive migration and provider downgrade/reupgrade preservation, and positive generated-project cleanup. That is separately reported worker evidence, not a fresh parent frozen-source full regression. The guarded runner already supports fresh output and generated projects/schemas:
|
||||
|
||||
```powershell
|
||||
rtk python scripts/mariadb-integration.py --output "$cvUxRoot/mariadb"
|
||||
rtk proxy python scripts/mariadb-integration.py --output "$cvUxRoot/mariadb"
|
||||
```
|
||||
|
||||
Run only after final source freeze and record actual new TRX membership/count, exact pinned image/server 12.2.2, schema ownership and positive cleanup. The runner's default mode creates a generated `jobtracker-it-<uuid>` project, loopback random port and tmpfs test data, then removes only its owned test service. Do not substitute SQLite or developer `mariadb-dev`; do not use broad prune/down -v. An earlier worker checkpoint may support development sequencing but cannot be added to this fresh full provider total.
|
||||
@@ -114,7 +116,7 @@ Existing MariaDB browser/HTTP-observation/15-minute workload helpers have fixed
|
||||
Ordinary shards produce the existing 16-fixture fidelity corpus and four settings-browser cases containing eight settings states in the fresh Windows roots above. Stop all producers before proof. Root cwd, use the bundled Python (verify available; retained installation path shown):
|
||||
|
||||
```powershell
|
||||
rtk C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B docs/redesign/phase-9/p9-requal-01/pdf-proof.py --platform windows --fidelity-root "$cvUxRoot/windows/fidelity" --settings-root "$cvUxRoot/windows/settings-fidelity" --output "$cvUxRoot/windows/proof" --record "$cvUxRoot/windows/native-pdf.json"
|
||||
rtk proxy C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B docs/redesign/phase-9/p9-requal-01/pdf-proof.py --platform windows --fidelity-root "$cvUxRoot/windows/fidelity" --settings-root "$cvUxRoot/windows/settings-fidelity" --output "$cvUxRoot/windows/proof" --record "$cvUxRoot/windows/native-pdf.json"
|
||||
```
|
||||
|
||||
`pdf-proof.py` accepts fresh roots unchanged and checks exact 16/36-page plus 8/24-page membership using `scripts/verify-cv-fidelity.py`. Retain original oracle SHA256 `64f82e622cc11483c33307d987e969f6cf27f82ab6bdbd72c2aeb1bfbceade87`; never edit tolerances or fixture expectations to make this feature pass. A real regression stays FAIL with artifacts.
|
||||
@@ -143,7 +145,7 @@ Set fresh `CV_FIDELITY_OUTPUT`, `CV_SETTINGS_FIDELITY_OUTPUT`, `LETTER_FIDELITY_
|
||||
After successful Linux producers and positive cleanup, root cwd:
|
||||
|
||||
```powershell
|
||||
rtk C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B docs/redesign/phase-9/p9-requal-01/pdf-proof.py --platform linux --fidelity-root "$cvUxRoot/linux/fidelity" --settings-root "$cvUxRoot/linux/settings-fidelity" --output "$cvUxRoot/linux/proof" --record "$cvUxRoot/linux/linux-pdf.json"
|
||||
rtk proxy C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B docs/redesign/phase-9/p9-requal-01/pdf-proof.py --platform linux --fidelity-root "$cvUxRoot/linux/fidelity" --settings-root "$cvUxRoot/linux/settings-fidelity" --output "$cvUxRoot/linux/proof" --record "$cvUxRoot/linux/linux-pdf.json"
|
||||
```
|
||||
|
||||
## Separate letter physical fidelity
|
||||
@@ -153,8 +155,8 @@ The new `e2e/cover-letter-document-fidelity.spec.ts` is a real authenticated pro
|
||||
Its measurements use the existing oracle's schema. The unchanged lower-level oracle supports arbitrary corpus size, so **no new PDF oracle or widened tolerances are needed**. Run separately after each platform's producers stop:
|
||||
|
||||
```powershell
|
||||
rtk C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B scripts/verify-cv-fidelity.py "$cvUxRoot/windows/letter-fidelity"
|
||||
rtk C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B scripts/verify-cv-fidelity.py "$cvUxRoot/linux/letter-fidelity"
|
||||
rtk proxy C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B scripts/verify-cv-fidelity.py "$cvUxRoot/windows/letter-fidelity"
|
||||
rtk proxy C:/Users/Connor/.cache/codex-runtimes/codex-primary-runtime/dependencies/python/python.exe -B scripts/verify-cv-fidelity.py "$cvUxRoot/linux/letter-fidelity"
|
||||
```
|
||||
|
||||
Require exactly the four fixture names `light-en-a4`, `dark-nb-a4`, `light-nb-letter`, `dark-en-letter`, each native result passing without failures, no duplicate/missing marker, matching physical page count/geometry/fonts/colors/safe areas. Retain `fidelity-results.json`, actual PDF page images/comparison images and producer inputs/hashes. Do not add these four documents to either original CV24 count. Review extracted PDF text for full sender email/phone/location, multiline recipient, subject, bold/italic content and final diacritics; marker checks alone do not establish every unmarked string. No physical printer/human fidelity claim follows from this oracle.
|
||||
|
||||
Reference in New Issue
Block a user