Repository navigation
Bind Dispatch workflow approvals to authoritative control state - #70
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.
Dispatch’s shipped workflows pause at legacy approvals. The internal Paperclip adapter now reads the canonical authoritative control view and constructs an exact revision/event/step/decision-bound approval or rejection with host-derived actor metadata. Failed or foreign inspections, unavailable/oversized evidence, terminal states and unsupported request contracts are rejected.
An explicit internal workflow-job budget allows fixed 120-second workflow effects and is included in the policy digest. The default, read-only commands and existing public execution plans remain capped at 27 seconds. This materializer does not provide production job admission or human authentication and does not register a public workflow tool. All thirteen other component snapshots remain unchanged.
All 13 checks passed at 08cf16a. The complete local
npm run verifysubsequently passed (37 files, 284 passes, two expected skips). The final commit changes only the Dispatch commit pin and its documentation; all source/checksum bytes and the other 13 component records are identical. Component/build/package checks and a fresh extracted-tarball smoke passed after repinning. All 13 gates must pass again on final head 850480e before merge. Native tests cover all three templates through pause, authoritative inspection, approval and completion; stale/duplicate/conflicting legacy decisions; existing v2 second-boundary behavior; import isolation; and explicit budget separation. Extracted-package smoke verifies the 107-file snapshot, approval completion and duplicate acknowledgement outside the canonical checkout.Upstream kujolang/dispatch#6 passed Linux/macOS release and clean-install gates and merged at 4c4d34b2979f6754a97a48d1da62e28fda14315d. The bundle is now pinned to that reviewed merge. Require all 13 checks and the unresolved-review audit on the final downstream head. No registry release or public workflow admission is included.