CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-07-05 23:57:53 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore: bump version and changelog (v1.53.1.0)

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-05-30 11:32:33 -07:00
parent 7396f04847
commit 721d0c8514
4 changed files with 43 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODOS.md
+14 -19
View File
@@ -2,27 +2,22 @@
## Test infrastructure
### P0: Rebaseline parity-suite (v1.44.1) — stale, 5 pre-existing failures
### ✅ DONE (v1.53.1.0): Rebaseline parity-suite (v1.44.1 → v1.53.0.0)
**What:** `test/parity-suite.test.ts` checks every skill's SKILL.md size against
the frozen `test/fixtures/parity-baseline-v1.44.1.json`. Five planning skills now
exceed the 1.05x ceiling: `plan-ceo-review` (1.052), `plan-eng-review` (1.062),
`plan-design-review` (1.068), `investigate` (1.053), `office-hours` (1.065).
**What:** `test/parity-suite.test.ts` checked every skill's SKILL.md size against
the frozen `test/fixtures/parity-baseline-v1.44.1.json`. Five planning skills had
crept past the 1.05x ceiling: `plan-ceo-review` (1.052), `plan-eng-review` (1.062),
`plan-design-review` (1.068), `investigate` (1.053), `office-hours` (1.065) — growth
from the brain-aware-planning releases (v1.49–v1.52) plus the v1.53 redaction guard.
**Why:** These grew during the brain-aware-planning releases (v1.49–v1.52) which
added the `BRAIN_PREFLIGHT`/`BRAIN_CACHE_REFRESH`/`BRAIN_WRITE_BACK` resolvers to
those skills. The v1.44.1 baseline was never regenerated, so it's four releases
stale. The failures are pre-existing on `origin/main` (proven: they fail with the
redaction branch absent). The active size gate (`skill-size-budget`, v1.47 baseline)
passes, and parity-suite is not in CI's `test:gate`, so nothing is blocked — but the
local `bun test` shows red until rebaselined.
**How to start:** Either regenerate the fixture to a current baseline
(`bun run scripts/capture-baseline.ts <tag>` and point the test at it), or bump the
per-skill ratio for the planning skills. Decide whether v1.44.1 should be retired in
favor of the v1.47 baseline the size-budget test already uses.
**Depends on:** nothing. Standalone.
**Resolved:** Captured a fresh baseline at HEAD via
`bun run scripts/capture-baseline.ts --tag v1.53.0.0` and re-pointed the test at
`test/fixtures/parity-baseline-v1.53.0.0.json`. The per-skill 1.05 ratio is kept, so
future bloat is still caught — only the stale anchor moved. Mirrors the earlier
`skill-size-budget` rebase (v1.44.1 → v1.47.0.0). Historical v1.44.1 / v1.46.0.0 /
v1.47.0.0 baselines retained in `test/fixtures/` for the v1→v2 audit trail. The
captured skill bytes match `origin/main` exactly (the rebasing branch left every
SKILL.md untouched). `bun test` is green again.
## gbrowser memory follow-ups (filed via /plan-eng-review + /codex on the v1.49 leak-fix PR)