Skip to content

fix(conformance): bind Chat token-profile alignment - #228

Merged
BunsDev merged 1 commit into
mainfrom
fix/chat249-token-profile-validator
Sep 12, 2026
Merged

fix(conformance): bind Chat token-profile alignment#228
BunsDev merged 1 commit into
mainfrom
fix/chat249-token-profile-validator

Conversation

@BunsDev

@BunsDev BunsDev commented Sep 12, 2026

Copy link
Copy Markdown
Member

Summary

  • bind the cross-repository validator to merged fix(conformance): align Windows native token profile chat#249 at 4682a4aa758c8d958f8b87b9976addf14856f76b
  • refresh exact workflow, harness, Windows bootstrap, nested child bootstrap, and Unix preparation digests
  • regenerate deterministic Brotli fixtures directly from the merged Chat workflow
  • document the supervisor-owned token-profile binding, separated USERPROFILE, bounded cleanup, and platform-aware launch budgets

Validation

  • full pnpm verify passed
  • focused conformance contract suite: 124 passed, 1 skipped
  • all regenerated fixtures match the exact merged Chat source bytes and parsed workflow step bodies
  • independent code review found no significant issues

Chat pre-merge CI run 34724946685 passed all ten checks, including Windows supervisor behavior and real-authority conformance. Protected cross-repository evidence remains pending until this validator merges and both protected validator variables are rotated.

Rebind the cross-repository validator and deterministic workflow fixtures to merged Chat #249, including the token-profile and platform-aware launch contracts.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings September 12, 2026 23:51

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.

🟡 Changes recommended

Documentation should qualify token-profile alignment as intended or unverified until protected validation proves the lifecycle.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This pull request rebinds SDK cross-repository conformance to merged Chat #249 and refreshes related digests, fixtures, tests, and documentation.

Changes:

  • Updates producer, workflow, harness, bootstrap, and platform digest pins.
  • Refreshes conformance expectations and lock metadata.
  • Documents token-profile handling, cleanup, and launch budgets.
File summaries
File Description
tests/conformance-gaps.spec.ts Updates producer and fixture digest expectations.
tests/conformance-contract.spec.ts Updates workflow authority assertions.
scripts/github-conformance-evidence.mjs Updates reviewed source pins.
RELEASING.md Updates release and validation notes.
docs/workflows/client-v1-cross-repository-conformance.md Documents the new conformance binding.
conformance/client-v1-cross-repository-lock.json Rebinds the frozen Chat producer.
Review details
  • Files reviewed: 6/9 changed files
  • Comments generated: 2
  • Review effort level: Lite

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

Comment thread RELEASING.md
Comment on lines +229 to +234
The trusted supervisor overwrites the dedicated Windows profile-root binding
with the operating-system profile registered for the restricted process token.
The producer validates it independently from the bootstrap-local `USERPROFILE`
redirect and publishes only the native fixture beneath that profile's
`.coven/cave`, matching Rust token-profile discovery. A forged caller value
cannot redirect publication. Fixture deletion follows confirmed RPC closure;
Comment on lines +43 to +48
The trusted supervisor overwrites the dedicated Windows profile-root binding
with the operating-system profile registered for the restricted process token.
The producer validates it independently from the bootstrap-local `USERPROFILE`
redirect and publishes only the native fixture beneath that profile's
`.coven/cave`, matching Rust token-profile discovery. A forged caller value
cannot redirect publication. Fixture deletion follows confirmed RPC closure;
@BunsDev
BunsDev merged commit c863b58 into main Sep 12, 2026
9 checks passed
@BunsDev
BunsDev deleted the fix/chat249-token-profile-validator branch September 12, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants