Files
jobtrackingapp/docs/pre-phase10-ux/A_ACCEPTANCE.md
T
2026-10-27 07:37:03 +01:00

4.8 KiB

A: blank CV and editor history acceptance

27 October 2026. Corrective branch: codex/cv-builder-blank-undo, from completed CV-QA 4a8c907. Audit/plan checkpoint: 5d4b8f2. This is development qualification; it does not reopen production or live inference.

Implemented

  • New Blank creation contains zero sections and no inherited identity/contact/photo/headline. Profile creation requires explicit section/contact selection. Existing settings without nullable inclusion flags retain legacy behaviour.
  • Editor, shared render resolver, document AI and application matcher agree on selected content. AI rejects an empty source before provider access. No live inference was performed.
  • Empty resolved export returns cv_empty_content before allocating a PDF worker, with English/Bokmål recovery copy. Design changes, save/reload, duplicate and historical restore preserve explicit selection.
  • Session undo/redo includes name and settings, groups focused typing bursts, records structural/design actions, invalidates redo after new edits, preserves history across autosave and rejects history actions during revision conflict. Native text undo remains native; document shortcuts support Ctrl/Cmd+Z, Ctrl+Y and Ctrl/Cmd+Shift+Z outside editable controls.
  • Document loads clear old controls and previews. Late save, preview, restore and history responses are scoped to their editor session. Explicitly selected profile other:n sections are reachable through Add content.

Evidence

Evidence root: .artifacts/pre-phase10-ux/. Original failing runs are retained; overlapping runs are never added together.

Lane Result Evidence / scope
Actual Next development reproduction Both reported defects reproduced runtime-red/; blank inherited four canonical markers; document Ctrl+Z failed for non-text section reorder
Focused backend 108 passed, 0 failed/skipped blank-green/blank-green.trx; resolver, legacy serialization, save/duplicate/restore, empty export allocation, bound AI and matching
Frontend 98 passed in 4 suites, 0 failed/skipped a-ui-qualified.json; includes Strict Mode typing, naming, branch redo, conflicts, document switch, restore isolation and explicit additional profile sections
Development browser 4 passed, 0 failed/skipped/flaky a-browser/results-final.json; EN1440/NB390 blank save/reload/template Apply, UI+API empty-export rejection, unchanged canonical source, persisted section-order shortcuts and native text undo
Accessibility automation Four scoped scans: 0 violations Each retains one serious contrast incomplete; this does not pass manual contrast/AT acceptance
TypeScript Exit 0 tsc --noEmit --incremental false, current source
Focused ESLint Exit 0 Editor/library/types/tests/translations; full lint remains final integration work
MariaDB + RD21 82 passed, 0 failed/skipped a-mariadb-final/mariadb.trx; full repository helper, generated loopback MariaDB12.2.2 schemas, locked restore and cleanup exit0. Includes2 new blank persistence/design/restore, stale-writer and ownership cases

Browser evidence precedes the final additional-section title fallback by one localized catalogue-line change; that addition has its own failing-then-passing frontend test and is also included in the final integrated browser source. No claim of human testing follows from automated widths or screenshot inspection.

Fresh review identified late restore/history isolation and additional profile-section reachability. Both received new RED tests before correction. The catalogue finding was narrowed to actual nonstandard other:n keys: the standard list already includes awards/publications/organisations/references. No standard section was missing. A previous assertion that renaming creates no undo state was updated to verify the new requested transaction and that rejected AI adds no extra history step.

Decisions and limits

Blank creation and undo/redo: development GO. CV integration preservation: conditional; focused legacy and revision paths pass, full regression/PDF qualification remains scheduled on the combined integration branch. B may start after this checkpoint is committed/pushed/remote-verified.

The initial MariaDB run also passed82, but its test binary preceded the fixture correction from an unknown design ID to actual minimal. The final run above rebuilt that source and is authoritative; these runs are not additive. No provider fallback or production connection was used.

Session history is bounded to60 steps and is not restored after refresh; the editor explains this. Historical settings revisions remain available separately. Human accessibility, physical devices, native-language review, contrast and printing remain open. CV-model compatibility/accuracy remain BLOCKED. Production remains NO-GO. Phase10 cleanup has not begun.