Skip to content

v1.91.283.0 fix(benchmark): reconcile the collection, comparison, budget and trend phases with the vet-the-number section (GSTA-128) - #3520

Merged
capy-ai[bot] merged 5 commits into
mainfrom
flaky-2026-10-27-bench
Oct 27, 2026
Merged

capy-ai[bot] merged 5 commits into
mainfrom
flaky-2026-10-27-bench

Conversation

@garrytan

@garrytan garrytan commented Oct 27, 2026 •

Copy link
Copy Markdown
Owner
{
  "schema_version": 1,
  "pr": 3520,
  "head": "30f4c25874328668c8d04be394f48f72f4d652b4",
  "version": "1.91.281.0",
  "base": "main",
  "gate": {
    "remote-free-gate": {
      "pass": 18028,
      "fail": 0,
      "skip": 0
    },
    "free-tests.yml": {
      "pass": 1,
      "fail": 0,
      "skip": 0
    },
    "windows-free-tests.yml": {
      "pass": 1,
      "fail": 0,
      "skip": 0
    },
    "llm-judge perf collection": {
      "pass": 1,
      "fail": 0,
      "skip": 0
    }
  },
  "session_kind": "unattended",
  "pregate": "requires-remote cleared @247d55926b3e (1 checks, current for 7bcd06ecf290)",
  "requires_remote": [
    "free-tests.yml/macos-named-regressions: https://github.com/garrytan/gstack/actions/runs/40575772087",
    "windows-free-tests.yml/windows-free-shard: https://github.com/garrytan/gstack/actions/runs/40575772146",
    "pregate.json/remote_gate: remote-gate tree=247d55926b3e tests=18028"
  ],
  "issues": {
    "fixes": [],
    "refs": [
      3520
    ],
    "flakes": []
  },
  "docs": {
    "status": "updated",
    "scope": "docs/, README.md, CLAUDE.md, AGENTS.md, CONTRIBUTING.md, benchmark/SKILL.md (128 docs inventoried); docs/skills.md /benchmark section corrected"
  },
  "review_loop": {
    "passes": 1,
    "blocking_found": 0,
    "deferred": 0,
    "noted": 0,
    "fixed": 0,
    "scope": "frozen"
  },
  "carry": {
    "from": "7bcd06ecf2906a540bf9a7635d1e35bd241f0c24",
    "reason": "base merge + release metadata",
    "product_patch_id": "d5918ca26ae738a673344c28c1115f7dca417885",
    "changed_paths": [
      "metadata:CHANGELOG.md",
      "metadata:VERSION",
      "metadata:agents-digest/gstack-AGENTS.md",
      "product:captain/templates/slot-call.md",
      "product:docs/captain.md",
      "product:docs/ship-policy.md",
      "product:docs/troubleshooting.md",
      "product:lib/changelog-check.ts",
      "product:lib/restamp.ts",
      "product:lib/ship-queue-train-verify.ts",
      "product:lib/ship-queue-train.ts",
      "metadata:package.json",
      "test:test/changelog-merge-damage.test.ts",
      "test:test/fixtures/merge-train-3453/base-d87eec95.md",
      "test:test/fixtures/merge-train-3453/main-3e4240a7.md",
      "test:test/fixtures/merge-train-3453/main-6ff98c66.md",
      "test:test/fixtures/merge-train-3453/pin-a78ce08a.md",
      "test:test/helpers/free-fixtures-data.ts",
      "test:test/helpers/ship-queue-train-fixture.ts",
      "test:test/restamp-base-merge.test.ts",
      "test:test/ship-queue-train.test.ts"
    ],
    "merge_commits": 1,
    "range_diff": "1:  229e874e0 = 1:  229e874e0 fix(benchmark): reconcile the collection, comparison, budget and trend phases with the vet-the-number section\n2:  45e3195c1 = 2:  45e3195c1 changelog: /benchmark phases reconciled with the vet-the-number section (GSTA-128)\n3:  7bcd06ecf = 3:  7bcd06ecf docs: /benchmark runs five times per page in docs/skills.md\n-:  --------- > 4:  30f4c2587 RESTAMP: 1.91.282.0 -> 1.91.283.0 (stamped; queue_mode=stamp-at-merge base=origin/main@9ccb5233f309 policy=base origin/main@9ccb5233f309:.gstack/ship-policy.json) ship, next in queue at 1.91.283.0 STAMP_VERSION: 1.91.283.0 claims: ignored (stamp-at-merge) stage version: done (wrote 1.91.283.0) stage release_tool: done (bun scripts/gen-agents-digest.ts) stage changelog: done (Unreleased -> 1.91.283.0) stage stamp_paths: skipped (no tentative mention newer than the fork version 1.91.281.0 and none of base 1.91.282.0 on a line this branch added) stage mirror: skipped (no mirror in policy) stage apply: done (4 file(s)) diff --git a/CHANGELOG.md b/CHANGELOG.md index 695e20bd5..15162a5d0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@  # Changelog",
    "covers": [
      "pre-landing review",
      "adversarial review",
      "gate integrity",
      "documentation audit"
    ],
    "reruns": [
      "CI at head (gstack-ship-queue ready requires it); test and helper code changed since the reviewed head runs there unreviewed"
    ]
  }
}

