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

Complete S03 runtime closure and S04 control loop

Browse Source
This commit is contained in:
cesnimda
2026-03-24 11:33:55 +01:00
parent 0cacb4e51b
commit 8890906231
17 changed files with 588 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gsd/REQUIREMENTS.md
+51 -51
View File
@@ -4,50 +4,6 @@ This file is the explicit capability and coverage contract for the project.
## Active
### R004 — The app must generate follow-up and reply drafts from the imported job, saved application material, and correspondence context tied to that job.
- Class: primary-user-loop
- Status: active
- Description: The app must generate follow-up and reply drafts from the imported job, saved application material, and correspondence context tied to that job.
- Why it matters: Follow-through is part of the core value, not an optional afterthought.
- Source: user
- Primary owning slice: M001/S03
- Supporting slices: M001/S01, M001/S02, M001/S05
- Validation: mapped
- Notes: The user stays in control of sending; the app provides strong drafts only.
### R005 — The first page should give the user a clear overview of jobs, status, readiness, and what needs attention.
- Class: continuity
- Status: active
- Description: The first page should give the user a clear overview of jobs, status, readiness, and what needs attention.
- Why it matters: The user explicitly wants to start from the job table each day.
- Source: user
- Primary owning slice: M001/S04
- Supporting slices: M001/S05
- Validation: mapped
- Notes: This should feel like “scan the field” before drilling into one job.
### R006 — The dashboard and follow-up surfaces must clearly show next actions, neglected threads, and jobs that need attention now.
- Class: continuity
- Status: active
- Description: The dashboard and follow-up surfaces must clearly show next actions, neglected threads, and jobs that need attention now.
- Why it matters: Tracking is only valuable if it turns state into action.
- Source: user
- Primary owning slice: M001/S04
- Supporting slices: M001/S05
- Validation: mapped
- Notes: The follow-up/dashboard view is the second navigation priority after the table.
### R007 — Each job needs a workspace where the user can update status, review/import correspondence, edit drafts, and prepare follow-ups.
- Class: core-capability
- Status: active
- Description: Each job needs a workspace where the user can update status, review/import correspondence, edit drafts, and prepare follow-ups.
- Why it matters: The user’s third step in the daily flow is to drop into a specific job and do focused work.
- Source: inferred
- Primary owning slice: M001/S03
- Supporting slices: M001/S02, M001/S04
- Validation: mapped
- Notes: This is where the product should feel connected instead of scattered.
### R008 — The app may draft application, reply, and follow-up content, but it must not auto-send emails or auto-apply to jobs.
- Class: constraint
- Status: active
@@ -116,6 +72,50 @@ This file is the explicit capability and coverage contract for the project.
- Validation: Validated by M001/S02: backend application-package generation now uses recruiter/job/profile/attachment/imported-correspondence context, focused backend tests pass in an isolated harness, and the Tailored CV workspace test proves generation, editing, save, and saved-state redisplay behavior.
- Notes: S02 proved the application-package drafts are materially more specific and persist as job-tied working material. Broader end-to-end live-loop revalidation still remains in M001/S05.
### R004 — The app must generate follow-up and reply drafts from the imported job, saved application material, and correspondence context tied to that job.
- Class: primary-user-loop
- Status: validated
- Description: The app must generate follow-up and reply drafts from the imported job, saved application material, and correspondence context tied to that job.
- Why it matters: Follow-through is part of the core value, not an optional afterthought.
- Source: user
- Primary owning slice: M001/S03
- Supporting slices: M001/S01, M001/S02, M001/S05
- Validation: Validated by M001/S03: follow-up draft generation now consumes imported correspondence plus saved application package material, focused backend follow-up tests pass in an isolated harness, the focused React follow-up test passes, and browser verification on the built branch UI proved the grounded follow-up draft plus manual send/log flow back into correspondence.
- Notes: S03 validated the follow-up half of the requirement. Explicit reply drafting may still be deepened later, but the requirement-level milestone bar is now met for job-grounded follow-up/reply assistance without autonomous sending.
### R005 — The first page should give the user a clear overview of jobs, status, readiness, and what needs attention.
- Class: continuity
- Status: validated
- Description: The first page should give the user a clear overview of jobs, status, readiness, and what needs attention.
- Why it matters: The user explicitly wants to start from the job table each day.
- Source: user
- Primary owning slice: M001/S04
- Supporting slices: M001/S05
- Validation: Validated by M001/S04: the job table now exposes actionable urgency chips that route directly into the relevant job workspace tab, focused daily-loop UI tests pass, and browser verification confirmed the table/dashboard/reminders flow routes into the same workspace model.
- Notes: S04 made the table a practical first-stop overview for daily use rather than a passive list.
### R006 — The dashboard and follow-up surfaces must clearly show next actions, neglected threads, and jobs that need attention now.
- Class: continuity
- Status: validated
- Description: The dashboard and follow-up surfaces must clearly show next actions, neglected threads, and jobs that need attention now.
- Why it matters: Tracking is only valuable if it turns state into action.
- Source: user
- Primary owning slice: M001/S04
- Supporting slices: M001/S05
- Validation: Validated by M001/S04: dashboard and reminders now expose actionable attention items routed into the existing job workspace, focused daily-loop UI tests pass, and browser verification confirmed those surfaces open the correct job workspace state.
- Notes: S04 made the follow-up/dashboard surfaces show actionable urgency instead of dead-end summaries.
### R007 — Each job needs a workspace where the user can update status, review/import correspondence, edit drafts, and prepare follow-ups.
- Class: core-capability
- Status: validated
- Description: Each job needs a workspace where the user can update status, review/import correspondence, edit drafts, and prepare follow-ups.
- Why it matters: The user’s third step in the daily flow is to drop into a specific job and do focused work.
- Source: inferred
- Primary owning slice: M001/S03
- Supporting slices: M001/S02, M001/S04
- Validation: Validated by M001/S03 and M001/S04: the per-job workspace now supports imported correspondence review, package drafting, follow-up drafting, and routed entry from overview surfaces, with focused tests and browser verification covering package and follow-up loops.
- Notes: S01-S04 now make the individual job workspace the real execution surface for import, drafting, and follow-up work.
## Deferred
### R011 — The app should later expand overview analytics, saved views, and clearer strategy readouts beyond the core daily loop.
@@ -204,10 +204,10 @@ This file is the explicit capability and coverage contract for the project.
| R001 | primary-user-loop | validated | M001/S01 | M001/S05 | S01 completed with a job-scoped Gmail import loop wired into the job workspace: backend `GET /api/gmail/job-candidates` uses the owned job as context, imports target that job directly, and focused UI verification passed in `job-tracker-ui/src/correspondence-gmail-import.test.tsx`. |
| R002 | integration | validated | M001/S01 | M001/S03, M001/S05 | S01 completed with backend-ranked job-aware Gmail candidates, explicit imported/skipped import payloads, persisted thread/sender/recipient metadata, and focused verification across isolated `GmailControllerTests` plus `CI=true npm --prefix job-tracker-ui test -- --watch=false --runTestsByPath src/correspondence-gmail-import.test.tsx`. |
| R003 | differentiator | validated | M001/S02 | M001/S05 | Validated by M001/S02: backend application-package generation now uses recruiter/job/profile/attachment/imported-correspondence context, focused backend tests pass in an isolated harness, and the Tailored CV workspace test proves generation, editing, save, and saved-state redisplay behavior. |
| R004 | primary-user-loop | active | M001/S03 | M001/S01, M001/S02, M001/S05 | mapped |
| R005 | continuity | active | M001/S04 | M001/S05 | mapped |
| R006 | continuity | active | M001/S04 | M001/S05 | mapped |
| R007 | core-capability | active | M001/S03 | M001/S02, M001/S04 | mapped |
| R004 | primary-user-loop | validated | M001/S03 | M001/S01, M001/S02, M001/S05 | Validated by M001/S03: follow-up draft generation now consumes imported correspondence plus saved application package material, focused backend follow-up tests pass in an isolated harness, the focused React follow-up test passes, and browser verification on the built branch UI proved the grounded follow-up draft plus manual send/log flow back into correspondence. |
| R005 | continuity | validated | M001/S04 | M001/S05 | Validated by M001/S04: the job table now exposes actionable urgency chips that route directly into the relevant job workspace tab, focused daily-loop UI tests pass, and browser verification confirmed the table/dashboard/reminders flow routes into the same workspace model. |
| R006 | continuity | validated | M001/S04 | M001/S05 | Validated by M001/S04: dashboard and reminders now expose actionable attention items routed into the existing job workspace, focused daily-loop UI tests pass, and browser verification confirmed those surfaces open the correct job workspace state. |
| R007 | core-capability | validated | M001/S03 | M001/S02, M001/S04 | Validated by M001/S03 and M001/S04: the per-job workspace now supports imported correspondence review, package drafting, follow-up drafting, and routed entry from overview surfaces, with focused tests and browser verification covering package and follow-up loops. |
| R008 | constraint | active | M001/S03 | M001/S05 | mapped |
| R009 | constraint | active | M001/S04 | M002/S01, M004/S01 | mapped |
| R010 | continuity | active | M001/S04 | M001/S01, M001/S03, M001/S05 | mapped |
@@ -221,7 +221,7 @@ This file is the explicit capability and coverage contract for the project.
## Coverage Summary
- Active requirements: 7
- Mapped to slices: 7
- Validated: 3 (R001, R002, R003)
- Active requirements: 3
- Mapped to slices: 3
- Validated: 7 (R001, R002, R003, R004, R005, R006, R007)
- Unmapped active requirements: 0