Files
gstack/ship/sections/manifest.json
T
garrytanandcapy-ai[bot] b104c3df4b feat(ship,spec,review): PR and issue text goes out only through gstack-post
/ship: Step 18 writes the title into an agent-written file. An existing PR's
title is piped from gh/glab through gstack-pr-title-rewrite.sh --stdin (new),
so neither the agent nor a shell string carries it; a new title is written
with the file tool and its version prefix checked in the file. Step 19
composes the body as before and publishes with gstack-post pr-create, or
pr-body then pr-title, which scan the exact bytes they send. The separate
title and body scans, the hand-rolled REST fallback and the title self-check
are gone (the helper does all three). Title preparation moved into the
pr-body section, so the skeleton shrinks.

/spec files its issue with gstack-post issue-create and drops the pre-issue
re-scan; Greptile replies use gstack-post reply and pr-comment.
scripts/resolvers/redact-doc.ts loses its PR and issue sinks, and a test
keeps any template from rendering one again.

Tests that pinned the old scan-then-gh wiring now pin the gstack-post wiring;
the publication tests run the real compose and publish blocks against a stub
gh with the real helper (HIGH in title or body refused, MEDIUM token flow).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-10-07 20:07:13 +00:00

81 lines
3.2 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 section reads are checked by test/skill-e2e-ship-section-loading.test.ts. 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": "App Store/TestFlight distribution is requested for an Apple app (.xcodeproj, .xcworkspace, or an app-product Swift package) \u2014 read at Step 0.9 before the branch gate; an Apple repository-landing request follows the normal pipeline"
},
{
"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": "measure",
"file": "measure.md",
"title": "Measure-then-fix loop for a red eval or free shard",
"trigger": "a paid eval case is red or a free-suite shard failed (Steps 5-6) \u2014 read from the tests section; diagnostic reruns, then the gate once"
},
{
"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": "shared-code-reuse",
"file": "shared-code-reuse.md",
"title": "Verified reuse of skipped shared-code advice",
"trigger": "reusing explicitly skipped shared-code advice (Step 9.3)"
},
{
"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": "documentation",
"file": "documentation.md",
"title": "Pre-publication documentation audit and completion gate",
"trigger": "auditing docs before final commit/verification (Step 14.5), on every ship"
},
{
"id": "pr-body",
"file": "pr-body.md",
"title": "PR/MR creation and documentation outcome",
"trigger": "preparing the title and creating or updating the PR/MR with the verified documentation outcome (Steps 18-19)"
}
]
}