What changed

Phase 5 now says how the seven vet-the-number questions apply against a stored baseline: compare each delta with both sides' spread, name the limiter, and call one-run comparisons inconclusive

Phase 5 before (main) and after (this branch): the comparison now opens with a verdict, names the run count, and says what a stored-baseline comparison can and cannot claim.

Before/after as text: Phase 5 now says how the seven vet-the-number questions apply against a stored baseline: compare each delta with both sides' spread, name the limiter, and call one-run comparisons inconclusive
--- Before · benchmark/SKILL.md.tmpl § Phase 5: Comparison at 392f50d · source text
+++ After · benchmark/SKILL.md.tmpl § Phase 5: Comparison on this branch · source text
 ### Phase 5: Comparison
 {{SECTION:vet-the-number}}
 
+If baseline exists, compare current metrics against it. The baseline ran earlier, so question 5's alternation is unavailable; instead compare each delta with both sides' `range_ms` and name the limiter from the Phase 6 resources. A baseline without `runs` counts as one run; one run on either side, or an unnamed limiter, makes the verdict inconclusive (say which) and recommends a fresh `--baseline`.
+Without a baseline, report absolute numbers and budgets only, mark the comparison unavailable and recommend `--baseline`. Missing metrics remain N/A. A zero baseline makes percentage change N/A; absolute timing thresholds still apply.
-If baseline exists, compare current metrics against it:
-Without a baseline, report absolute measurements and budgets only, mark comparison unavailable, and recommend a `--baseline` run. Missing metrics remain N/A. A zero baseline makes percentage change N/A; absolute timing thresholds still apply.
 
 ```
 PERFORMANCE REPORT — [url]
 ══════════════════════════
+VERDICT: slower — LCP 800ms → 1600ms at the median, outside both ranges, bound by the hero image decode
 Branch: [current-branch] vs baseline ([baseline-branch])
+Runs: 5 per side (medians; ranges in the JSON report)
 
 Page: /
-─────────────────────────────────────────────────────
 Metric              Baseline    Current     Delta    Status
-────────            ────────    ───────     ─────    ──────
 TTFB                120ms       135ms       +15ms    OK
 FCP                 450ms       480ms       +30ms    OK
 LCP                 800ms       1600ms      +800ms   REGRESSION
@@ ⋯ 6 unchanged ⋯ @@
 CSS Bundle          85KB        88KB        +3KB     OK
 
 REGRESSIONS DETECTED: 4
+  [1] LCP 800ms → 1600ms — a large new image or blocking resource
+  [2] Transfer 1.2MB → 1.8MB — new JS bundles
+  [3] JS 450KB → 720KB — new dependency or missing tree-shaking
+  [4] Full load 1400ms → 2100ms — see Phase 6
-  [1] LCP doubled (800ms → 1600ms) — likely a large new image or blocking resource
-  [2] Total transfer +50% (1.2MB → 1.8MB) — check new JS bundles
-  [3] JS bundle +60% (450KB → 720KB) — new dependency or missing tree-shaking
-  [4] Full load +700ms (1400ms → 2100ms) — inspect the slowest resources
 ```
 
 **Regression thresholds:**
@@ ⋯ 2 unchanged ⋯ @@
 - Bundle size and total transfer: >25% increase = REGRESSION
 - Bundle size and total transfer: >10% increase = WARNING
 - Request count: >30% increase = WARNING (no separate regression threshold)
+Apply REGRESSION before WARNING; otherwise OK. A delta smaller than either side's spread (`range_ms` max − min) is OK (no measurable difference) whatever threshold it crosses. Negative deltas are improvements.
-Apply REGRESSION before WARNING; otherwise OK. Negative deltas are improvements.

