release: v0.36.1 — widen bareguard peer range to admit 0.13.x - #31
Merged
Conversation
bareguard 0.13.0 shipped a gate.annotate() behavior change (a malformed fact is now rejected into an annotate_malformed audit row instead of silently honored; surface must be an explicit boolean). judgeToAnnotation is already compliant by construction — single object literal, surface: v.verdict !== 'honored' (explicit boolean), meta of String()-coerced scalars (JSON-safe, no __proto__ key) — so no bare-agent code change is needed; this is a manifest range bump only (>=0.9.0 <0.13.0 -> >=0.9.0 <0.14.0 in peerDependencies + devDependencies). Validated against bareguard 0.13.0: typecheck + build:types clean; the bareguard-touching tests (shell-tools + both integration-bareguard suites) pass 84/84; the one full-suite miss was a pre-existing load-induced timing flake in spawn.test.js (idle-watchdog vs child cold-start), reproduced 0/3 in isolation and structurally unaffected by a devDep bump. Closes the #30 coordination item. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gnmz6puuaZrv4NmSr1FpfT
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v0.36.1 — admit bareguard 0.13.x (manifest bump, no code change)
Closes the conditional coordination item tracked in #30 (bareguard 0.13.0 is now live on npm).
What & why
bareguard 0.13.0 changed
gate.annotate()— a malformed fact (non-object, array, missingsurface, or one that throws when read) is now rejected into a distinctannotate_malformedaudit row instead of normalized into a silently-honored one;surfacemust be an explicit boolean.judgeToAnnotationis already compliant by construction (verified at source, not on the maintainer's word):surface: v.verdict !== 'honored'→ always an explicit boolean;metaisString()-coerced scalars → JSON-safe (immune to 0.13.0's meta JSON-round-trip copy) and has no__proto__key (immune to__proto__stripping).So this is a manifest range bump only:
>=0.9.0 <0.13.0→>=0.9.0 <0.14.0in bothpeerDependenciesanddevDependencies(conservative<0.14.0ceiling — each future bareguard minor is re-verified before admission).Validation against bareguard 0.13.0
typecheck+build:typesexit 0.shell-tools+ bothintegration-bareguardsuites): 84/84 pass.spawn.test.js(idle-watchdog vs child cold-start under concurrent-suite load) — reproduced 0/3 in isolation, andspawndoes not import bareguard so a devDep bump cannot affect it.No test change needed
Our tests exercise the pure
judgeToAnnotationrender (which already assertssurfaceis an explicit boolean); nothing calls the realgate.annotate, so 0.13.0's changedannotatesemantics touch no test here.🤖 Generated with Claude Code
https://claude.ai/code/session_01Gnmz6puuaZrv4NmSr1FpfT