[IanHollow]

Summary

Expose verified package source-PR validation results to GitHub’s protected merge gate. Explicitly dispatched bot jobs exist in the Actions API but are absent from the PR rollup, preventing unattended source updates from entering the normal queue.

The shared reconciler gains an opt-in workflow-to-required-job map. It proves exact bot/repository/branch identity, actual parent ancestry, selected package/catalog ownership, and current protected workflow blobs before reporting real job outcomes. Genuine failures link their actual failed jobs; missing, running, skipped, stale, or untrusted evidence never becomes success. Existing synthetic queue reporting is unchanged.

Evidence

The live Claude source PR has successful native validation and an actual DCO failure omitted from its PR rollup. The new adapter rejects its stale workflow contract and identifies the exact failed DCO job without mutating the repository.

All 133 repository regressions and offline workflow/security validators pass, including 73 queue/source cases. Fixtures cover immutable identity and scope proofs, approval runs with zero jobs, real failure URLs, producer reruns during collection/publication, API errors, idempotence, and request budgets. Six idle source PRs require 103 reads and no writes; admitted-head scans require 12 reads; exact-head events inspect only the relevant source. Native Nix and representative caller checks are required before merge.

Merge danger

This changes privileged admission/reporting only for callers that explicitly enable package source checks. The representative caller must provide all protected job names and requested/in-progress notifications; it then regenerates bot branches from reviewed protected main. Normal expected-head admission and full merge-group validation still apply. No additional token permissions or caller-code execution are introduced. Rollback restores the previous shared commit and disables the source opt-in.

Closes #79.