Repository navigation
Expose byte-compatible package artifact verification - #52
Merged
Merged
Conversation
Preserve the existing ordered tuple hash and trusted key aliases. Keep bootstrap and directive signing domains separate.
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.
Summary
Extract the existing reusable package-artifact tuple verifier into public compute-core protocol. Preserve exact ordered JSON/hash bytes, optional plugin ID, explicitly trusted key aliases and signature encoding. Bootstrap raw-JSON and legacy directive signatures remain separate domains.
Scope Manifest
Approved recovery ADR 0152: 25 tasks / 14 PRs, original outcomes retained.
This PR is only Task 24 / PR 13, branch
feat/public-package-artifact-verifier-20261003.Design/plan: GoCodeAlone/workspace
docs/plans/2026-10-02-workflow-compute-recovery-design.mdanddocs/plans/2026-10-02-workflow-compute-recovery-0a.md.Four files only: new public payload/verifier and external-package tests, shared vector consumer and append-only golden vector additions. No installer, provider, private app policy, key generation or signing fallback.
Verification
GOWORK=off go test ./... -race -count=1: 4 packages, 444 test events, zero failures/skips, including a separate Go-module caller of the real public API.git diff --checkclean.Runtime Launch Transcript
The first plain developer build correctly failed wfctl's dev-sentinel gate; explicit local candidate metadata then passed. This is supporting native launch evidence, not a stable release. Failure-signature scrape of the final launch is clean. Exact stable assets/public module/consumer proof and original installer/launcher adoption remain subsequent plan gates.
Rollback
Additive API; consumers remain pinned to prior core until the immutable successor and real consumers are verified. No deployment, enrollment, cloud mutation or root change.