Skip to content

chore(release): admit historical 0.15.5 verification evidence - #1122

Draft
blove wants to merge 1 commit into
mainfrom
blove/historical-0155-evidence-admission
Draft

blove wants to merge 1 commit into
mainfrom
blove/historical-0155-evidence-admission

Conversation

@blove

@blove blove commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Draft: the separate code-only fix #1123 merged normally as 547c4ecbf3f7f7bf5662ed78522fbe8f6fe0b522. This proposal preserves the earlier genuine capture, while fresh corrected-main capture, review and service checks remain required before admission. It is not trusted-main or publication authority.

Global release arbitration is blocked when create-b4-app@0.15.5 lacks its keyed publish bundle. This admits the exact historical completion record allowed by the reviewed policy, captured through the normal collector from merged controller 5ce2bfd2baba81b1c5ae28561bebcc2f7cab1fa2 on 2026-10-28 at 16:39–16:41 UTC.

The record authenticates the original successful publisher archive and independent audit. Two fresh sweeps, started 60 seconds apart, establish all 21 exact tarball identities, 20 complete ordinary verifications, and the affected package’s precise provenance-only shape. Both complete GitHub snapshots are retained; only the already approved download-counter differences are normalized for comparison. The original verifier assertion remains distinct from fresh keyed-signature proof.

This PR contains ten byte-identical captured files, ten derived data pins, the pin-file checksum, and three exact existing-schema frozen-evidence brand entries. All 94 existing pins and every other brand entry remain unchanged. Ordinary 0.15.7 verification still requires full proof for all packages.

Validation: independent capture-evidence and admission-scope reviews passed; strict family discovery, binary archive authentication, byte/mode/hash comparisons and twelve independent data-family tests passed. The unchanged brand gate reproduced the three exact failures before the required entries were added and now passes all fifteen tests. Local pnpm ci:validate passed integrity, lint, build-cache, build and typecheck, then failed on six original 5-second timeouts in unchanged Vercel/filesystem tests. Both complete files subsequently passed sequentially at their original limits (133 and 8 tests); all three supplementary suites passed. The failed full-run evidence is retained and no full local pass is claimed. Normal CI, native Vercel, CopilotKit and the immediate fresh premerge service/global checks must pass before merge.

Record SHA-256: 33e0c76cb15a5ddebe5da958d0b31d8b8630fa64fa30b0a015a6fa53b84b8857.

@vercel

vercel Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated
b4-run Ignored Ignored Oct 28, 2026 4:51pm UTC
navlog-web Ignored Ignored Preview Oct 28, 2026 4:51pm UTC

Request Review

@github-actions github-actions Bot 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.

Automated approval for repository bookkeeping. The maintainer reviews and merges this PR.

@blove
blove deployed to vercel-preview October 28, 2026 16:51 — with GitHub Actions Active
@blove
blove marked this pull request as draft October 28, 2026 17:05

This branch was successfully deployed

1 active deployment
vercel-preview — 6471ee6c Deployed Oct 28, 2026 by blove via vercel-native #3266
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.

1 participant