[garrytan]

{
  "schema_version": 1,
  "pr": 3654,
  "head": "c50c93bf2f6c259992d4be563f3f923157dc30b4",
  "version": "1.91.340.0",
  "base": "main",
  "gate": {
    "tests": {
      "pass": 19892,
      "fail": 0,
      "skip": 0
    }
  },
  "session_kind": "unattended",
  "head_tree": "88758677d30ead193b42fb486bb055796820b333",
  "product_patch_id": "f441cbc25737e6344841139e8933296dea005440",
  "gstack_version": "1.92.0.0",
  "review_depth": {
    "depth": "full",
    "class": "gate",
    "runtime_lines": 49,
    "rules": "55726fab80631072",
    "base": "7bc2034724bffe2ecf84e215c443e1a5282e9d89",
    "registry": "7bc2034724bffe2ecf84e215c443e1a5282e9d89",
    "gate_scan": {
      "tagged": 0,
      "head": "c50c93bf2f6c259992d4be563f3f923157dc30b4"
    },
    "reasons": [
      "gate-class",
      "runtime=49<=50"
    ]
  },
  "pregate": "requires-remote cleared @88758677d30e (1 checks, current for c50c93bf2f6c)",
  "requires_remote": [
    "free-tests.yml/macos-named-regressions: https://github.com/garrytan/gstack/actions/runs/41121713213",
    "windows-free-tests.yml/windows-free-shard: https://github.com/garrytan/gstack/actions/runs/41121718970",
    "pregate.json/remote_gate: remote-gate tree=88758677d30e tests=19892"
  ],
  "issues": {
    "fixes": [],
    "refs": [
      3603
    ],
    "flakes": []
  },
  "docs": {
    "status": "updated",
    "scope": "docs/ship-policy.md (gstack's own files), captain/SKILL.md.tmpl, docs/skills.md, changelog.d/README.md against the 7bc2034..c50c93b diff; docs/captain.md and captain/templates already teach train land"
  },
  "review_loop": {
    "passes": 1,
    "blocking_found": 0,
    "deferred": 0,
    "noted": 7,
    "fixed": 4,
    "scope": "frozen",
    "fix_checks": 0,
    "dispatches": {
      "specialist": 1,
      "red-team": 1
    }
  }
}

Summary

gstack now versions its own PRs at merge time. With this merged, a gstack PR adds changelog.d/<branch-slug>.md and no version, and trains merge through train land instead of slot calls. This is the policy flip (P) from GSTA-154's approved plan: #3594, then #3595, then #3613, then this PR, then the pilot train.

Why it matters. Every PR used to pick a version before it merged, so each merge made the next PR's version stale and its lane redid the stamp. #3594, #3595 and #3613 built the merge-time path; this turns it on for gstack.

What changed

• changelog_fragments is on (.gstack/ship-policy.json, changelog.d/README.md). required_checks lists the six checks every PR runs: free-tests, windows-free-tests, Check VERSION is not stale vs queue, quality, check-freshness, actionlint. Path-filtered workflows (Windows Setup E2E, make-pdf gate, Native ARM Setup Smoke, Dependency Review) are left out, because a stamp commit of a PR outside their paths never gets those checks and train land would hold on them. Branch protection enforces only free-tests.
• min_gstack_version is 1.91.340.0, the first release that reads required_checks and counts a stamped slot as merged only when GitHub reports it MERGED. An older gstack refuses the policy by name (POLICY_GSTACK_TOO_OLD) instead of failing on an unknown key.
• CHANGELOG_FRAGMENTS_KEY_VERSION is 1.91.336.0, the version v1.91.336.0 ship-queue: assign VERSION/CHANGELOG at merge time (changelog fragments + gstack-ship-queue land) #3594 landed at, in place of the placeholder 1.92.0.0. Test fixtures that pinned the placeholder move with it.
• mergeChangelogs handles v1.91.340.0 ship-queue: train land counts a slot as merged only when GitHub reports it MERGED (#3603) #3613's shape (lib/changelog-check.ts). A stacked child whose only own line sits inside its released parent's list used to return null, so v1.91.340.0 ship-queue: train land counts a slot as merged only when GitHub reports it MERGED (#3603) #3613's slot needed a hand resolve. When filing inserted lines as additions to the parent would leave the child nothing of its own, they are now the child's entry. A child entry that repeats a released parent line (a reordered or duplicated bullet) still returns null. On v1.91.340.0 ship-queue: train land counts a slot as merged only when GitHub reports it MERGED (#3603) #3613's real CHANGELOGs the result equals the resolve that shipped as 1.91.340.0.
• /captain and docs teach train land per slot (captain/SKILL.md.tmpl, docs/skills.md), and docs/ship-policy.md's "gstack's own files" section shows the new policy.

Landing notes

• Version Gate reads the base's policy, so this PR is judged with the key off and carries an [Unreleased] entry. After it lands, a PR with only [Unreleased] still passes during migration.
• Land it alone or as the last slot of its train. A slot after it in a train built before the flip would land under the new key without stamped prefixes.
• CREW.md's REQUIRED_CHECKS still lists the path-filtered workflows; the controller may want to match it to this list.

Test plan

• bun run typecheck
• Focused suite: changelog merge, ship policy, fragments, land, train land, train stamp, train, Version Gate, restamp, gate reuse, evals workflow, doctor, parity and size guards. Two test/gstack-restamp-queue.test.ts cases time out at 5 s on this 4-core machine, and the same cases time out on main 7bc2034 here; they pass in the remote run.
• Remote free tier (gstack-pregate --stage tests --remote) at tree 88758677: 19892 tests, 0 failed; macOS and Windows lanes cleared by dispatched runs 41121713213 and 41121718970
• bun run gen:skill-docs freshness

🤖 Generated with Claude Code

Issues

Refs #3603

[trunk-io]

😎 This pull request was merged.