The briefing was still teaching `scripthut project view` and `--project`
in two places, was missing any inventory of the user's configured
sources (so an agent couldn't pick `--source <name>` without guessing),
and didn't mention `scripthut status` or `scripthut source sync` —
both directly relevant to the agent's verify-then-submit loop.
Changes to the rendered prompt:
- New `### Sources` inventory block listing each configured source with
its type, branch (for git), default backend (when set), and a clear
explanation that `workflow run` re-syncs the git clone before
submitting, so runs execute against latest HEAD on the source's
configured branch. Edits to existing workflow files are picked up
automatically; new files need `source sync`.
- `### Source workflow` section expanded with `--backend` (required for
git sources without a default) and the latest-HEAD semantics.
- Cheat sheet (`## Inspecting state`) now leads with `scripthut status`,
carries the full source surface (`source list / view / sync`), and
spells out the three log modes the agent will reach for: live
`-f`, historical `--tail`, and stderr `--error`.
- Verify checklist now starts with `scripthut status` (if that fails,
nothing else will), and the submit/track section breaks `status`,
`output`, and `logs` into explicit numbered steps.
- Stragglers fixed: the cheat sheet's `project view` line and the
verify-step's `--project` reference are gone.
Tests:
- `TestLiveInventory` gains coverage of git + path source rendering
(branch, default backend, path-on-backend) and the empty-sources
case.
- `TestNoProjectStragglers` asserts `--project`, `scripthut project`,
`project view`, and `project list` never appear in the rendered
output, so any future regression to the old vocabulary fails CI.
- `TestObservabilitySurfaces` asserts the briefing teaches `status`,
`source sync`, and all three log modes (-f, --tail, --error) — the
things the user specifically asked the agent to know.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
