Files
gstack/ship/sections/manifest.json
T
Garry TanandClaude Fable 5 2cb359cbc5 fix(ship): name the /document-release subagent at every Step 18 decision point
The v1.54.0.0 carve moved Step 18 (documentation sync) into
ship/sections/pr-body.md and the Claude-host skeleton stopped saying
"document-release" anywhere in the workflow body — the dispatch became
invisible at exactly the moments an agent decides whether to open the
section. Restore visibility at three touchpoints, all subagent-framed
(never bare-slash-framed, which would invite an inline Skill invocation
that bypasses the fresh-context subagent + JSON contract):

- manifest trigger (renders into the section-index row AND the STOP
  pointer): "dispatching the /document-release subagent to sync docs
  (Step 18) and then creating or updating the PR/MR (Step 19)"
- Step 17 handoff line names Step 18's dispatch explicitly
- new hoisted doc-sync invariant beside the PR-title invariant: the
  dispatch itself is never skipped; only a failed subagent is
  non-blocking

Pin it in carve-guards: 'the /document-release subagent' (all three
touchpoints) + 'dispatches the /document-release subagent' (invariant)
must stay in the skeleton; the carved imperative 'Dispatch
/document-release as a subagent' must stay carved. Skeleton cap
91,600 → 92,300 (measured 91,764; trigger renders twice). Goldens
regenerated for all three hosts.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-26 00:08:46 +00:00

63 lines
2.5 KiB
JSON

{
"$schema": "https://gstack.dev/schemas/section-manifest.json",
"skill": "ship",
"version": 1,
"note": "PASSIVE registry (v2 plan T9 / CM2). Fields are IDs, file paths, human titles, and human-readable trigger text ONLY. The skeleton's decision-tree prose is the ONLY place that decides WHEN to read a section; required-reads live in the E2E fixtures. No machine predicate here \u2014 see docs/designs/v2_PLAN.md:663.",
"sections": [
{
"id": "apple-release",
"file": "apple-release.md",
"title": "Apple App Store / TestFlight release adapter",
"trigger": "the ship target is an Apple platform app (.xcodeproj, .xcworkspace, or an app-product Swift package) \u2014 read BEFORE Step 1's branch gate and any preflight; store distribution never routes through the branch/PR ceremony"
},
{
"id": "tests",
"file": "tests.md",
"title": "Test bootstrap, run, triage + eval suites",
"trigger": "running the test suites and (if prompt files changed) the eval suites (Steps 4-6)"
},
{
"id": "test-coverage",
"file": "test-coverage.md",
"title": "Test coverage audit (subagent)",
"trigger": "auditing test coverage of the diff (Step 7)"
},
{
"id": "plan-completion",
"file": "plan-completion.md",
"title": "Plan completion + verification audit (subagent)",
"trigger": "auditing plan completion, verification, and scope drift (Step 8)"
},
{
"id": "review-army",
"file": "review-army.md",
"title": "Pre-landing review + specialist army",
"trigger": "the pre-landing review and specialist dispatch (Step 9)"
},
{
"id": "greptile",
"file": "greptile.md",
"title": "Address Greptile review comments",
"trigger": "addressing Greptile review comments when a PR exists (Step 10)"
},
{
"id": "adversarial",
"file": "adversarial.md",
"title": "Adversarial review + learnings refresh",
"trigger": "the adversarial review and learnings capture (Step 11)"
},
{
"id": "changelog",
"file": "changelog.md",
"title": "CHANGELOG entry (release-summary + itemized)",
"trigger": "writing the CHANGELOG entry (Step 13)"
},
{
"id": "pr-body",
"file": "pr-body.md",
"title": "Documentation sync + PR/MR creation",
"trigger": "dispatching the /document-release subagent to sync docs (Step 18) and then creating or updating the PR/MR (Step 19)"
}
]
}