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

docs(cv): track builder integrity progress
CI and Deploy / test (pull_request) Failing after 1m31s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details

Browse Source
This commit is contained in:
cesnimda
2026-08-09 19:10:33 +02:00
parent b58cc19d54
commit df89a69306
7 changed files with 85 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/work-programmes/decisions.md
+10
View File
@@ -349,3 +349,13 @@
- **Consequences:** the page presents concise state-aware navigation without changing API, profile persistence or imported-data approval semantics. Browser and production verification remain before `DONE`; deeper builder/job interaction remains in CAREER-002/JOBS-001.
- **User approval required:** No; this is the smallest cohesive implementation of the approved programme requirement.
- **Reversible:** Yes. Revert the CAREER-001 implementation commit; no data/configuration migration exists.
## DEC-036 — CV autosave uses revision ordering and explicit discard warnings
- **Date:** 2026-08-09
- **Decision:** Keep the existing debounced variant autosave API, but track the latest name/settings and a monotonic client revision. Only the newest request may update the visible save state. Offer an explicit retry and block route/unload navigation until the user chooses to discard pending or failed edits.
- **Reason/evidence:** the editor already has versioned server saves, but a route change during the debounce and overlapping responses could lose work or falsely display `Saved`. Blank names were ignored by the backend while remaining blank in the UI. The existing API is sufficient; the defect is client coordination and feedback.
- **Alternatives considered:** replace autosave with a manual-only form; add a queue/schema; extend timeouts; silently flush during unload; refactor variant versioning. These regress the working interaction, add unrelated infrastructure or cannot reliably complete during page teardown.
- **Consequences:** users receive a native discard decision for in-app navigation and browser-standard warning on unload. A blank name stays unsaved until corrected. The deeper builder redesign and browser checks remain CAREER-002 work.
- **User approval required:** No; this is a reversible data-loss safeguard within the approved programme.
- **Reversible:** Yes. Revert `b58cc19`; server variants and version history require no migration.