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

docs(career): record workspace evidence
CI and Deploy / test (pull_request) Failing after 1m35s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details

Browse Source
This commit is contained in:
cesnimda
2026-08-09 19:02:34 +02:00
parent 268b3a07de
commit c201832603
8 changed files with 105 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/work-programmes/decisions.md
+10
View File
@@ -339,3 +339,13 @@
- **Consequences:** term changes appear on the next request; obsolete pending generated learning items auto-complete under existing behavior while done/dismissed decisions remain. The curated vocabulary remains intentionally bounded and test-driven.
- **User approval required:** No; this is the deterministic-first implementation explicitly required by both programmes.
- **Reversible:** Yes. Revert `da1aa8b`; no schema, cache or provider state changes.
## DEC-035 — Career Workspace derives actions from existing domain state
- **Date:** 2026-08-09
- **Decision:** Render one action-oriented overview from the completeness and durable import state already owned by `CareerProfilePage`; load only the separate recent-CV list. Link actions to the existing profile/import anchors, builder and saved-job workflow, and retain extraction Apply/Discard as the sole merge gate.
- **Reason/evidence:** duplicating `/career/profile` and `/profile-cv/runs` requests in the route wrapper would create competing loading/polling state. The existing page already has correct durable run, review and version data, while CV variants are a separate bounded list. The old wrapper duplicated headings and explanation without exposing next actions.
- **Alternatives considered:** a second workspace data loader; moving all profile state into a new global store; direct one-click job-CV creation without a job choice; rewriting the profile editor. These add inconsistent state, premature architecture or bypass the established job/application boundary.
- **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.