Repository navigation
chore: release Grok as a parent harness as 1.21.0 - #289
Conversation
Refs #281 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Live evidence: Open Pstack
|
Merge Protections🟢 All 2 merge protections satisfied — ready to merge. Show 2 satisfied protections🟢 Queue ready pull requestsAutomatically queue non-draft pull requests targeting main after verify and live-gate pass on the head and every review thread is resolved.
🟢 🚦 Auto-queueWhen all merge protections are satisfied and these conditions match, this pull request will be queued automatically.
|
✅ Merged into
|
✅ No blocking findingsWalkthroughThis cuts the
Details
First review of this pull request. @unfret review · @unfret status · @unfret help |
Summary
This releases Open Pstack 1.21.0: Grok becomes a parent harness (#281, through #284, #286 and #288).
UPSTREAM, README and the reference carry the new version. The reference's intro now says four harnesses. CHANGES adds a "Grok in the live gate" entry covering the verifier's new harness and the two fix-forwards.
Evidence
python3 scripts/release.py notesprints the 1.21.0 section from this head.bun run staticpasses, including "version matches across UPSTREAM.md and the 4 manifests (1.21.0)".Merge Danger
Door: two-way
Blast Radius: version-only
No runtime file changes besides the version strings.
Gate results (head c0de350)
bun run testbun run typecheckbun run staticclaude plugin validate plugins/pstackgrok plugin validate plugins/pstackNot verified
live-gateis pending:claude:hook:startupandcodex:hook:startup, run from trustedmain, for the version-only manifest bumps. The Grok manifest's bump has no Grok-observable behaviour beyond its version string.grok plugin validatereads 1.21.0.🤖 Generated with Claude Code