Skip to content

v1.94.0.0 ship: CI is the one full test run (CI carry, tree cache, /ship beside CI) - #3901

Merged
capy-ai[bot] merged 125 commits into
mainfrom
gsta-258-a-ci-carry
Nov 3, 2026
Merged

capy-ai[bot] merged 125 commits into
mainfrom
gsta-258-a-ci-carry

Conversation

@garrytan

@garrytan garrytan commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner
{
  "schema_version": 1,
  "pr": 3901,
  "head": "904171960692cc8970860d2732ea035b24354e07",
  "version": "1.93.37.0",
  "base": "main",
  "gate": {
    "targeted": {
      "pass": 185,
      "fail": 0,
      "skip": 0
    }
  },
  "session_kind": "unattended",
  "head_tree": "1fad5891aaa6473260683c586bb51228011c0f24",
  "product_patch_id": "bf3fc3176972ca56d08f741f8c2e52584e00ebf4",
  "gstack_version": "1.93.24.0",
  "review_depth": {
    "depth": "full",
    "class": "gate",
    "runtime_lines": 827,
    "rules": "b2272efd321ce7cb",
    "base": "e4e9913398e3b11a445bb5706bd387b4be5d38c4",
    "registry": "e4e9913398e3b11a445bb5706bd387b4be5d38c4",
    "gate_scan": {
      "tagged": 0,
      "head": "904171960692cc8970860d2732ea035b24354e07"
    },
    "reasons": [
      "gate-class",
      "risk:money",
      "risk:security",
      "runtime=827"
    ],
    "risk": [
      "money",
      "security"
    ]
  },
  "pregate": "requires-remote cleared @1fad5891aaa6 (7 checks, current for 904171960692)",
  "requires_remote": [
    "free-tests.yml/macos-named-regressions: https://github.com/garrytan/gstack/actions/runs/41570950214/attempts/1",
    "windows-smoke.yml/windows-smoke: https://github.com/garrytan/gstack/actions/runs/41570950098/attempts/1",
    "pregate.json/remote_gate: remote-gate tree=1fad5891aaa6 tests=34511 skipped=112 runs=41571664924/1 profiles=ci-reuse/free-tests heads=904171960692 verified=2026-11-03T03:25:49.511Z"
  ],
  "issues": {
    "fixes": [],
    "refs": [
      3914,
      3915
    ],
    "flakes": [],
    "related": []
  },
  "docs": {
    "status": "updated",
    "scope": "docs/, README.md, AGENTS.md, CONTRIBUTING.md (base 6f1dfd5b to a102205e)"
  },
  "review_loop": {
    "passes": 2,
    "blocking_found": 7,
    "deferred": 2,
    "noted": 2,
    "fixed": 4,
    "scope": "frozen",
    "fix_checks": 1,
    "rounds": 3,
    "unrecorded": 3,
    "ledgers_read": 3,
    "dispatches": {
      "specialist": 6
    }
  },
  "review_loop_exception": {
    "accepted_by": "GStack Minder",
    "date": "2026-11-03",
    "via": "standing grant, GSTA-258 builds, 2026-11-03",
    "reason": "one scoped fix-check after the round-2 cap, scoped to the three round-2 fixes in a102205e",
    "fix_check": {
      "head": "a102205e50e97ad2aaa2d823d0dada584b234293",
      "findings": 1,
      "files": [
        "bin/gstack-evidence",
        "lib/pregate/checks/lanes.ts",
        "docs/pregate.md",
        "changelog.d/gsta-258-a-ci-carry.md",
        "test/pregate-carry-gate.test.ts",
        "test/ship-ci-carry.test.ts"
      ]
    }
  },
  "review_targeted": {
    "classes": [
      "money"
    ],
    "rules": "c82addff6fb60fa0",
    "brief_sha": "7f92a0d0a8319c3c0e076fb3b1a4689c45120b2be2c14dfc7d4cb03aafa9d6a5",
    "product_patch_id": "bf3fc3176972ca56d08f741f8c2e52584e00ebf4",
    "status": "done",
    "findings": 0,
    "raised_by": "targeted"
  }
}

What changed

gstack-pregate on a 4-core machine: before, the test tier waited on the Ubicloud VM; after, the green Free Tests run at the same tree clears it. (Image render failed in this sandbox; text version below.)

Before/after as text: gstack-pregate on a 4-core machine: before, the test tier waited on the Ubicloud VM; after, the green Free Tests run at the same tree clears it
--- Before · before.txt · captured output
+++ After · after.txt · captured output
+CI_CARRY: accepted ci-carry tree=7be72149fbd6 tests=34511 runs=41567501815/1 profiles=ci-reuse/free-tests heads=02b2f2938a96 verified=2026-11-03T02:53:44.485Z
+CI_CARRY: cleared pregate.json/remote_gate remote-gate tree=7be72149fbd6 tests=34511 skipped=112 runs=41567501815/1 profiles=ci-reuse/free-tests heads=02b2f2938a96 verified=2026-11-03T02:53:44.485Z
+requires-remote: pregate.json/remote_gate (remote) 112 test(s) — cleared by remote-gate tree=7be72149fbd6 tests=34511 skipped=112 runs=41567501815/1 profiles=ci-reuse/free-tests heads=02b2f2938a96 v
+PREGATE: requires-remote (2 uncleared) tree=7be72149fbd6 head=02b2f2938a96 checks=7
-CI_CARRY: none (no_verified_run: ci-reuse/free-tests: run 41562764513: tree_mismatch)
-requires-remote: pregate.json/remote_gate (remote) 891 test(s) — uncleared; run bash scripts/ubicloud/pregate-remote.sh, then clear with gstack-pregate clear --remote pregate.json/remote_gate --rece
-PREGATE: requires-remote (3 uncleared) tree=5b7b3b524819 head=9125936247e9 checks=1
 

Why

"CI is the one full test run" (R65, Garry: "make sure gstack minder gets this fixed in ship in gstack"). Every /ship ran the full free suite a second time on a VM or locally, about 10 minutes, after CI had already run it on the same tree. Now pregate and /ship reuse CI's verified run at the exact tree, and on gstack that is the default way the remote gate clears (plan choice F1, approved by Garry); the VM is an opt-in.

Blast radius

This changes what pregate and /ship accept as test evidence: lib/pregate/index.ts (autoCarry, carryGate), lib/ci-carry.ts, bin/gstack-evidence record-ci, lib/ship-bin-common.ts and lib/ship-release.ts (finish, accept, push --early). What keeps it safe is that a carry needs a green same-repository run whose tree.json names HEAD's exact clean tree and covers the inventory. A merge-ref pull_request run on a branch behind main is refused tree_mismatch, as seen live at 9125936 (script ran: ~/.capy/work/gstack/ship-3901/pregate-head.out).

Approvals

Date Asked Exact words Outcome Covers Still pending
2026-11-03 One scoped fix-check on PR #3901 after the round-2 cap (review_loop_grant a102205) “Granted: one scoped fix-check on #3901 at a102205. Record it as review_loop_exception, granted by GStack Minder, "standing grant, GSTA-258 builds, 2026-11-03". Scope it to the three round-2 fixes.” (GStack Minder (standing grant, via GSTA-258)) approved the three round-2 fixes in a102205: record-ci policy label, remote gate hint, changelog and docs wording none

Source: gstack-approvals record for gsta-258-a-ci-carry (display only; not an approval citation).

Summary

Before, at 179b128, the remote gate run took 618 s. After, at 02b2f29, a full gstack-pregate carried Free Tests run 41567501815 (780 of 892 files) and cleared pregate.json/remote_gate (tests=34511 skipped=112) in 27 s.

  • CI carry: findCarry and gstack-ci-carry find|wait. The tests stage looks up the run by itself (--no-ci-carry turns it off). A /ship lane carries only when the base's ship_lanes_from maps its exact command and the run covers its inventory. gstack-evidence record-ci now finds and verifies the run itself and records the base policy that mapped the lane. The receipt records ci_carried.
  • Tree cache: gstack-evidence run --reuse reuses a pass at the same tree, command and runtime. A newer failure vetoes an older pass.
  • Run beside CI: push --early runs the secrets scan and sealed guard first. finish defers a mapped lane it can't carry yet, and writes that preflight-only run to its own file. accept carries the lane from the green run at the final head.
  • F1 on gstack: gstack's .gstack/pregate.json already declares remote_gate_runs on main, so no policy key changed. carryGate clears the gate from the carried run, and the uncleared obligation names the CI route first: push, gstack-ci-carry wait --base main, then rerun gstack-pregate --allow-repo-commands. The local preflight stage and the sealed guard are unchanged.

