chore(M001/S03): auto-commit after complete-slice
This commit is contained in:
@@ -12,8 +12,8 @@ This file is the explicit capability and coverage contract for the project.
|
||||
- Source: user
|
||||
- Primary owning slice: M001/S03
|
||||
- Supporting slices: M001/S05
|
||||
- Validation: mapped
|
||||
- Notes: This is a durable trust constraint across all milestones.
|
||||
- Validation: Constrained by S03 follow-up tests and workspace UX: focused backend/frontend verification proves drafting uses context while outbound follow-up still requires an explicit manual send/log action.
|
||||
- Notes: S03 re-checked the manual-send boundary inside the follow-up workspace: users edit drafts locally and `POST /api/jobapplications/{id}/send-followup` fires only from the explicit send/log action. The broader anti-autonomy constraint still remains active across later milestone validation.
|
||||
|
||||
### R009 — Core UX, data model emphasis, and roadmap decisions should optimize for one person managing their own search.
|
||||
- Class: constraint
|
||||
@@ -208,7 +208,7 @@ This file is the explicit capability and coverage contract for the project.
|
||||
| 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 |
|
||||
| R008 | constraint | active | M001/S03 | M001/S05 | Constrained by S03 follow-up tests and workspace UX: focused backend/frontend verification proves drafting uses context while outbound follow-up still requires an explicit manual send/log action. |
|
||||
| R009 | constraint | active | M001/S04 | M002/S01, M004/S01 | mapped |
|
||||
| R010 | continuity | active | M001/S04 | M001/S01, M001/S03, M001/S05 | mapped |
|
||||
| R011 | operability | deferred | M002/S02 | none | unmapped |
|
||||
|
||||
Reference in New Issue
Block a user