Bind the Chat 366 producer authority - #315
Merged
Merged
Conversation
Chat #365 made the report check prefer a recorded handshake stage over the identifier derived from the assertion name, and #366 repinned the harness authority to that merge. The repin landed as a single commit, so the reviewed head has the harness authority as its sole parent again and sourceAuthorityPath returns to empty. The test helper, the two symmetry refusals and the binding prose return with it to the forms they had before the intermediate was needed. Producer, reviewed head, harness authority, the workflow digest and the Windows and Unix step digests move, with the three reviewed constants that recompute them. Every identifier in the binding was read back from the Chat repository and resolves to a Git object of the expected type. Scope rotation and a fresh protected run remain required. This binding alone is not acceptance. Refs OpenCoven/chat#219 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
The binding rotation and regenerated evidence require final human verification.
Review effort: Lite
Findings: None
What changed in this PR
This pull request rebinds frozen conformance evidence to Chat #366, updating authority identities, workflow digests, fixtures, tests, and documentation.
Changes:
- Rotates producer, source, harness, and workflow bindings.
- Removes the obsolete intermediate authority path.
- Refreshes conformance expectations and documentation.
| File | Summary |
|---|---|
tests/conformance-gaps.spec.ts |
Updates producer and workflow assertions. |
tests/conformance-contract.spec.ts |
Updates ancestry and fixture expectations. |
scripts/github-conformance-evidence.mjs |
Updates reviewed script digests. |
RELEASING.md |
Updates release evidence documentation. |
README.md |
Documents the new binding. |
docs/workflows/client-v1-cross-repository-conformance.md |
Updates conformance workflow documentation. |
docs/ROADMAP.md |
Updates checkpoint and remaining work. |
conformance/client-v1-cross-repository-lock.json |
Updates frozen authority metadata. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Chat #365 made the report check prefer a recorded handshake stage over the identifier derived from the assertion name, and Chat #366 repinned the harness authority to that merge.
The binding
evidenceProducer.commitd37c2058deee56baevidenceProducer.treed02d9b832068184fevidenceProducer.source.commitb666ec03b491b8abevidenceProducer.harnessAuthority.commite969c88897803d0aevidenceProducer.harnessAuthority.treefe44ee9023edb811workflow.sha2563bf4a605…c33edc48…workflow.windowsBootstrapScriptSha2567ab1016e…9a498d8c…workflow.unixSupervisorPreparationScriptSha2568250b401…77a7601e…Every identifier above was read back from the Chat repository and resolves to a Git object of the expected type. I also re-read every path, size and digest triple in the lock from Chat
deee56ba; the only one that differs issources.chat.consumerLock, which binds the frozen consumer and is meant to.sourceAuthorityPath returns to empty
Chat #366 was deliberately a single commit, so its reviewed head has the harness authority as its sole parent again.
sourceAuthorityPathgoes back to[], and with it the test helper, the two symmetry refusals that had to accept either message while the two bindings named different numbers of intermediates, and the binding prose. ThecurrentAuthority0fixture role stays, carried forward unchanged like the other historical roles.Fixtures
tests/fixtures/chat280-cave5ee-source.json.bris regenerated for theproducer,reviewedandharnessroles; the other twenty are carried forward. Object count goes from 222 to 230. The three derived workflow fixtures are regenerated from the new producer.Verification
pnpm verifypasses.Scope rotation and a fresh protected run remain required. This binding alone is not acceptance.
🤖 Generated with Claude Code