Gate code (R45, please read)

  • PAID_ONLY dead end, fixed. On a small machine, the files left after a carry were all paid evals (112 at 0fba553). The remote gate reports PREGATE_REMOTE_PAID_ONLY tests=0 for them and clear --run refuses paid_only, so nothing could clear the gate. carryGate now clears it from the same run under clear --run's own checks. Failing-first test: test/pregate-carry-gate.test.ts ("the carried run clears the gate when only skipped files remain…"). A second case shows a run missing an inventory file leaves the gate uncleared; a third shows the CI route is named first, and not under --no-ci-carry.
  • F1 default route: lib/pregate/checks/lanes.ts obligation text, docs/pregate.md ("Small machines and the remote gate", "gstack's own gate"), and the CREW.md REMOTE_PREGATE replacement text in the Captain's drive at handoffs/GSTA-258/A-captain-notes.md.
  • Review fixes with failing-first tests: record-ci took run ids and test counts from its caller (pass 1 red-team); finish overwrote pregate.json with a preflight-only run (pass 1 testing).

Security read

No new dependency, and no workflow, setup or install change. The network calls are GitHub Actions API reads through gh (runs, jobs and the tested-tree artifact) that already existed for clear --run. ship_lanes_from inventory commands are pin-file commands: they run only with --allow-repo-commands and are read only from the base branch.

Test Coverage

New tests: test/ci-carry.test.ts, test/evidence-reuse.test.ts, test/ship-ci-carry.test.ts and test/pregate-carry-gate.test.ts. The coverage audit found thin coverage on accept's refusal branches and on push --early; no tests were generated for those.

Tests ran: typecheck count unavailable
Tests ran: targeted 185

Pre-Landing Review

