Repository navigation
fix: a workload credential carries no build seal (core #812) - #71
Merged
antoinetoussaint-byte merged 2 commits intoOct 18, 2026
Merged
Conversation
…ests follow Moves to the host-aligned sdk-go 70dc7a54 / core b81d92e6. Since core's signed module manifest the host binds the execution at mint (the projected token and the pod it names, held to the approved build) and seals none, so the runtime's 'seals no execution' refusal rejected every valid credential: on a host running it, every viewer call a solution makes (collection, search, chat, traces) failed. The sealed identity is the installation alone; the scoped credential's build-consistency check goes with the seal. Test fixtures still reference the removed seal fields and are updated in the next commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Core b81d92e6 seals no build and mints from no Execution input, so the tests that proved the build half of the seal now describe a shape core cannot mint: the execution-free refusal test, the build-changed renewal test and table rows are removed; the broker renewal table and the per-field comparison keep the installation case; the conformance floor follows core's 35 fixtures (the five build-seal ones are gone); the typed-decode fixture spells an accessor core still has. go test ./... green. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
antoinetoussaint-byte
deleted the
fix/workload-credential-carries-no-build-seal
branch
October 25, 2026 17:04
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.
What broke
Against a host running the signed-module-manifest protocol (core #812, where the host binds the execution at every mint and seals no build),
usableCredentialrefused every workload credential:the credential this process holds seals no execution (image digest "", build incarnation 0). Every viewer call a solution makes — collection, search, chat, traces — failed (this solution cannot currently act for the viewer). Verified live on a hosted cell; dev-deployed from this branch it works.Fix
usableCredential: the execution-seal check is deleted (the protocol no longer carries the fields).sealedIdentity: the installation alone; a renewal to another installation is still refused by name.go test ./...green. Independent review pending. Classification: fix (a consumer the protocol change missed).🤖 Generated with Claude Code