# S07 Research — Daily-loop UAT artifact closure

## Summary

This is **light/targeted** work, not a new subsystem. S06 already built the hard part: a repeatable localhost preflight + seed + acceptance runner, a deterministic acceptance fixture, and a live evidence doc at `docs/s06-acceptance-run.md`. S07’s missing artifact is the **planner-facing research artifact for this slice**, and the product-facing gap is narrower: convert the existing live rerun evidence into a durable **executed daily-loop UAT closure artifact** that explicitly proves one seeded job behaves coherently across `/jobs`, workspace entry, `/reminders`, and `/dashboard`.

The codebase already has the acceptance data and most of the evidence:

- `scripts/s06-acceptance-data.sh` seeds the deterministic fixture (`S06 Acceptance Labs` / `S06 Acceptance Backend Engineer`) through the live API and prints the expected workflow/readiness/reminder outputs.
- `scripts/s06-acceptance-run.sh` runs preflight + seeding + one focused UI regression and rewrites the generated section of `docs/s06-acceptance-run.md` while **preserving** the guided browser section between `<!-- acceptance-run:browser:start -->` markers.
- `docs/s06-acceptance-run.md` already contains the real browser observations, debug-bundle paths, trace path, timeline path, and the explicit manual-send / Gmail-continuity limitations from the latest live run.
- `job-tracker-ui/src/daily-control-loop.test.tsx` and `job-tracker-ui/src/workflow-trust-signals.test.tsx` already encode the cross-surface contract that the same workflow signal should route `/jobs`, `/dashboard`, and `/reminders` into the same workspace semantics.

So the natural S07 move is **not** to invent new acceptance data or new routing logic. It is to package the existing live run into the milestone’s final UAT closure shape and make the evidence chain easy to rerun and audit.

## Requirement Focus

Active requirements this slice supports:

- **R008** — keep follow-up/reply assistance manual. S06 already captured the live manual-send proof; S07 must preserve that evidence in the final UAT closure artifact and avoid weakening the claim.
- **R009** — keep the loop individual-first. The seeded fixture and the `/jobs -> workspace -> /reminders -> /dashboard` proof are all single-job, single-user checks; S07 should keep the UAT narrative framed around one person managing one role end to end.

Validated requirements this slice is effectively re-demonstrating in executed-UAT form:

- **R005 / R006 / R007 / R010** — the same job must appear and behave coherently across the overview surfaces and the individual workspace.

## Skills Discovered

Installed skills already directly relevant; no additional skill install is needed.

- `agent-browser` — relevant for the executed browser/UAT pass. Two rules matter here:
  - **navigate → snapshot → interact → re-snapshot** after DOM/navigation changes, because refs become stale after page changes.
  - use explicit verification/diff evidence rather than prose-only confirmation.
- `test` — relevant because S07 should continue to anchor the closure artifact to the existing focused UI regressions instead of expanding scope to a broad suite.
- `react-best-practices` / `aspnet-core` exist, but S07 does not look like a React or backend architecture change first; it is mostly artifact/evidence closure on top of established behavior.

## Recommendation

Treat S07 as an **artifact-closure slice**, not a feature slice.

Build/prove in this order:

1. **Reuse the S06 acceptance fixture and runner as the source of truth.** Do not create a second seeded job, second seed script, or second acceptance data contract.
2. **Add or refresh one final S07-owned UAT artifact** that references the latest executed run and records the exact browser evidence for:
   - `/jobs` row signals
   - workspace entry for that same job
   - `/reminders` visibility and action routing
   - `/dashboard` visibility/analytics presence
   - manual-send boundary still holding
   - Gmail continuity status reported honestly
3. **Keep the shell-generated/live-browser split.** `scripts/s06-acceptance-run.sh` already has a good seam: generated shell summary vs preserved guided-browser section. Reuse that pattern instead of hand-editing a monolithic markdown file.
4. **Lean on the existing focused UI tests as regression proof**, then use browser assertions/debug artifacts for the final live executed proof.

The simplest successful version of S07 is likely one of these:

- extend the existing S06 artifact flow so the executed browser observations become the final S07/UAT closure evidence, or
- create a small S07-specific wrapper/doc that imports the current run metadata from `docs/s06-acceptance-run.md` and adds a final closure-oriented summary without duplicating the seeding/runtime logic.

## Implementation Landscape

### Files that already matter

- `docs/s06-acceptance-run.md`
  - Current live evidence artifact.
  - Already contains the exact observations S07 needs: `/jobs`, workspace, `/reminders`, `/dashboard`, trace/timeline/debug paths, manual-send proof, and the honest Gmail limitation.
  - Important detail: it is partially generated and partially hand-preserved.

- `scripts/s06-acceptance-run.sh`
  - Orchestrates preflight, seed, focused UI regression, and doc refresh.
  - Preserves the browser-observation block between `<!-- acceptance-run:browser:start -->` markers.
  - Natural seam if S07 wants a rerunnable final artifact instead of a one-off markdown edit.

- `scripts/s06-acceptance-data.sh`
  - Owns the deterministic fixture values and the expected follow-up/readiness state.
  - If S07 references concrete labels or expected reminder badges, those should come from here rather than being duplicated by hand.

- `.gsd/milestones/M001/slices/S06/S06-UAT.md`
  - Already defines the manual test cases and pass criteria for the live acceptance rerun.
  - Good source material for a final “executed results” closure artifact, but it is still a test-plan style document, not the final closure proof itself.

- `job-tracker-ui/src/daily-control-loop.test.tsx`
  - Best compact contract test for this slice’s user-facing claim.
  - Proves `/jobs`, `/dashboard`, and `/reminders` route into the shared workspace flow.

- `job-tracker-ui/src/workflow-trust-signals.test.tsx`
  - Lower-level routing/readiness contract proof.
  - Especially useful if S07 work changes route/query-param handling or the wording of action buttons.

### Natural seams for task breakdown

1. **Artifact-shape task**
   - Decide whether S07 owns a new doc or reuses `docs/s06-acceptance-run.md` as the canonical executed artifact.
   - Keep the generated/manual split if touching the runner.

2. **Browser-evidence task**
   - Re-run the live browser flow and capture explicit assertions/screenshots/debug bundles for the four overview/workspace surfaces.
   - Record the same job identity consistently across all surfaces.

3. **Regression/verification task**
   - Re-run the focused frontend tests and the acceptance runner so the final artifact is backed by both live execution and deterministic regression output.

## Constraints / Gotchas

- **Do not over-claim Gmail continuity.** S06 explicitly recorded that seeded correspondence was visible but `POST /api/gmail/refresh-linked-threads` did not fire in the local run. S07 should preserve that honesty unless the environment actually exposes connected Gmail state.
- **Do not break the deterministic fixture.** `scripts/s06-acceptance-data.sh` depends on backdated `followUpAt` and correspondence timestamps to keep the fixture in `follow-up` / `Waiting 14d` state.
- **Do not replace the manual-send proof with looser prose.** The strongest current evidence is concrete network behavior: `GET .../followup-draft` seen, no `POST .../send-followup` during draft review/regeneration.
- **Avoid duplicating fixture constants.** Company/job labels, dates, and expected reminder state already live in the seed script and UAT doc.

## Verification

Minimum verification stack for S07 planning/execution:

- `bash scripts/s06-preflight.sh`
- `bash scripts/s06-acceptance-run.sh`
- `test -s docs/s06-acceptance-run.md`
- from `job-tracker-ui/`: `CI=true npm test -- --runInBand --watch=false src/daily-control-loop.test.tsx src/workflow-trust-signals.test.tsx`

For the live browser part, prefer explicit assertions/evidence capture over prose-only checks. The final executed artifact should point to screenshot/debug-bundle/trace/timeline outputs and state exactly which surface each artifact proves.

## Planner Takeaway

This slice should be planned as **documentation/evidence closure on top of S06’s existing live-run machinery**. The risky work is already done. The planner should avoid new backend or UI feature work unless the rerun shows a real gap. The likely deliverable is a small, deterministic extension of the current acceptance-run artifact flow that turns S06’s live observations into the final S07 executed UAT closure for the daily loop.