Pass 1 fixed two INFORMATIONAL findings (record-ci trusted caller-supplied run facts; finish overwrote pregate.json). Pass 2 noted one. Step 11's adversarial reader found three items it rated "Low, blocks: no"; the collector labeled them CRITICAL, so they were fixed in round 2 and checked by one granted fix-check, which noted one more. The outside voice found two defects in main's lib/autoplan-lean.ts (#3897), deferred as issues.

REVIEW_LOOP: passes=2 blocking_found=7 deferred=2 noted=2 fixed=4 scope=frozen unrecorded=3 ledgers_read=3 fix_checks=1 dispatches=6

Gate edits: none detected (6 listed, 0 read; patterns: RH-1,RH-3,RH-4,RH-12,RH-13,RH-14,RH-15,RH-16; unlisted idioms: none)

Outside review: completed (openai/gpt-6.1-sol, medium); request changes for the two main defects below, none in this PR's code.

Review-loop exception: accepted by GStack Minder 2026-11-03 via standing grant, GSTA-258 builds, 2026-11-03: one scoped fix-check after the round-2 cap, scoped to the three round-2 fixes in a102205 (fix-check at a102205, 1 finding)

Deferred findings

Blocking findings in code this PR did not change (review scope: frozen); filed as issues and not closed by this PR.

Review notes

Below the blocking floor (advisory, informational, test-gap or wording items); recorded here and not fixed in this PR.

  • INFORMATIONAL lib/pregate/checks/lanes.ts:536 The new default remote-gate route tells the agent to 'rerun --stage tests' (lanes.ts obligation detail, and docs/pregate.md 'gstack's own gate': gstack-pregate --stage tests --allow-repo-commands). runPregate selects only that stage's checks and writes them over the default .gstack/tmp/pregate.json. The full record's preflight results (regen, secrets, strays, literals, timing, guards) are replaced by a record holding only lanes. verifyPregate never checks that the preflight checks are present, so gstack-pregate verify, gstack-ship-queue ready (local-file path) and the ship receipt's pregateFieldFor all accept the tests-only record as a current pass. If the earlier full run had a preflight fail, such as stale generated output or a secrets hit, following the hint erases it from the record the gates read. Free Tests CI runs no gitleaks scan, so nothing else re-checks secrets at that tree. The docs say the preflight stage 'always run[s] here', but the evidence the gates consume no longer shows it. The ship-queue mirror guard checks only that tests-stage checks are present, not preflight ones.
  • INFORMATIONAL bin/gstack-evidence:695 (fix-check) The new policy field is audit-only: carried and the receipt's ci_carried don't show or check which base policy mapped the lane.

Issues

Refs #3914
Refs #3915

Documentation

Status: updated: three factual doc fixes for the CI-carry change, no blockers.

Scope: base 6f1dfd5b to head a102205e (27 committed files, nothing staged, unstaged or untracked). I searched all tracked doc and template files for gstack-ci-carry, ship_lanes_from, --no-ci-carry, record-ci, gstack-ship-release push --early/accept and the --stage tests --remote route.

Documentation health:
  docs/pregate.md              Updated (added --no-ci-carry to the gstack-pregate usage block)
  CONTRIBUTING.md              Updated (new "Which command do I run?" row for clearing the test tier from CI; Ubicloud row relabeled as the opt-in)
  docs/recommended-harness.md  Updated (first-train step 4: a small machine's test tier clears from a verified CI run when the base declares remote_gate_runs)
  ship/DRIVER.md.tmpl          Current (generated DRIVER.md matches)
  ship/sections/tests.md.tmpl  Current (generated tests.md matches)
  docs/troubleshooting.md      Current (the VM route is listed as one option)
  CHANGELOG.md                 Skipped (changelog.d fragment; parent-owned)
  TODOS.md                     Skipped (parent-owned)

Documentation coverage:

  [entity]                        [reference]  [how-to]  [tutorial]  [explanation]
  gstack-ci-carry find|wait       ✅           ✅        ❌          ✅
  gstack-pregate --no-ci-carry    ✅           ❌        ❌          ✅
  ship_lanes_from                 ✅           ❌        ❌          ✅
  gstack-ship-release accept      ✅           ❌        ❌          ✅
  push --early                    ✅           ✅        ❌          ❌
  ship receipt ci_carried         ✅           ❌        ❌          ❌

Common gaps: ci_carried and gstack-ship-release accept have only reference coverage (docs/pregate.md#ci-carry and ship/sections/tests.md), with no how-to. docs/PROJECT_STRUCTURE.md's bin list does not name gstack-ci-carry; it ends with "etc.". No critical gaps. Diagram drift: none.

Test plan

  • bun run typecheck and bun run typecheck:test (814 known diagnostics, none new)
  • Targeted lane at the stamped tree: 185 pass
  • Focused run at 02b2f29: 380 pass, 0 fail across 28 files
  • Full gstack-pregate at 02b2f29 carried CI and cleared the remote gate
  • Every required check green at the final head (CI)

Not in this PR

Review depth (build C) and the pregate flaky exception (build B). Trial merges at a102205: with B (c935355), one conflict in lib/pregate/index.ts import lines, keep both. With C (de04a78), the conflicts are all C-against-main hunks (C conflicts with main alone in 16 files); this PR's ciCarried hunk in bin/gstack-ship-receipt is not in any conflict.

garrytan and others added 30 commits October 31, 2026 07:21
…ested fixes no longer force a second review loop (GST-407, GST-384, GST-391)

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>
…-triggers

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

# Conflicts:
#	ship/DRIVER.md
#	ship/DRIVER.md.tmpl
…ds; trim elsewhere

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>
comparePath returns same only when every hunk sits where the base change puts it (patch-ids ignore positions) and treats a file-mode change as changed; the scoped-review packet says when a fence is truncated; --docs-result must be the posted audit's result; the --context-reviewed record goes beside the packet, outside the worktree. Negative controls for each.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A test edit routes as tests= only when it adds lines with no gate tag; a removed or changed line or an unreadable test diff goes through the full loop. Diffs skip textconv. A hunkless patch (binary, empty, mode-only) is same when its patch-id matches. Without --reviewed-base test files route as before. finish's packet path and attempt's state directory have fallbacks.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…ew is release metadata (GBRA-251)

gateEditedPaths reads removed lines only inside hunks; carry refuses when a path listing fails; docs freshness stops on a failed listing; attempt counts an unreadable state file. releasePaths includes stamp_files paths whose edit is a version swap under stamp_patterns.

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

A test-only edit with no gate tag gets the scoped fix-check of its test hunks instead of a lanes-only rerun. Packet write failures print a STOP or RECEIPT_CARRY_REFUSED. attempt's allowance uses an exclusive create.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…t diff outside context paths

The attempt STOP no longer echoes the audit child's fix text. A scoped-review carry now requires the product patch-id without the context paths to match at both heads.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…ch; name-only test globs only in test dirs

A scoped-review packet section over 200 lines sends that path to the full loop instead of a truncated packet. The docs-result path match is exact. test_*.py, *Test.java and similar count as test code only under a test directory.

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>
…roubleshooting (docs-a-1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…like ship-release (run 41193336209)

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

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

# Conflicts:
#	bin/gstack-ship-receipt
… and repair when a pass's tree moved (GST-430)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…e receipt fails closed on a failed diff (GST-448)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
… review; carry --dry-run writes no packet (GST-442)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…the --docs-requested fix; trims keep the cap (GST-442, GST-444)

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

- A notes-only pass is recorded clean only when every finding is fixed, or noted or deferred below the
  blocking floor (never CRITICAL or blocking), by its logger-stamped action, and the findings account
  for the claimed issue and critical counts (GST-430).
- The preflight scoped carry route commits and pushes the base-merge fix before writing the packet (GST-442).
- patchId refuses by name on an unwritable TMPDIR; the tree receipt names why its diff failed (GST-448).
- Step 16 stage 3 spells out --docs-requested with its --docs-result (GST-444).

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>
…ng reads UNVERIFIED (red-team, pass 1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…n rule, stale patch-id dirs swept

- deriveFromFindings stamps gate rows with the session kind before deriving status, so a findings file cannot
  dispose of a gate finding the unattended logger forces open (outside-voice#1).
- reviewFreshness reads a claimed row's findings with isOpenByAction, the rule the notes-only rewrite uses;
  noted and deferred clear a finding only when it is marked blocking: false and is not CRITICAL.
- patchId sweeps gstack-patch-id-* directories over an hour old that a killed carry left in TMPDIR.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…ion; resolved gate, skipped and below-floor actions stay CURRENT

- isOpenFinding treats action 'open' (the logger's forced-open stamp) as open before a row's status or disposition.
- reviewFreshness flags a claimed clean row only for an 'open' action or a CRITICAL or blocking deferral or note, so
  interactive kept and restored gates, skipped advisories and INFORMATIONAL deferrals read CURRENT as before.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…the git dir; changelog matches the review-log floor

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
… finding reads UNVERIFIED (pass 2 red-team)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…fusal (docs-d-1 audit)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…hip-workflow-clarity pin)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…timeout (60 s); pregate literals check

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
garrytan and others added 7 commits November 2, 2026 19:52
…11 (rule 19 grant)

Conflicts resolved keeping both sides: bin/gstack-review-plan (baseContainsHead and approval-record imports); scripts/harness-version.json (main's session-ledger and session-runner pins, the wave's skill-fixture pin); ship/DRIVER.md.tmpl (main's done-or-voices wording, regenerated DRIVER.md 12,278 B); test/review-packets-removed.test.ts (merged review-army.md, adversarial.md and review-depth.ts pinned under combined GST-508+GST-464+GST-967 and GST-508+R51+GST-911+GST-967 entries).
…508 placeholders

The merged sectionTexts differ from main's by exactly the wave's GST-508 exclude-pathspec lines (merged minus main equals wave minus fc292e2); the 1,440-case plan grid still hashes to main's MAIN_PLANS. Checks: GStack Minder drive handoffs/GSTA-202/merge-6841-checks.md.
…/accept split (GSTA-258 A)

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

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: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

# Conflicts:
#	.gstack/pregate.json
#	bin/gstack-review-dispatch
#	bin/gstack-ship-receipt
#	docs/pregate.md
#	docs/troubleshooting.md
#	lib/pregate/config.ts
#	lib/ship-policy.ts
#	ship/DRIVER.md
#	ship/DRIVER.md.tmpl
#	test/review-exclude.test.ts
#	test/review-packets-removed.test.ts
#	test/review-targeted.test.ts
…s, so a paid-only remainder is not a dead end

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

trunk-io Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

😎 This pull request was merged.

garrytan and others added 4 commits November 3, 2026 01:54
…ated KEPT entry

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

/ship pass 1 findings red-team#1 and specialist-batched#1 (GSTA-258 piece A).

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>

# Conflicts:
#	lib/pregate/checks/lanes.ts
… is opt-in (plan choice F1)

The uncleared remote_gate obligation names the CI route first when the base
declares remote_gate_runs. docs/pregate.md says how gstack clears it, including
the pull_request merge-ref tree mismatch. GSTA-258 piece A.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
garrytan and others added 3 commits November 3, 2026 02:59
record-ci records the base policy that mapped the lane; the CI-first remote
gate hint respects --no-ci-carry and reruns the whole pregate; changelog and
docs say what the tool does. GSTA-258 piece A.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…sage line (ship docs audit)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
@github-actions github-actions Bot changed the title ship: CI is the one full test run (CI carry, tree cache, /ship beside CI) v1.94.0.0 ship: CI is the one full test run (CI carry, tree cache, /ship beside CI) Nov 3, 2026
@capy-ai
capy-ai Bot merged commit 4ec1722 into main Nov 3, 2026
46 checks passed
garrytan added a commit that referenced this pull request Nov 3, 2026
1.94.0.0 shipped as #3901 without the key, so the released-key test reds once main's CHANGELOG is in the tree. The slot stamp moves the tentative value through stamp_paths.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
capy-ai Bot added a commit that referenced this pull request Nov 3, 2026
…y records HEAD's version (GST-1026, GST-1030) (#3892)

* fix(stamp): name branch lines by position; carry and finish accept a kept VERSION claim (GST-979, GST-980)

BranchSide carries the positions of the branch-added lines and stampOnlyLine takes the removed line position, so a base line whose text duplicates a branch line keeps the old-version floor. At equal versions only the branch own lines may move. stampOnlyText and stampedFiles accept a kept claim for those lines, and the carry leaves a stamp file out of the product comparison when its only change since the reviewed head is a stamp on the branch own rows and the base did not touch it. Failing-first: all five new tests fail on main fc292e2.

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

* fix: pre-landing review fixes (GST-980 carry reads the stamp file line by line at the branch's positions, and keeps its mode)

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

* docs(changelog): GST-979/980 entry counts the seven tests

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

* docs: the receipt carry follows a stamp on the branch's own rows (GST-980)

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

* docs: keep docs/ship-policy.md at the reviewed text; its GST-980 sentence already states the carry rule

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

* Revert "docs: keep docs/ship-policy.md at the reviewed text; its GST-980 sentence already states the carry rule"

This reverts commit f926ccb.

* fix(stamp): a declared placeholder restamped on the branch's own row is a stamp; the carry names HEAD's version (GST-1026, GST-1030)

stamp_placeholders (default []) lets a repo declare literals such as TBD that its
restamp replaces with the new version inside a stamp_patterns template. stampOnlyLine
accepts that move only on a branch line named by position; finish's stampedFiles,
the receipt carry and the tree receipt share it. The carried receipt's version is
HEAD's, read the way write reads it.

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

* fix: pre-landing review fixes (carry keeps a write --version receipt's version without a version source; a placeholder fill composes with a stamp move; a bare {version} template and a blank placeholder take no placeholder)

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

* docs(changelog): GST-1026/1030 fragment names the review fixes

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

* fix(ship-receipt): carry masks only package.json version on a pin-bump PR (GST-1030, GBEV-3)

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

* refactor(ship-policy): stamp key validation moves to lib/ship-policy-stamps.ts for the module-size ratchet

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

* fix(ship-policy): stamp_placeholders key names the next minor 1.95.0.0

1.94.0.0 shipped as #3901 without the key, so the released-key test reds once main's CHANGELOG is in the tree. The slot stamp moves the tentative value through stamp_paths.

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

* test(restamp-mentions): set the stamp file's exec bit through the index so the mode-change carry case holds on Windows

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

* unstamp: return VERSION, package.json, CHANGELOG and the digest to main f6d6215's values and restore the changelog fragment after #3892 left train 100

The tentative STAMP_PLACEHOLDERS_KEY_VERSION goes back to 1.95.0.0 for the next slot stamp to move.

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant