docs(captain): name the lane brief in the template lists; fix two template command lines

docs/skills.md and docs/PROJECT_STRUCTURE.md enumerate captain/templates/ and
omitted brief.md (document-release audit gsta130-docs-1). brief.md's restore
line now names the checkpoint dir that resume --from takes, and plan-ask.md's
answer line carries --rec-hash like brief.md (ship review pass 2).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

captain/templates/brief.md

@@ -37,6 +37,6 @@ Plan: exempt reason.
 ```
 
 A lane whose brief says `approved: <dir>` starts at step 2 with that run (restore it with
-`gstack-autoplan resume --out <new dir> --from <dir>` when it lives on another machine); a
+`gstack-autoplan resume --out <new dir> --from <its checkpoint dir>` when it lives on another machine); a
 lane whose brief says `exempt:` starts at step 3. A brief with no `Plan:` line reads as
 `Plan: required`.

captain/templates/plan-ask.md

@@ -29,6 +29,6 @@ named: docs, trains, cleanups>, and carry them through to done with no further a
 ```
 
 When the answer comes back, record it before the work starts. For an autoplan gate:
-`gstack-autoplan answer --out <run dir> --gate-rev <n> --reply <tokens> --by agent:<thread> --owner-reply "<exact words>"`,
+`gstack-autoplan answer --out <run dir> --gate-rev <n> --reply <tokens> --rec-hash <h> --by agent:<thread> --owner-reply "<exact words>"`,
 then `gstack-approvals import --autoplan <run dir> --by "<owner>"` (the tool records the relayer). For any
 other plan: `gstack-approvals add --ask "<what>" --words "<exact words>" --by "<owner> (via <controller>)" --scope "<what it covers>"`.

docs/PROJECT_STRUCTURE.md

@@ -55,7 +55,7 @@ gstack/
 ├── deslop-shared-libs/ # Recommendations-only audit for worthwhile shared-code extractions
 ├── test-audit/      # Report-first sweep for low-value tests (test value bar, audit mode)
 ├── eval-plan/       # Preregistered paid evals: prereg, arms, $0 dry run, priced pilot (bin/gstack-eval-plan)
-├── captain/         # /captain (also /crew): one controller, many lanes; templates/ holds CREW.md, AGENTS.md, NOTES.md, DIGEST.md, the flaky ledger, the lane report, the READY block, slot call, asks and the daily automation prompt
+├── captain/         # /captain (also /crew): one controller, many lanes; templates/ holds CREW.md, AGENTS.md, NOTES.md, DIGEST.md, the flaky ledger, the lane report, the READY block, slot call, the lane brief, asks and the daily automation prompt
 ├── plan-ceo-review/ # /plan-ceo-review skill
 ├── plan-eng-review/ # /plan-eng-review skill
 ├── autoplan/        # /autoplan skill (auto-review pipeline: CEO → design → DX → eng, eng always last)

docs/skills.md

@@ -1411,7 +1411,7 @@ this model disagree (squash or merge, who stamps, gate-ahead, the severe race, a
 id in the READY), the skill ships both as options for the crew rules file.
 
 Templates (CREW.md, AGENTS.md, NOTES.md, DIGEST.md, the flaky ledger, the lane report,
-the READY block, the slot call, the plan and merge asks, the daily automation prompt)
+the READY block, the slot call, the lane brief, the plan and merge asks, the daily automation prompt)
 live in `captain/templates/`; the team setup guide for Capy is [docs/captain.md](captain.md).
 
 ## `/gstack-upgrade`