jobtrackingapp/docs/s07-uat.md

S07 UAT Closure: Daily-loop evidence seam

This document closes S07 by importing evidence from the executed S06 acceptance run instead of duplicating that generated run log. The canonical execution artifact remains docs/s06-acceptance-run.md, produced by scripts/s06-acceptance-run.sh.

Evidence source and seam

• Canonical acceptance artifact: docs/s06-acceptance-run.md
• Acceptance runner: scripts/s06-acceptance-run.sh
• Imported-evidence rule: this S07 document summarizes the cross-surface proof and links back to the acceptance artifact; detailed shell/browser output stays in the S06 run document and its linked artifacts.
• Evidence scope carried forward here: /jobs → workspace → /reminders → /dashboard, plus the follow-up draft manual-send boundary and Gmail continuity status.

Seeded job identity

The seeded job used for the daily-loop proof is:

• Company: S06 Acceptance Labs
• Role: S06 Acceptance Backend Engineer
• Surface identity anchor: the same seeded row is the object traced across /jobs, the job workspace, /reminders, and /dashboard.

Surface coherence summary

The imported acceptance evidence proves one seeded job stays coherent across the main overview surfaces:

1. /jobs

   • The live table rendered S06 Acceptance Labs • S06 Acceptance Backend Engineer.
   • The row showed the expected trust/status badges, including Follow up, CV ready, and Waiting.

2. Workspace

   • Opening the seeded job from /jobs loaded the real workspace dialog.
   • The tailored CV/application package content was present for the same seeded job.
   • The correspondence tab showed the seeded recruiter-thread message for that same record.

3. /reminders

   • The seeded job appeared under Needs Follow-up.
   • Reminder-facing badges and follow-up date matched the seeded acceptance state, preserving identity from the jobs table into reminders.

4. /dashboard

   • Dashboard counters and company activity reflected the same integrated seeded state.
   • Top companies by activity included S06 Acceptance Labs, showing the seeded job is visible in aggregate surfaces as well as record-level surfaces.

Manual-send boundary evidence

The acceptance run preserved the manual-send boundary for follow-up email behavior:

• The workspace follow-up draft tab rendered a generated draft for the seeded job.
• Network evidence recorded GET /api/jobapplications/3/followup-draft -> 200.
• The captured browser/network evidence recorded no POST /api/jobapplications/3/send-followup request during observation.
• Therefore, this run proves draft viewing/regeneration stayed on the safe/manual side of the boundary: the system prepared a draft but did not auto-send email.

Gmail continuity status

Gmail continuity was not proven as a passing live-sync behavior in this local run.

• The correspondence evidence for the seeded job was present in the real workspace.
• The newer linked-thread continuity banner was not visibly surfaced during this pass.
• No POST /api/gmail/refresh-linked-threads request appeared in the captured browser network log.
• The correct interpretation is: local run evidence preserved the continuity note and showed no refresh activity, so Gmail-connected continuity remains a stated limitation/known boundary for this execution, not an implied success.

Acceptance artifact links

These links point to the executed S06 acceptance evidence imported by this S07 closure:

• Acceptance run doc: docs/s06-acceptance-run.md
• Jobs/workspace debug artifact: /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-17-55-372Z-s06-jobs-workspace
• Follow-up draft debug artifact: /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-19-39-323Z-s06-followup-draft
• Dashboard debug artifacts:
  • /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-20-06-098Z-s06-dashboard
  • /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-20-47-319Z-s06-reminders-and-dashboard
• Browser trace zip: /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-17-13-689Z-session/s06-acceptance.trace.zip
• Browser timeline JSON: /home/pi/development/JobTracker/.artifacts/browser/2026-03-27T08-17-13-689Z-session/s06-acceptance-timeline.json

Rerun commands

Use the existing acceptance runner rather than editing this document by hand:

bash /home/pi/development/JobTracker/.gsd/worktrees/M001/scripts/s06-preflight.sh
bash /home/pi/development/JobTracker/.gsd/worktrees/M001/scripts/s06-acceptance-run.sh

If auth is required for seeding against a non-default/local context, export AUTH_TOKEN before rerunning the acceptance script.

Closure statement

S07 closes the daily-loop UAT requirement by attaching a dedicated artifact to the executed acceptance evidence seam: one seeded job (S06 Acceptance Backend Engineer) is shown coherently across /jobs, the workspace, /reminders, and /dashboard, while the follow-up flow preserves the manual-send boundary and the Gmail continuity limitation remains explicitly called out rather than overstated.