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

feat(S04/T02): Made the job table show actionable follow-up/package nex…

Browse Source 
- job-tracker-ui/src/components/JobTable.tsx
- job-tracker-ui/src/daily-control-loop.test.tsx
- job-tracker-ui/src/i18n/translations.ts
- .gsd/milestones/M001/slices/S04/S04-PLAN.md
- .gsd/milestones/M001/slices/S04/tasks/T02-PLAN.md
This commit is contained in:
cesnimda
2026-03-24 13:56:42 +01:00
parent 8c9fb5b71f
commit 85fa373ba4
9 changed files with 236 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gsd/milestones/M001/slices/S04/tasks/T02-PLAN.md
+6
View File
@@ -42,3 +42,9 @@ Strengthen the job table so the first daily view shows what action is actually d
- `job-tracker-ui/src/components/JobTable.tsx` — clearer next-action affordances.
- `job-tracker-ui/src/daily-control-loop.test.tsx` — proof that the table participates in the routed daily loop.
## Observability Impact
- Signals changed: the table's urgency chips and primary row actions should now expose the same routed follow-up and package-work intents already used by dashboard and reminders.
- How to inspect later: read `job-tracker-ui/src/components/JobTable.tsx` for the shared workspace-route usage and run `CI=true npm --prefix job-tracker-ui test -- --watch=false --runTestsByPath src/daily-control-loop.test.tsx` to confirm table, reminders, and dashboard all land in the expected workspace state.
- Failure state made visible: if table actions drift from the shared routing contract, the focused UI test should fail with the wrong route/tab content instead of silently leaving decorative chips in place.