Make Boatstack inert outside active delivery - #182
Merged
Conversation
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.
Summary
Boatstack previously treated repository presence as enough authority for ambient safety and workflow behavior. That made ordinary repository administration observable—and sometimes blockable—even when no delivery was active.
This rewrite introduces one engagement boundary shared by commands, hooks, and host adapters:
DORMANTapplies no Boatstack policy and emits no output.COMMANDgrants temporary authority only for an explicitly invoked Boatstack operation.ACTIVEis backed by a verified worktree-, branch-, feature-, slice-, and plan-lock-bound lease.Activation creates the durable lease transactionally, allowing genuine pre-publication deliveries to survive host restarts. Verified PR publication releases it. Generated Cursor, Claude, Codex, and Gemini hooks now use inert lease probes, and stale ambient contracts and path-authority exemptions have been removed. An event-completeness registry prevents future entry points from bypassing the resolver.
Cross-platform CI also exposed a shared-runtime publication race: helper and manifest paths could become visible before the hydrate writer released its lock. POSIX and PowerShell launchers and guards now treat lock release as the publication point, with deterministic regressions for ready-looking incomplete manifests.
Test Plan
cd boatstack && go test ./... -count=1cd boatstack && go vet ./...python3 -m unittest discover -s .github/tests -p "test_*.py"python3 .github/scripts/release_notes.py validate --repo .