Daily flaky pass (GSTA-128) follow-up for the benchmark/SKILL.md perf collection judge case, which failed twice on the #3518 screen (run 40558235014, clarity 3 < 4, completeness 3 < 4, actionability 3 < 4, 3 samples each) on bytes train 25's gate had judged 24/24 two hours earlier.

Diagnosis. All six judge samples name the same contradictions in Phases 3–9, so the case sits at its threshold on real prose conflicts, not judge noise:

"the mandatory vet-the-number section demands ≥5 alternating A/B runs per side, but comparisons are against a stored baseline.json that cannot be interleaved, and Phase 3 only says 'run 3 times if the user wants stable numbers' — the agent is left to reconcile this" (attempt 1, sample 1)
"Phase 7's rule counts PASS+WARNING as 'below budget' … yet the sample output grades 'B (4/6 passing)'" (rerun, sample 2)
"the trend table shows a Grade column, yet the baseline schema stores no grade, and it's unclear whether trends read baselines or Phase 9 JSONs (whose schema is never defined)" (attempt 1, sample 1)

Repair (benchmark/SKILL.md.tmpl, regenerated SKILL.md; the vet-the-number section is untouched):

  • Phase 3 runs the script 5 times per page and later phases use each metric's median with its range, which the Garry-approved vet section (question 5) already demanded; the optional 3-run median was the contradiction. --quick is named as the one-run ballpark with no comparison verdict.
  • Phase 4's baseline schema carries runs and range_ms.
  • Phase 5 says how the seven questions apply against a stored baseline: alternation is unavailable, so compare each delta with both sides' spread, name the limiter from Phase 6, and call the verdict inconclusive when either side is one run (a baseline without runs counts as one). A delta smaller than either spread is OK whatever threshold it crosses. The report leads with the verdict and names the run count.
  • Phase 6 defines third-party and what a recommendation names; Phase 7's grade example reads "4/6 below budget: 3 PASS, 1 WARNING, 2 FAIL"; Phase 8 reads the benchmark and baseline JSON files by timestamp and says where Bundle and Grade come from; Phase 9 defines the JSON (Phase 4 object plus per-page grade, verdict and metric status) and uses the same UTC-timestamp filename as Phase 4.
  • Nearby prose tightened (persona, Phase 1 refresh note, example rulers and recommendation lines, Important Rules) so the skeleton stays under its 31,300-byte cap: 30,781 → 31,290 bytes. No cap, pin, threshold, trial count, sample count or budget changed.
  • /ship's documentation audit (7bcd06e) corrected docs/skills.md: the /benchmark section said "Multiple runs averaged" and "3 runs each"; it now says five runs per page, median with range, --quick a single-run ballpark.

Why

