ci: build exact v30.1.5 canary candidate - #51
Draft
Blackcoin-Dev wants to merge 16 commits into
Draft
Conversation
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.
Purpose
This draft provides a fail-closed v30.1.5 candidate pipeline and a separately gated OCI publication/handoff path. Neither path can build, publish, or deploy until the final signed Core source and its exact successful safety-gate evidence are atomically pinned.
Signed stages on this branch
bad55a3a321d33ac5294cfcbc230b9ae7e5b1594— identity-generic candidate adapter.f2ef7c4e0490ba098de125a5754a78c8f2ed8032— initial OCI publication adapter (superseded history).50a1b1a4c4484fd2d8ed6d601a82105f7ed243b2— exact Core-CI/check-run/zero-report TSan receipt.db8812b603744fee7615979f87899b4dd48b154d— live-main protection binding: exact 16 contexts and Actions app ID15368.6c34b97122b46505b8360841be5014ba06b61f1a— exact integer-type closure for Core receipt schemas and GitHub IDs.97ae128d0a7b3924474c487556d6c37813c3fcff— schema-2 publication intent, sealed OCI-manifest equality, and digest-preserving registry copy (superseded by schema 3).f539049beaa98d4d1a2cfb2b94e40eb56669d533— repository-required executable modes for the Core receipt tools.f6042df3cf14c9c3f2a53d341affc070c96303f1— schema-3 complete publication authority and hardened live wrapper.f0b93f583f7bc4e81c1236d4bcba9977cf71b204— portable Bash entrypoint and resealed publication package.1419cf02c6c007bd06abb1e176c25f2da7873589— blocked/ready publication-fixture isolation for the eventual checked-in authorization transition.Every stage is signed by Blackcoin-Dev with ED25519 fingerprint
SHA256:jAkpBudDw+ntWHSUx3e1KY+czAFjnlaPxQtRFtptL70and pushed before the next stage. The Core-CI receipt stage has completed independent hostile review with no remaining P0/P1/P2 defect. The exact schema-3 publication head is undergoing an independent read-only hostile audit; no live publication is authorized from this draft.Current authority state
The checked-in policy remains deliberately blocked:
{ "state": "blocked_pending_final_signed_source_and_green_ci", "dispatch_enabled": false, "temporary_source_pin": true, "core_ci_run_id": null, "core_ci_run_attempt": null, "thread_sanitizer_artifact": null }The workflow sentinel remains
EXPECTED_CORE_CI_RUN_ID: 0. Build, assembly, OCI import, registry publication, and fleet deployment are impossible from this state.Implemented gates
pull_requestrun, current strict-main freshness, open/non-draft/clean PR, and exact live protected-context set;15368;curl --disable, compressed ZIP cap, stopped-container host-side executable hashing, and no candidate execution;skopeo copy --preserve-digests, exact source/remote manifest bytes, same-response digest verification, digest-refetch equality, and fail-closed ambiguous-copy handling; andqqblackcoin/blackcoin-v4-gui@sha256:<manifest>.Validation at current head
git diff --check: pass.Remaining stages
The exact Core candidate remains
0e62ec0af3daefba30f87382d9b3cc8b00224e62, treed460eee11b7c8c6d5fffe6935f2e9a5d58e18aac, run31710198720, attempt1. Its TSan job is green with a verified zero-report artifact, but the overall run remains 15/16 while ASan/UBSan is still running. Only after that last protected job succeeds and the publication audit is green may a later signed commit atomically pin H/T, terminal run/attempt, exact TSan artifact, and the distinct base/source workflow digests and enable dispatch. This draft authorizes no build, registry push, canary, or fleet deployment.