cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(cv): publish qualified acceptance and import handoff

Browse Source
This commit is contained in:
cesnimda
2026-10-26 10:37:31 +01:00
parent b1817aa52c
commit 4a0af6273b
10 changed files with 272 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/cv-redesign/CV_IMPORT_HANDOFF.md
+4
View File
@@ -1,11 +1,15 @@
# CV-IMPORT-01 handoff — implementation not started
Final CV-UX application/UI checkpoint: `b1817aa52c604f12df3c875b53b8f4e69fa6f2be`, descending from `28f83df`. [ACCEPTANCE.md](ACCEPTANCE.md) records automated development PASS with conditional overall acceptance, owner-blocked live-model checks and open human/hosted/production gates. The final report/evidence and tested Linux helper correction are published separately from application source. This handoff does not activate CV-IMPORT-01.
This document supplies compatibility requirements from CV-UX-01. It does not authorise or start Docling, model qualification, legacy-parser replacement or Phase10 cleanup.
Career Profile remains the canonical career-data owner. An eventual import must preview and explicitly reconcile facts through the established profile service; it must preserve CV-specific overrides, hidden/order choices, null-as-inherit design settings and existing revisions. CV settings history resolves the current Career Profile; it is not a historical full-profile snapshot.
Cover letters use the parent JobApplication.Version for optimistic concurrency. Every intended writer stages current text, normalized document settings and history through ApplicationAssetsService before the parent transaction commits. Preserve generic null-clear versus draft null-unchanged semantics, no-op acknowledgements, recovery of previously uncovered legacy text, restore-as-new and owner filtering. Do not introduce an independent revision counter or write CoverLetterText directly from import code.
Preserve attachment flags independently: generic/create/application-draft text writers retain the previous `HasCoverLetter` value; only a changed nonempty dedicated letter Save retains its historical promotion behavior. Imported text must not imply an imported attachment. Checklist readiness already considers actual nonempty text. New regression coverage proves both flag values and clear/no-op/restore behavior on SQLite and MariaDB.
Contact/design copies are explicit reviewed snapshots. Imported facts or later CV edits must not silently rewrite saved letters. Historical text-only letters and submitted packages remain readable. New submitted packages freeze letter HTML/settings and CV output; future source changes must not rewrite their bytes. Account/backup portability includes letter design/history.
CV AI proposals are bound to owned source/revision capabilities and reviewed acceptance. Letter AI requires an owned linked CV with actual visible career evidence. Advert requirements, identity/header text and a previous letter do not establish experience. Import text is untrusted data, never model instructions. Reuse the existing approved self-hosted infrastructure; do not infer semantic, GPU or production readiness from CPU compatibility or mocked UI tests.