feat: accept Curator Protocol v1.0.0-rc.10 - #47
Merged
Conversation
Advance the accepted protocol revision from 1.0.0-rc.5 to 1.0.0-rc.10 (curator-spec b8b03d5, the merge of the pinned-agent authentication tail the manager already emits). Conformance assertions now match the rc.10 corpus; the manifest digest moves to 803918bf. The audited-hash ledger records the test change. The external-build-repositories header now states the rc.10 schema-8 boundary with the new revision and digest, the body pairs schema-7 with marker v3 and schema-8 with marker v4, and the pinned-agent form cites the spec as its source: the third canonical authentication tail, RECOMMENDED. The skill-authoring link follows the accepted core to v1.0.0-rc.10.
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.
What
The full chain requested by the owner, delivered in one PR (board story docs-build-https, tasks accept-protocol-rc10 and spec22-pin-delta):
b8b03d5and taggedv1.0.0-rc.10. The conformance corpus does not encode the tail, so the manifest digest is unchanged from rc.9.PROTOCOL_VERSIONmoves to1.0.0-rc.10,CONFORMANCE_MANIFEST_SHA256to803918bf...; every conformance assertion aligned with the actual rc.10 corpus (no fail-closed check weakened); the audited-hash ledger records the test change.cskalready emitted spec form 3 byte-for-byte, so no behavior changes.Review evidence
Producer and reviewer runs on the board (claude-opus-5 reviewers re-derived the revision hex, tag, and manifest digest from fresh clones twice, and verified spec form 3 against
git_admission.pybyte-for-byte). Full suite on this tree: 1797 passed, 245 skipped. The reviewers' stop-the-line on the empty Change-Request plane is a board workspace-mapping defect tracked as BUG-260827-2kr92i, unrelated to this diff.