docs(ship): Step 5 pre-gate text for stalls and the small-machine remote gate (Lane C-c)

The pre-gate paragraph now says `incomplete` blocks (a stall is incomplete)
and that `requires-remote` covers the remote gate under 8 cores, cleared by
`gstack-pregate clear` or `--remote --spend-cap <usd>` only under a cap the
user gave. Kept within the ship parity size cap (union 308,771 of 308,776
bytes; base 308,767), so the `--explain` hint moved to docs/pregate.md. The
handoff's escalation line already names any `requires-remote` lane; unchanged.

Files (G2): ship/sections/tests.md.tmpl, ship/sections/tests.md (generated).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
garrytanandcapy-ai[bot] committed 2026-10-15 00:23:34 +00:00
1 parent d6f4ea9f12
commit 4c2d3fe011
2 files changed
+8 -8

No files matched your search

+4 -4
View File
@@ -214,10 +214,10 @@ Only commit if there are changes. Stage the bootstrap's own files by name (confi
```
Stage 1 (regen, secrets, strays, literals) is the two-minute preflight; stage 2
runs the local lanes the touched files select under pipefail and prints
`requires-remote` for platform lanes this machine cannot run. `fail` or
`incomplete` blocks: fix, rerun (`--explain` shows each mapping). Step 18 refuses
a stale `pregate.json`, so rerun it after the final stamp.
runs the selected lanes under pipefail. `fail` or `incomplete` blocks: fix,
rerun. `requires-remote` (other platforms; the remote gate under 8 cores) needs
`gstack-pregate clear` or, under a user cap, `--remote --spend-cap <usd>`. Rerun
after the final stamp; Step 18 refuses a stale one.
Use the project's test commands discovered in Step 4 or documented in CLAUDE.md/AGENTS.md. Run every applicable suite; do not assume Rails or Vitest. The commands below are examples only for repositories that actually provide them. Use the same lane labels and exact commands again in Step 16.
+4 -4
View File
@@ -13,10 +13,10 @@
```
Stage 1 (regen, secrets, strays, literals) is the two-minute preflight; stage 2
runs the local lanes the touched files select under pipefail and prints
`requires-remote` for platform lanes this machine cannot run. `fail` or
`incomplete` blocks: fix, rerun (`--explain` shows each mapping). Step 18 refuses
a stale `pregate.json`, so rerun it after the final stamp.
runs the selected lanes under pipefail. `fail` or `incomplete` blocks: fix,
rerun. `requires-remote` (other platforms; the remote gate under 8 cores) needs
`gstack-pregate clear` or, under a user cap, `--remote --spend-cap <usd>`. Rerun
after the final stamp; Step 18 refuses a stale one.
Use the project's test commands discovered in Step 4 or documented in CLAUDE.md/AGENTS.md. Run every applicable suite; do not assume Rails or Vitest. The commands below are examples only for repositories that actually provide them. Use the same lane labels and exact commands again in Step 16.