The vet-the-number section (absorbed from pstack, #3487) made the skill contradict itself on run counts and on what a stored-baseline comparison can claim; a judge reading the whole bundle has to pick a side. This resolves the demonstrated ambiguities together in the skill's own phases instead of adding clauses.

Verification

  • Judge after the repair (EVALS=1 EVALS_TIER=gate … bun test test/skill-llm-eval.test.ts -t 'benchmark/SKILL.md perf collection'): clarity, completeness, actionability 4/4/4 on all three samples, four runs ($0.06 each): three on the repaired tree before the commit, one by /ship on the committed benchmark/SKILL.md bytes (sha256 15ac49f4, unchanged by 7bcd06e).
  • Remote pregate on Ubicloud, whole free tier: 17,995 tests / 0 failed at tree 51899fae (45e3195), then 18,028 / 0 at tree 247d5592 (7bcd06e); $0.06 + $0.08.
  • Focused free guards: parity suite, skill-md-size guard, context-budget ratchet, pstack-sections, gen-skill-docs freshness, prose lint: all green (Exploratory QA below). The earlier 1007/0 focused run on the pre-commit tree stands as supporting evidence.

Approvals

Standing: CREW.md rule 16 (daily flaky pass, Garry 2026-10-19); GStack Minder's go for this follow-up (2026-10-27). Lane paid spend $0.24 of the $10 cap (four judge runs); Ubicloud $0.14.

Blast radius

Two prose files and one doc: benchmark/SKILL.md.tmpl, its generated SKILL.md (bun run gen:skill-docs ran at both heads, tree clean, 31,290 bytes), and the /benchmark paragraph of docs/skills.md. The vet-the-number section, the carve guard entry, every test and every other skill are unchanged (gate scan: 0 eligible hunks). Behavior change for users of /benchmark: five runs per page by default instead of one (the section already required it before any comparison was reported), and --quick keeps the single run. Rung: script ran (regen, guards, judge, remote free gate).

Summary

The benchmark/SKILL.md perf collection judge read Phases 3–9 and found the skill arguing with its own vet-the-number section about run counts and what a stored-baseline comparison can claim. The phases now say five runs, medians with ranges, and a verdict that calls one-run comparisons inconclusive; the judge rates the bundle 4/4/4 four times running. Commits: the template repair, the CHANGELOG entry, and the docs/skills.md correction from /ship's documentation audit.

Test Coverage

Skipped audit: prose-only diff (benchmark/SKILL.md.tmpl, generated SKILL.md, CHANGELOG, docs/skills.md). Phases 3–9 are [→EVAL] paths covered by the judge case 'benchmark/SKILL.md perf collection' (test/skill-llm-eval.test.ts:630, spans Phase 3 to Important Rules). No new application code paths to audit.

Tests: 1501 → 1501 (+0 new)
Coverage gate: could not determine percentage — skipping.
Tests ran: remote-free-gate 18028 · free-tests.yml macos-named-regressions (CI run 40575772087) · windows-free-tests.yml windows-free-shard (CI run 40575772146) · llm-judge perf collection 1

Pre-Landing Review

No issues found. Core checklist clean; specialists testing, maintainability, security, performance, simplification: NO FINDINGS; state-machines skipped (scope); Red Team not activated (144 lines, no CRITICAL).
REVIEW_LOOP: passes=1 blocking_found=0 deferred=0 noted=0 fixed=0 scope=frozen
Gate edits: none detected (0 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: Codex CLI not installed; the outside voice was a Capy subagent on openai/gpt-6.1-sol (adversarial pass, NO FINDINGS, "Recommendation: proceed"). Native adversarial pass (anthropic/claude-fable-5-1): nine INFORMATIONAL findings, all below the rule-23 floor, noted below and fixed in no pass.

Review notes

Native adversarial findings on benchmark/SKILL.md.tmpl, kept as notes (none would fail a test, break production or lose data; six ask for design beyond the judged contradictions, two concern example content the diff only tightened; the judge passed these bytes 4/4/4 four times). A follow-up prose pass is the owner's call; any such edit must re-tighten under the 31,300-byte cap (10 bytes of headroom).

  1. Spread rule (line 186, "smaller than either side's spread") vs the VERDICT example ("outside both ranges"): one noisy run on either side could relabel a REGRESSION as OK with no visible marker. Suggested: one noise test and an OK (within noise) status.
  2. "Name the limiter from the Phase 6 resources" (line 150) always yields a top entry, so the unnamed-limiter inconclusive branch rarely fires; the named resource may not be on the metric's critical path.
  3. The "within 3s" words left the NAV= explanation (line 99) while the script keeps setTimeout(…, 3000); a null LCP stays N/A in Phase 7 (pre-existing handling), and the median rule does not say how a null among five runs is reported.
  4. The Phase 6 example (line 204) recommends lazy-loading hero-image.webp, the resource the VERDICT example names as the LCP limiter, and names two remedies against the new one-remedy rule.
  5. Phase 8 trend (line 230) mixes one-run --quick files and baseline files with five-run benchmarks and shows neither runs nor branch.
  6. --quick "no comparison verdict" (line 109) does not say to skip Phase 5, so a one-run delta table could still print.
  7. A failed run among the five has no field: the schema carries runs and range_ms and no failure count (line 111).
  8. "Recommends a fresh --baseline" (line 150) does not say on which branch.
  9. 10 bytes of headroom under the skeleton cap (benchmark/SKILL.md 31,290 / 31,300).

Exploratory QA

Functional smoke, 8 captures in 55 s of a 300 s budget, all pass: skeleton size cap (31,290 ≤ 31,300); gen:skill-docs leaves the tree clean; skill-md-size-guard 2/0; parity-suite 2/0; pstack-sections 8/0; prose lint ok on the template and the CHANGELOG entry; context-budget-ratchet 7/0; the Phase 7 grade example (3 PASS, 1 WARNING, 2 FAIL = 4/6 below budget) matches its table. Report with linked checkpoints 002–008: .gstack/qa-reports/ship3520-20261027T195340Z/functional/report.md (lane machine). Limits: no live /benchmark run against a page (browser-bound surface outside the smoke budget; Phases 3–9 are judged by the paid eval); test/carve-guards.test.ts does not exist on this tree, so the carve guards were exercised through the size-guard and parity captures.

Design Review

No frontend files changed — design review skipped.

Eval Results

benchmark/SKILL.md perf collection (llm-judge, EVALS_TIER=gate): PASS c:4 c:4 a:4, $0.06, 26 s, run id ship3520-judge on the committed bytes (judge log: ~/.capy/work/flaky/ship3520/judge/out.log on the lane machine). Three earlier runs on the same bytes before the commit: PASS 4/4/4 each, $0.06 each (~/.capy/work/flaky/bench/judge-run{,2,3}/). Lane paid total $0.24.

Greptile Review

No Greptile comments.

Scope Drift

Scope Check: CLEAN
Intent: reconcile /benchmark Phases 3–9 with the vet-the-number section so the perf-collection judge stops failing on real contradictions
Delivered: benchmark/SKILL.md.tmpl + regenerated SKILL.md, CHANGELOG [Unreleased] entry, docs/skills.md run-count correction

Plan Completion

Plan completion audit: not run (no plan is bound to this branch and no docs/designs/ file matches). Fix: add "Plan: " to the PR body, or run /autoplan.

Issues

Refs #3520

Verification Results

No plan-specific verification items (no plan file); automatic diff-scoped QA above: 8 PASS, 0 FAIL, 0 BLOCKED, 0 NOT RUN.

TODOS

No TODO items completed in this PR.

Documentation

Status: updated. One factual correction in docs/skills.md, no blockers.

Scope: base 392f50d, branch flaky-2026-10-27-bench, mode edit. The committed diff touches benchmark/SKILL.md.tmpl, its generated benchmark/SKILL.md and the CHANGELOG [Unreleased] entry. There are no staged, unstaged or untracked changes. The audit covered the candidate's 128 inventoried docs. The banned-terms check returned none.

Documentation health:

  • docs/skills.md: updated. The /benchmark section said "Multiple runs averaged" and showed "3 runs each"; it now says five runs per page, median with range, and --quick as a single-run ballpark.
  • README.md: current. The /benchmark row names no run counts.
  • CHANGELOG.md: current. The [Unreleased] entry matches the template change. It was not edited.
  • benchmark/SKILL.md.tmpl and benchmark/SKILL.md: reviewed, not edited (the generated file is already in the diff).

Coverage debt: /benchmark has reference coverage in README.md and docs/skills.md, with no how-to, tutorial or explanation page. That is existing debt, not caused by this change. /document-generate could fill it.

Diagram drift: none. The diff touches no ASCII or Mermaid diagram entities.

Test plan

  • gstack-pregate --stage tests --remote --spend-cap 2 --timeout 2700 --allow-repo-commands at tree 247d5592: 18,028 tests, 0 failed ($0.08); at tree 51899fae: 17,995 / 0 ($0.06)
  • EVALS=1 EVALS_TIER=gate bun test test/skill-llm-eval.test.ts -t 'benchmark/SKILL.md perf collection': PASS c:4 c:4 a:4 ($0.06)
  • bun test test/skill-md-size-guard.test.ts test/parity-suite.test.ts test/pstack-sections.test.ts test/context-budget-ratchet.test.ts: 19 pass / 0 fail
  • bun run gen:skill-docs: tree clean; wc -c benchmark/SKILL.md = 31290
  • pull_request CI at 7bcd06e: 45 passed, 0 failed, 11 skipped (Quality gate green on its rule-16 rerun, attempt 2, after attempt 1 was cancelled at the job timeout inside Install ShellCheck)

🤖 Generated with Claude Code

garrytan and others added 2 commits October 27, 2026 19:40
…d phases with the vet-the-number section

The perf-collection judge (run 40558235014, both attempts, six samples) named
the same contradictions: Phase 3 offered an optional 3-run median while the
mandatory vet section demands 5 alternating runs per side and a stored
baseline cannot be interleaved; the budget example read '4/6 passing' against
a rule that counts WARNING as below budget; the trend table showed Grade and
Bundle columns no stored file defined; Phase 9 named two files with no
contents. Phase 3 now runs 5 per page with median and range and names
--quick as the one-run ballpark; the baseline schema carries runs and
range_ms; Phase 5 says how the seven questions apply against a stored
baseline (compare the delta with both spreads, name the limiter from Phase 6,
inconclusive when either side is one run); the grade example counts 3 PASS,
1 WARNING, 2 FAIL; Phase 8 reads the benchmark and baseline JSON files by
timestamp; Phase 9 defines the JSON as the Phase 4 object plus grade, verdict
and per-metric status. Nearby prose tightened so the skeleton stays under its
31,300-byte cap (31,290). Judge after the repair: clarity, completeness and
actionability 4/4/4 on all three samples, twice.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…on (GSTA-128)

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

trunk-io Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

😎 This pull request was merged.

garrytan and others added 3 commits October 27, 2026 20:10
Step 14.5 of /ship on #3520: the /benchmark section said 'Multiple runs averaged' and
'3 runs each'; it now matches Phase 3 (five runs per page, median with range, --quick a
single-run ballpark). GSTA-128.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Train slot 2 stamp for #3520 (GStack Minder slot call, base 9ccb523, order 3520,3497). CHANGELOG.md resolved with mergeChangelogs (additive); no other conflicts.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
… base=origin/main@9ccb523 policy=base origin/main@9ccb5233f309:.gstack/ship-policy.json)

ship, next in queue at 1.91.283.0
STAMP_VERSION: 1.91.283.0
claims: ignored (stamp-at-merge)
stage version: done (wrote 1.91.283.0)
stage release_tool: done (bun scripts/gen-agents-digest.ts)
stage changelog: done (Unreleased -> 1.91.283.0)
stage stamp_paths: skipped (no tentative mention newer than the fork version 1.91.281.0 and none of base 1.91.282.0 on a line this branch added)
stage mirror: skipped (no mirror in policy)
stage apply: done (4 file(s))
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 695e20b..15162a5 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,6 +1,6 @@
 # Changelog

-## [Unreleased]
+## [1.91.283.0] - 2026-10-27

 **/benchmark's collection, comparison, budget and trend phases now agree with its vet-the-number section.** The 2026-10-27 flaky pass (GSTA-128) read the `benchmark/SKILL.md perf collection` judge's six samples from run 40558235014: every sample named the same contradictions, so the prose was repaired and no threshold moved.

diff --git a/VERSION b/VERSION
index 269b6e8..0b68a05 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-1.91.282.0
+1.91.283.0
diff --git a/agents-digest/gstack-AGENTS.md b/agents-digest/gstack-AGENTS.md
index 583844b..894898d 100644
--- a/agents-digest/gstack-AGENTS.md
+++ b/agents-digest/gstack-AGENTS.md
@@ -1,4 +1,4 @@
-# gstack digest v1.91.282.0 — regenerate/re-copy after upgrading gstack
+# gstack digest v1.91.283.0 — regenerate/re-copy after upgrading gstack

 Behavioral rules from gstack (https://github.com/garrytan/gstack), compressed
 for agent hosts without a full skill install. The full skills add workflows,
diff --git a/node_modules b/node_modules
new file mode 120000
index 000000000..858ae29
--- /dev/null
+++ b/node_modules
@@ -0,0 +1 @@
+/workspace/gstack/node_modules
\ No newline at end of file
diff --git a/package.json b/package.json
index 66ec462..da0b872 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "gstack",
-  "version": "1.91.282",
+  "version": "1.91.283",
   "description": "Garry's Stack — Claude Code skills + fast headless browser. One repo, one install, entire AI engineering workflow.",
   "license": "MIT",
   "type": "module",
FILES: CHANGELOG.md VERSION agents-digest/gstack-AGENTS.md package.json
MERGE_CONDITION: sha=aa8c07b76935d91ec548fb5a32fd429392f88460
next: NEW_VERSION=1.91.283.0; commit and push only the stamp diff above (FILES), with no edit of your own: the train's verify accepts the CHANGELOG only as the base's plus this PR's entry re-headed; merge with the expected head aa8c07b and recompute on a stale queue.
GSTACK_RESULT: skill=restamp status=complete run=/workspace/gstack/.gstack/tmp/restamp-journal.json

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
@github-actions github-actions Bot changed the title fix(benchmark): reconcile the collection, comparison, budget and trend phases with the vet-the-number section (GSTA-128) v1.91.283.0 fix(benchmark): reconcile the collection, comparison, budget and trend phases with the vet-the-number section (GSTA-128) Oct 27, 2026
@capy-ai
capy-ai Bot merged commit 215c76e into main Oct 27, 2026
63 checks passed
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