Repository navigation
Bind legacy approvals to authoritative control revisions - #6
Merged
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
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.
The shipped templates pause at legacy approval gates, but external controllers cannot inspect an authoritative revision or bind a legacy decision to it.
inspect --jsonnow includes a bounded control view from the canonical state loader, and legacyresume-decisionaccepts an optional positiveexpected_state_revisionchecked under the run lock before claiming work.New legacy receipts retain the exact parsed-payload digest. An identical applied decision returns
already_appliedeven after a second gate opens; changed payloads conflict, and claimed/failed or unverifiable historical receipts fail closed for revision-bound callers. Calls without the new field retain historical receipt compatibility. Inspection is observational and does not authenticate actors or authorize execution.Validation adds UTF-8 size-limit tests and CLI checks for filesystem/SQLite authority, stale and invalid revisions, v2 boundary projection, duplicate/conflicting delivery, uncertain receipts, historical compatibility, second-gate isolation, and completion of all three shipped offline templates without blanket auto-approval. The four control-view tests, complete revision-bound CLI suite (including all three templates), and existing resume-policy suite pass locally on Kujo 1.8.1. Full pinned Kujo 1.6.0 Linux/macOS CI results are pending. The local broad gate was stopped after partial checks because it used different companion revisions and competed with plugin verification; no local full-gate pass is claimed. no release or downstream plugin exposure is included.