Skip to content

Repin the harness authority to the preferred stage diagnostic - #366

Merged
BunsDev merged 1 commit into
mainfrom
chore/219-authority-repin-365
Sep 22, 2026
Merged

BunsDev merged 1 commit into
mainfrom
chore/219-authority-repin-365

Conversation

@BunsDev

@BunsDev BunsDev commented Sep 22, 2026

Copy link
Copy Markdown
Member

Follow-up to #365, which merged as 97803d0a.

Per the two-PR rule, that content PR left the lock alone. This one only moves the pin: harness.revision, harnessAuthority.revision and harnessAuthority.tree now select the merge commit, and two governed entries move to their new bytes.

Governed file blob sha256
scripts/phase1-schema-v2-producer.mjs 40ab6faf → 7990dcc7 6b2f58e2… → 21f6a3aa…
.github/workflows/client-v1-conformance.yml e4fcc078 → ce6ab14e 3bf4a605… → c33edc48…

All 25 governed files and ten production deltas were re-read from the merge commit; no other entry moved, and the literal authority fixture already lists both paths.

This PR is deliberately one commit. The previous repin needed a second commit after review, which left its reviewed head reaching the harness authority through an intermediate and obliged SDK #314 to bind that intermediate in sourceAuthorityPath. A single commit keeps the sole-parent shape.

Verification

  • pnpm lint, pnpm typecheck
  • vitest run — 1108 passed, 61 skipped
  • vitest run --config vitest.heavy.config.ts — 914 passed, 35 skipped

SDK rebinding, both scope rotations and a fresh protected run remain required. This binding alone is not acceptance.

🤖 Generated with Claude Code

Copilot AI lite review requested due to automatic review settings September 22, 2026 20:44
@BunsDev BunsDev added the ci:full Run the macOS and Windows CI jobs on this pull request label Sep 22, 2026
#365 landed as a merge commit, so the governed bytes for the producer and
the protected workflow now differ from the revision the lock selects.
Point the harness authority at that merge and refresh the two moved
entries, per the two-PR rule.

Kept to one commit so the reviewed head has the harness authority as its
sole parent, which spares the SDK binding an intermediate authority-path
entry.

SDK rebinding, both scope rotations and a fresh protected run remain
required. This binding alone is not acceptance.

Refs #219

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@BunsDev
BunsDev force-pushed the chore/219-authority-repin-365 branch from 5df3d17 to b491b8a Compare September 22, 2026 20:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🔵 Needs a closer look

Authority rebinding and protected-run validation still require final human review.

Review effort: Lite
Findings: None

What changed in this PR

Repins the Phase 1 conformance harness to merge commit 97803d0a and synchronizes integrity pins, tests, and documentation.

Changes:

  • Updates harness authority revision and tree.
  • Refreshes governed file digests.
  • Synchronizes lock expectations and documentation.
File Description
src/​phase1-conformance-lock.test.ts Updates expected authority values.
phase1-conformance.lock.json Stores the new revision, tree, and file digests.
docs/​phase1-conformance.md Documents the new source snapshot.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@BunsDev
BunsDev merged commit deee56b into main Sep 22, 2026
11 checks passed
@BunsDev
BunsDev deleted the chore/219-authority-repin-365 branch September 22, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:full Run the macOS and Windows CI jobs on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants