On Codex, /ship and the other skills now start audit and reviewer
subagents with Codex's own `spawn_agent` and wait on `wait_agent`,
instead of Claude Code's Agent tool, which Codex can't call.
Why: Codex's /ship stopped at the Step 7 coverage audit and never
finished (#4476).
Codex users need `multi_agent = true` under `[features]` in
`~/.codex/config.toml`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Recording the same owner answer from two processes at once no longer
fails about one time in ten; the second add waits for the first to
finish writing.
Why: this was a daily flaky-test repair, and the owner-answers "two
processes adding at once" failure turned out to be a real race, not a
flaky test.
Nothing to do: tests only change, except the 11 lines in
`lib/owner-answers.ts`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=testing
Posting a /ship PR body no longer stops on a phone-number warning for
the run id and commit ids that /ship writes into it.
Why: most /ship runs hit this confirm (#4480, and #4474), which turned a
privacy guard into noise people click past.
Nothing to do: the next /ship post goes through without `--confirm`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: v1/outside-voice#1 reader=outside-voice
Review-Finding: v1/adversarial-native#1 reader=adversarial-native
The /ship child that `gstack-ship-budget launch` starts on Claude Code
now opens its prompt with `/ship --continue ` (or `/gstack-ship` under
`skill_prefix`), so Claude Code expands the skill instead of hoping the
model finds it.
Why: Claude Code expands a skill only when the prompt starts with the
typed command, and unattended Opus 5.5 found a skill from its
description in 0 of 60 sessions (gstack-evals#366).
Nothing to do: the rule for parents is now in docs/unattended.md.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A security finding that an owner ruled a note, dispositioned, or that
review deferred now shows in a PR body only as an opaque id and
"security finding, details recorded privately".
Why: on a public repository the old lines named the file, line and
reason of a live exposure outside the PR's change.
Nothing to do: other findings print exactly as before, and the details
stay in the private approval record.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=security
Review-Finding: p1/red-team#1 reader=red-team
When /ship stopped on a second-model review finding marked "Blocks:
yes", the record it left on the PR said no blockers were found; now the
finding is counted and /ship will not write that record until it is
fixed or ruled.
Why: `ready` and the merge step trust that record, so an undercount let
a blocked PR look clean.
Nothing to do: the next /ship run logs Step 11's findings and checks
them before writing.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: h2p1/red-team#1 reader=red-team
Review-Finding: h2p1/red-team#2 reader=red-team
Review-Finding: h2p1/red-team#3 reader=red-team
Review-Finding: v1/outside-voice#1 reader=outside-voice
An unattended /autoplan run that's handed the owner's reply at the final
gate now records it and finishes, the same way whichever instruction
file the agent reads.
Before, autoplan/SKILL.md said "never approve" while autoplan/DRIVER.md
said to record the relayed reply, so the outcome depended on which file
the model followed.
Nothing to do; this fixes existing instructions and adds no new feature.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
An unattended /autoplan run on Claude Code now says its phase guard is
on, instead of saying it is off while the guard blocks it. A phase
report written only in reasoning now gets a denial that says so and
names the exact command to send.
Why: in the day-one eval, two runs were blocked by a guard their own
record called off, and one run ended blocked after four publish attempts
whose report was invisible.
Nothing to do.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
When /ship stops at a pull request's review round cap, a grant naming
that stop now buys one scoped review of the fix, in the same run or the
next, instead of another read-only full review.
Before, a grant recorded after the read-only review, or between /ship
runs, bought nothing, so teams paid for extra full reviews or second
grants (ghome#40: $8.78 against about $3).
Nothing to do: /ship prints the grant command when it stops.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=security
Review-Finding: p1/specialist-batched#2 reader=state-machines
Review-Finding: p1/specialist-batched#3 reader=testing
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/red-team#3 reader=red-team
/ship's push step now always ends with one line that says what happened:
`PUSH: pushed …`, `PUSH: already_pushed …` or `PUSH: failed reason=`,
with the remote, branch and full commit.
Why: an eval grader looked for a `git push` call and counted 48 real
/ship pushes as "no push"; scripts and graders can now match this one
line instead.
If a script of yours matched the old `PUSH: ALREADY_PUSHED ` or `PUSH:
pushed to origin/` lines, update it; the exit status is unchanged.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
/ship's review planner now sends Swift code that asks for a privacy
permission, reads HealthKit or calendar data, or writes, deletes or
protects users' files on the device to the full review panel.
Why: since #4469, iOS changes that asked for microphone permission,
wrote and deleted meeting transcript files, or read calendars got the
light, one-reader review. Reported from the GHome iOS app's PR review.
Nothing to do: plain SwiftUI views, UserDefaults settings and file reads
still plan light.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
When /ship reuses a CI run that passed only after its failed jobs were
re-run, its CI line and its final summary line now add `rerun=
attempts=`.
Why: gbrain's CI now records which test files passed on a re-run
(gbrain#9690), and a pass on a re-run must read as flaky, never as
clean.
Nothing to do: runs without that record print as before; a malformed
record is refused with `CI_CARRY_RERUN_MALFORMED`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/outside-voice#1 reader=outside-voice
Review-Finding: p1/outside-voice#2 reader=outside-voice
Review-Finding: p1/adversarial-native#2 reader=adversarial-native
Review-Finding: p1/red-team#1 reader=red-team
`gstack-autoplan revise` now accepts a revised plan whenever the first
`next` accepted its shape, so a run no longer pays for a full review
round and then refuses the owner's edit.
Why: a plan with no section headings is reviewed whole by `next`, but
once the owner added one heading, `revise` stopped with
`PLAN_SECTIONS_INVALID`.
Nothing to do: runs already in progress pick this up too.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A second-model plan review in `/autoplan` is no longer reported as
unavailable when it actually ran, and `gstack-outside-voice --help` no
longer prints a line that reads like a real consent refusal.
Why: sessions believed the false label and paid to re-run the review, or
closed the plan phase without its second-model review.
Nothing to do: the command autoplan already runs now picks the right
check by itself.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
/ship's review planner now sorts Swift and Xcode files by risk, so a
plain iOS UI change gets the light review instead of the full
five-reader panel.
Why: `gstack-diff-scope` had no rule for `.swift`, so every all-Swift
diff printed `SCOPE_ERROR=unmatched` and the planner failed closed.
Reported from the GHome iOS app's PR review.
Nothing to do: unknown file types still fail closed exactly as before.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/outside-voice#1 reader=outside-voice
Review-Finding: p2/red-team#1 reader=red-team
Adds `gstack-first-use`: before an app build reaches its owner as "ready
to try", an agent from another model family plays that exact build, does
the plan's first five day-one actions with a screenshot or video of
each, and checks every link. Only then does it print the "try this
build" message.
Why: a recent app build passed every review and its owner still found
the first screen broken, because nothing tried the build the way the
owner would.
Nothing to do now; the first real use is that app's next build.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/red-team#4 reader=red-team
An agent can now check a draft question against the owner's earlier
answers before sending it, so the owner isn't asked again about
something they already said yes to.
Why: owners repeat "don't ask me, just do it" across threads, because
each new session forgets earlier answers. In a four-day sample, about 1%
of 444 asks were repeats this could skip, so a two-week pilot decides
whether it's kept.
Nothing to do: the new command is opt-in, and no existing command,
install output or factory rule changes.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=state-machines
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p3/outside-voice#1 reader=outside-voice
Review-Finding: p3/outside-voice#2 reader=outside-voice
Tests and scratch repositories in the temp directory can no longer write
approval rows into your real Capy Drive. When `gstack-approvals` runs
under `bun test`, or its state root or repository sits in the temp
directory, a Drive mirror that resolves outside the temp directory
(links followed) is refused with `APPROVAL_RECORD_WRITE_FAILED`; the
local row is kept.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
/office-hours no longer carries its 34 founder videos and essays in the
skill file; the closing runs a new `gstack-founder-resources` command
that prints the ones a user hasn't been shown yet.
Why: the skill was 9 bytes from its size cap, and the approved
partner-session improvements need room. This frees about 8.6 KB.
Nothing to do as a reader.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=testing
/ship's pre-push test selection now finds the tests of a monorepo app
that imports through its own `@/` alias (for example `apps/mobile`
mapping `@/*` to `./src/*`).
Why: only the root tsconfig was read, so every touched file in such an
app failed with `PREGATE_NO_LANE` even with a test beside it. Rebuilt
from #4462 by @dtoelke, who found and fixed it; thank you.
Nothing to do: a repo whose only tsconfig is at the root (gstack itself)
resolves exactly as before.
Co-authored-by: stackpt-agent <348614618+stackpt-agent@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p2v/outside-voice#1 reader=outside-voice
/ship's preflight and its CI-run lookup now reuse a passing CI test run
when a base merge left the files unchanged, stop instead of quietly
starting an hour-long test suite on the local machine, and refuse a
`--base` that names no commit instead of reporting an empty diff.
Why: gbrain #9662 lost a green CI run to a no-op base merge, then ran a
50-minute suite on a 4-CPU box, and its audit read a commit sha as a
branch and saw zero changed files.
Nothing to do: `--run-uncarried-here` restores running an uncovered
suite locally under `--tests-only`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: s11/outside-voice#1 reader=outside-voice
Review-Finding: s11/outside-voice#2 reader=outside-voice
/ship no longer stops for an owner's ruling when a base merge only
changes base-side text, such as the preamble hash in regenerated
SKILL.md files, and a reviewer's confirmation prose becomes a finding
the lead can lower with a reason.
Why: each of these cost a stopped /ship and an owner ruling on recent
PRs (#4383, ghome#16, #4431), which keeps unattended shipping from
finishing.
Nothing to do.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Unattended `/autoplan --full` now runs the second-model review when
`codex_reviews: enabled` is set, runs it in the foreground with a
9-minute limit, and records a timeout with the standard failure line
instead of ending the session. Two runs started in the same second also
get different run ids now.
Why: in a planning test, Opus 5.5 skipped the second reviewer in 2 of 3
runs over consent the config had already given, and ended the third
session while the review ran in the background.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
The secrets check no longer stops a push on three kinds of ordinary code
that only look like secrets: TypeScript types with spaced generic
arguments, Python arguments that read a settings constant, and camelCase
dotted field paths.
It also catches two kinds of real secrets it used to miss, one built
with `+` from short pieces and one written in a comment, so pushes are
both quieter and safer.
Nothing to do; a secret in any of the loosened positions still fails the
check.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/adversarial-native#1 reader=adversarial-native
Review-Finding: p1/outside-voice#1 reader=outside-voice
Review-Finding: p1/outside-voice#2 reader=outside-voice
/sync-gbrain now says when an artifacts push failed or memory pages
failed to import, instead of printing OK and "pushed", and one malformed
queued path (from a skill started where the project slug was empty) no
longer stops artifacts sync for every project.
Why: people trusted those rows and lost track of unsynced work; fixes
#4445, #4418 and #4417.
Nothing to do after upgrading: a stuck `projects//timeline.jsonl` record
is dropped and reported on the next sync.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=testing
Review-Finding: p1/specialist-batched#3 reader=testing
GitHub release pages now list every change a release ships, one plain
line each, linked to the pull request that made it, instead of one
headline per version or "see CHANGELOG.md".
Why: the release page is where people read what changed, and recent
releases went out saying only "see CHANGELOG.md".
Nothing to do: the next release uses it; a release with no CHANGELOG
entry stops with `NOTES_MISSING` instead of publishing a stub.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Three small fixes: `skill_prefix=true` now survives updates when gbrain
is installed, the OpenClaw docs stop sending people to stale ClawHub
skills, and `gstack-issue-links` no longer reads other repositories'
issue numbers as gstack issues.
Why: each one misleads users or /ship today (wrong skill names after
every update, April 2026 skill builds, wrong `Refs #N` lines in PR
bodies).
Nothing to do as a reader. Thanks @fliaron (#4413) and @exGeni (#4421)
for the detailed reports.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Free-tests CI now uploads test results to Trunk with analytics-uploader
v2.1.8 and analytics-cli 0.17.0, up from v2.1.6 and 0.16.2.
Why: Trunk warned that uploader v2.1.6 may pick up analytics-cli 1.0.0
when it ships and then fail to upload; v2.1.8 never resolves a CLI above
0.x.
Nothing to do.
Co-authored-by: Tyler Beebe <tsb252@gmail.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A driven /ship now runs each ship/DRIVER.md phase as one command, shows
how many calls the run made, and stops itself with a printed line at 100
minutes.
Why: measured /ship runs made 121 to 308 calls where the driver plans 9
to 12, and 10 of 12 ran past the 100-minute stop while those limits were
only prose.
Nothing to do: older ship records without `calls=` still validate and
print.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/outside-voice#1 reader=outside-voice
A `/ship` with a token cap on Claude Code no longer stops at its first
handoff: the child `claude -p` session now gets its prompt.
Why: `--allowedTools` takes every argument after it, so the prompt was
read as one more tool name and the child exited at once. The launch now
puts `--` before the prompt.
Nothing to do. Thanks to @exGeni for the report and diagnosis.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Packing a checkout for a Ubicloud run no longer fails when git running
beside it is rewriting a ref, and the /plan-ceo-review HOLD SCOPE eval
no longer fails a review whose follow-up question doesn't repeat the
mode name.
Why: both made tests fail at random. The pack race failed Free Tests
twice on 2026-11-17, and the HOLD check failed the weekly eval census on
main.
Nothing to do.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
gstack's router no longer gives bug reports a special check-the-cause,
fix-it-test-first rule, and its description no longer lists debugging,
so the model fixes a bug the way it would without gstack. This keeps
gstack to the parts that measurably help, and on 26 hard real bugs the
rule gave no clear gain.
Nothing to do.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
When `/ship` posts a pull request's description, the count of earlier
review rounds now always comes from the PR's real history. Before this
fix, a description that brought extra history blocks of its own could
make gstack count one round where there were three.
Why: the per-PR round cap (R51) depends on that count, and it's the last
gap before crews can stop counting rounds by hand.
Nothing to do as a reader.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=red-team
Review-Finding: p1/specialist-batched#2 reader=testing
/autoplan's approval page now re-reviews a scope change both reviewers
raise, asks a plan with no Owner's words to confirm its direction, and
checks owner quotes only against this repository's approvals record.
This keeps the rule that only the owner's own words set a plan's
direction, and there is nothing for the reader to do.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/specialist-batched#1 reader=specialist-batched
Review-Finding: p1/specialist-batched#2 reader=specialist-batched
* WIP plain PR bodies and squash messages
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Fold PR bodies to three plain lines and land every PR as one plainly titled commit
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Expect the plain commit body in the train land tests
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Count the new policy keys in the floor tests and record the ship size change
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Let older, generated and Dependabot PRs pass the body check, and keep comments posting
The opening check now follows the same date and branch exemption as the rest of the body check, Dependabot branches are exempt, the exemption only counts for branches in this repository, a merge that cannot read the PR waits instead of refusing, and a broken policy file no longer stops comments.
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=testing
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/red-team#4 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Stop re-posted PR bodies from duplicating sections, and let file names through the word check
Posting an already-folded body now replaces each section once instead of keeping the old copy beside it, and listed words inside file paths or file names, such as a test file in the Tests section, no longer count as prose.
Review-Finding: v2/outside-voice#3 reader=outside-voice
Review-Finding: v2/adversarial-native#2 reader=adversarial-native
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Describe the folded three-line PR body in the skills guide and the prose lint help
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say when /ship's test step hit its time limit, and keep long file lists off the remote test command line
gstack-ship-preflight stopped gstack-pregate after a fixed hour and printed
'PREGATE: unreadable (exit 143)'. The whole step's budget is now
--step-timeout <s> (default 3600), and a stop at it prints
'PREGATE: time limit hit' with the way out: push and let CI's full run
carry the tests, or a larger budget.
The test_backend command pregate prints for a small machine put every
selected file into one argument, which Linux refuses past 128 KiB. The
files now reach the VM in a setup script named by its content.
Also adds an arg-limit troubleshooting entry and says the Windows job has
eight shards.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Read the small-machine file list from the setup script in the hidden-folder path test
The remote command now names a setup script instead of the files, so the
test checks that the script lists the ./-prefixed path.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep a test path with a newline out of the remote file list
A selected test path containing a newline, or equal to the list's end marker, could end the setup script's file list early and run the rest as shell on the test VM. Such paths now keep the quoted inline command.
Review-Finding: p1/outside-voice#1 reader=outside-voice
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Mark the preflight half of the Step 5 time limit to-do as done
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep checking a custom skill's contract when it still lists the removed test-after-edit item
The Stop hook used to treat such a contract as invalid and check none of
its items. It now skips only that item, warns with a line naming the file
and item, and checks the rest.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Move the changelog note to its own entry, since a landed entry is never edited
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix: pre-landing review fixes
Test that gstack-skill-contract check warns about a removed-kind item and checks the rest.
Review-Finding: p1/specialist-batched#1 reader=specialist-batched
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* chore: changelog and TODOS
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say when to use each gstack skill in Claude Code's skill list (GST-2774)
Claude Code's listing of each gstack skill now keeps a short when-to-use
clause after its first sentence, so Opus 5.5 loads /review on "review my
changes" and /plan-eng-review on "plan this feature" (GSTA-558).
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep /review and /plan-eng-review within their size pins and refresh budgets
CI on the first head found five size and fact checks the new catalog
clause moved: the per-host SKILL.md size pins, the context-budget
ceilings, the deslop-shared-libs catalog byte pin, the Claude ship golden
and the catalog ceiling CLAUDE.md states. /review's and /plan-eng-review's
full descriptions are now shorter than before, so their pins go down, and
/plan-eng-review's scope gate is unchanged from main.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say which skills keep no when-to-use clause in the changelog entry
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Update the catalog budget and voice-trigger docs for the when-to-use clause
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Drop "deploy this" from /ship's Claude Code skill list line
Deploying belongs to /land-and-deploy, so /ship's when-to-use clause keeps
"ship it, create a pr, push to main" only. Budgets, the size ledger and the
Claude ship golden are re-measured.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix: pre-landing review fixes
Review-Finding: p1/specialist-batched#1 reader=specialist-batched
Review-Finding: p1/red-team#1 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Re-measure the setup-gbrain size cap after merging main
Main grew setup-gbrain's always-loaded part to 38,621 bytes, and this
branch's when-to-use clause adds 55 more, so the cap measured on the old
base (38,637) is stale. The cap is now the merged measurement, 38,676.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
finish --docs-requested refused a correct fix when the docs audit named the
file as path:line ("changelog.d/engine-parity-decisions.md:8: wording") or
path:line:column, because the match only allowed whitespace, quotes or
punctuation right after the path. It now also allows :<line> and
:<line>:<column> before those, while a different file sharing the path's
prefix still doesn't match. Reported by Vorflux via FOUN-32.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Load the never-print-secrets rule in every skill on every host, with the commands it missed (GST-2753)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Ask each question once and check every handed-over file, in every skill on every host (GST-2756)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Point the shared CI-wait rule at gstack-pr-wait and name the missed secret-printing commands
The Ground Rules section told every skill to wait with gh pr checks --watch, which spends the shared GitHub GraphQL quota gstack moved off; it now names gstack-pr-wait. The banned list also covers ps aux and ps -ef, set -x, git config -l and an export $(...) that expands to a bare export. Size caps raised to the measured +70 bytes.
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say which skills carry the new rule in its release note
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say the new rules reach only skills that load the shared preamble
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* List all four shared Ground Rules in the loadouts guide
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep reviewer product challenges open on the approval page
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Read the approvals record without writing the slug cache when building the gate
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep every reviewer challenge on the approval page, and ask again when the cut list changes
A challenge with no change kind and no real owner quote now becomes a proposal instead of vanishing. An ordinary finding that only mentions an earlier challenge no longer closes it. The cut list and confirm-direction items carry their content in their origin, so an earlier answer is not reused for a changed list.
Review-Finding: p1/specialist-batched#1 reader=specialist-batched
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/red-team#3 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep removed owner quotes redacted, and keep High proposals as blocking tasks when declined
Public exports now redact the Owner's words from every plan text the run kept, so a quote a revision removed stays hidden in earlier reviewer results. A paired proposal takes the heaviest change either reviewer named, so an ordering-plus-scope pair is re-reviewed instead of settled. A proposal behind a Critical or High finding offers b as keep the draft and carry it into the build as a blocking task, and only a settles it.
Review-Finding: p1v/outside-voice#1 reader=outside-voice
Review-Finding: p1v/outside-voice#2 reader=outside-voice
Review-Finding: p1v/adversarial-native#2 reader=adversarial-native
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Document owner's words, reviewer proposals and day-one items on the approval page
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* chore: changelog and TODOS
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
* Count review rounds per pull request across /ship runs (GST-2673)
/ship's two-round review cap was counted inside each run, so a pull request
shipped many times was reviewed again at every head. Step 1 now reads the
rounds the PR body's receipt history records, passes them to the review plan,
and sends later heads to the scoped re-check, with a lane or Captain round
grant for an extra round. Adds the no-loss replay preregistration.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Cap full review rounds per pull request and keep fix-checks to each run
The plan counts a PR's earlier full rounds (--prior-full) against the cap of
two, as the approved plan says, and prints every earlier round as pr_rounds=.
Renames the troubleshooting anchor to pr-round-cap, lists <SESSION_ID> as a
reviewed placeholder, and leaves ship/DRIVER.md at its size cap.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Point the ship driver's review pass at Step 9's plan flags, which carry the PR round count
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Give a pull request's final head a full review and make the diff-only re-check advice only (GST-2673)
A scoped re-check that reads only what changed since the last reviewed head
caught 22 of 24 planted faults but none of 8 real faults that full rounds had
caught, so it no longer carries a /ship receipt. A later head whose own lines
changed now gets a fresh full review, the PR's last before merge; a PR already
at two full rounds gets one read-only full review with no fix round, whose
blocker goes to the lane's Captain. carry prints RECHECK: advisory and refuses
--recheck. The drift threshold, the re-check blocker count and the
design-change grant kind are removed with the route they fed.
Repins lib/review-depth.ts and ship/sections/review-army.md under replay
GST-2673 (docs/evals/pr-round-count-results.md; deterministic grid against
main: 196,608 of 196,608 plans identical with no prior rounds).
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep a review round grant usable through its fix round and after a read-only review
A grant now holds after the fix round's commits move HEAD past it, counts only the rounds earlier heads spent, and a receipt written without a run keeps other runs' stubs.
Review-Finding: p1/specialist-batched#1 reader=state-machines
Review-Finding: p1/red-team#2 reader=red-team
Review-Finding: p1/red-team#3 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Count every review round at a granted head again, so a grant can't reset the count
Reverts the history change that skipped rounds recorded at a round grant's head: the run that hit the cap is recorded at that same head, so skipping it wiped the count. A grant recorded after a read-only review still doesn't buy a fix round (fails closed).
Review-Finding: p2/adversarial-native#1 reader=adversarial-native
Review-Finding: p2/outside-voice#1 reader=outside-voice
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Give a merge head a full review when its removed lines changed or its receipt came from a re-check
A head whose removed lines changed with the base no longer carries on one scoped reader, a receipt an older gstack carried through a scoped re-check no longer carries on or lands, and a /ship body post keeps the run history. The read-only stop stops offering a round grant it can't honor, and the stamp-only-carry no-stop class is removed because a refused carry never stopped. (GST-2706)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep the run history inside Agent notes when the PR text quotes a receipt
Review-Finding: p1/red-team#1 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Let a receipt write skip a retired no-stop entry left in an older branch ledger
Review-Finding: p3/outside-voice#1 reader=outside-voice
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say in troubleshooting that the queue refuses a receipt carried through a re-check
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* gstack-runaway prices each wake and marks it cold or warm (GST-2770)
Each wake read is priced in warm model calls, with a cold call (after the 5-minute prompt cache lapsed) at 19.4. The scan line reports cold and empty wakes' share of spend, and scan --wakes lists each wake. A message sent to another thread now counts as action.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Document gstack-runaway wake pricing in the /runaway-stopper reference
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* gstack-runaway charges a lapsed cache to the call after a long tool and ignores a null message target
A cold wake no longer counts its first call twice, a call issued more than 5 minutes after the previous model call is cold whether or not an inbound item was recorded, and a report to the parent with an explicit null target stays a report.
Review-Finding: p1/outside-voice#1 reader=outside-voice
Review-Finding: p1/outside-voice#3 reader=outside-voice
Review-Finding: p1/red-team#1 reader=red-team
Review-Finding: p1/red-team#2 reader=red-team
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Describe gstack-runaway's cold_extra_spend and empty_spend as shares of spend in docs/skills.md
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Stop the optional Stop hook checking for a test after the last edit (GST-2811)
Models already run a test after their last edit when /verify asks (Opus 5.5
96%, GPT-6.1 Sol 89%), and the hook's check added no measurable gain. Remove
the check_after_last_edit contract item and its shell-write parser, keep the
rule as /verify prose, and stop /verify telling models never to edit CHANGELOG.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Point the removed shell-write parser at the contract checker's test so the pre-merge check accepts its removal
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say in the changelog entry that a custom contract with the removed item stops being checked
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Never let a later docs-audit line override an earlier blocked line (GST-2349)
A blocked documentation-audit result line followed by an unfenced "current"
JSON line for the same audit as the very last line was accepted as current,
and a last "current" line whose only fault was its format was repaired back to
current. The blocked verdict now carries: a last line that drops an earlier
blocked status or blocker for the audit is never accepted and gets the
one-way re-ask, whose reply must stay blocked and keep those blockers.
Step 2 of the docs audit section no longer says it parses only the last
line, and the changelog entry now claims only what the parser checks.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Leave the landed changelog entry alone and correct its claim in a new entry (GST-2349)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Split a run-on sentence in the changelog entry for the docs-audit fix
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Stop Ubicloud fan-outs overshooting the vCPU limit and owners deleting each other's VMs (GST-2852)
The runner's quota check now reads usage and books the new VM's vCPUs under
one lock per machine, so shards started together see each other instead of
all passing on the same reading. A new room command prints how many VMs of a
size fit now, so a fan-out can size each batch. When usage can't be read,
a UBI_QUOTA_VCPUS ceiling refuses the create instead of letting it through.
VM names keep the whole owner id (up to 31 characters) instead of its first
12, so owners sharing a prefix no longer reap each other's VMs (#3748). A VM
named under the old cut form is still reaped by the machine that recorded it.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Add the changelog entry for the Ubicloud quota and owner-id fixes (GST-2852)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix: pre-landing review fixes
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=red-team
Review-Finding: p1/specialist-batched#3 reader=testing
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say which old-form VMs a long owner still reaps in the changelog entry (GST-2852)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Name the room command in the Ubicloud skill summary (GST-2852)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Make gstack-pr-wait, gstack-ci-gate and the release cut count a failed check hidden behind an empty rerun (GST-2252)
GitHub rollup and default check-runs list hold only each check suite latest attempt, so a rerun attempt with no jobs hid the failed run before it, and a workflow run that failed before any job never appeared. All three readers now add CI at the commit as the merge queue reads it (ciAtHead via lib/ci-head-checks.ts) and keep the worse bucket per check. Tests reuse the gstack-evals#303 recording from #4235.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Have the release cut read every check attempt only for commits that pass its named checks (GST-2252)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Say in the changelog that the release cut now counts failed commit statuses (GST-2252)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Let the release cut set its own jobs aside in the every-attempt check read too (GST-2252)
After #4297 the cut sets aside check runs from its own workflow and the Windows nightly by job id, but the rows from lib/ci-head-checks.ts skipped that filter, so the cut waited on its own run. headCheckRows now takes the set-aside check run and workflow run ids and removes them from every list before ciAtHead reads it.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Stop /ship's docs audit halting when the child writes prose after its result (GST-2349)
The Step 14.5 documentation audit read only the child's last nonempty line.
Children that ended with their JSON result and then restated the documentation
section in prose had a valid "current, no edits" audit rejected with no format
repair, which spent an attempt each time and, after two, stopped /ship for an
owner risk grant (founderstar #837, harness-evals #393).
gstack-docs-candidate result now reads the last line that opens a JSON object,
ignores prose after it and says so with TRAILING_PROSE:. A result missing only
documentation_section keeps the existing free re-ask, whose prompt now tells the
child to put the section inside the JSON and write nothing after the line; the
re-audit retry note says the same. Content failures still count.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Send any docs-audit result with text after it back for one free re-ask (GST-2349)
A cross-family audit of the previous commit showed that ignoring prose after
the result line let a contradicting verdict through: a blocked result followed
by a fenced "current" example was accepted as current, and a "Correction: the
audit is BLOCKED" after a current line became a repair that had to stay current.
Text after a JSON line carrying the audit id is no longer ignored and never
searched for another result. It is a format slip: FORMAT_REPAIR re-asks once
for the whole result line without spending an attempt, the re-ask counts
everything the audit wrote after its JSON line, and the reply is judged on its
own with nothing kept from the first line. A reply that itself has text after
its line counts as an attempt.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Keep a blocked docs audit blocked through the free re-ask (GST-2349)
Review of the previous change found that the free whole-line re-ask could
turn a blocked audit into a passing one: a blocked result line, then a fenced
"current" example, then a "current" reply was accepted as current.
The re-ask now works one way. It is offered only when every JSON line that
carries the audit id is free of content problems; a content problem such as a
missing status or "current" with edits still spends an attempt. If any of those
lines said blocked or listed a blocker, the reply must stay blocked and keep
every blocker (it may add more), and the re-ask prompt says so.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Make gstack's shell locks hold when mkdir reports a race it lost (GST-2247)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Fix lock tests and fixtures for gstack_lock_take; trim setup-gbrain lock prose
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Ship the lock helper with every copied runtime and fixture that runs a lock
The Claude Code wrapper's copied runtime now includes bin/gstack-lock.sh, and
bin/gstack-render-claude.sh sources it beside itself, so gstack-config set
works in a copied runtime and the render lock is taken by every caller.
Test fixtures that copy single bin scripts now copy the helper too, and the
mkdir lock guard is registered as a repo-wide docs reader.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Release a lock whose owner file could not be fully written
gstack_lock_take created the owner file with a noclobber redirect and, when
that redirect failed, treated an existing file as a competing holder. If the
file was created but the write then failed (disk full, quota, ulimit -f), the
helper found its own empty file, returned 1 and left a lock nobody held;
freeze's state lock has no stale recovery, so it stayed busy until removed by
hand. The helper now tells "opened but write failed" from "already held",
removes its own file and directory, and returns 3. The inline copy in
gstack-ff-update is updated byte for byte, and a new test under ulimit -f 0
fails on the old helper.
Review-Finding: s11/outside-voice#1 reader=outside-voice
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Describe the lease lock as gstack_lock_take's O_EXCL owner file
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Make gstack agents lead every report with what failed, what's unverified and what else changed (GST-1455)
The shared closer asks a status report to stay under 250 words and open with Failed or skipped:, Unverified: and Also changed: lines, each naming every item or none; lists past 10 give the top 10 and a count. Capy's factory.md point 10, the lane report Outcome and READY's lane lines carry the same lines, and point 10 points findings write-ups at ETHOS.md section 8. The wording is GEVA-2's round-3 candidate f83eba4, ported without the retired /investigate rows. factory.md is 4,396 B, so its budget rises from 4,200 to 4,400.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Update the ship skill golden files for the new shared preamble id (GST-1455)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>