Skip to content

docs(g01): reconcile post-merge canary evidence #165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jjangg96 merged 1 commit into from
Nov 3, 2026
Merged

docs(g01): reconcile post-merge canary evidence #165

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/evidence/g01-live-canary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -951,3 +951,10 @@ Verification used Go `1.27.3`, with build/module caches and temporary files on t
| `gofmt` and `git diff --check` | PASS |

These checks use synthetic HTTP/subprocess fixtures only. They do not prove live GitHub status freshness or atomicity: a run may change after the final GET and during child execution, and the API supplies no conditional handoff primitive. An accepted management-token POST whose response is lost cannot be self-revoked without a token value; uncertain DELETE or ledger confirmation likewise retains a pending barrier. Server-side conditional Scale Set deletion, production workflow provenance/trust-root custody, broker-only execution, runtime/isolation/resource qualification, current canary repository protection and the separately authorized Linux ARM64/JIT run remain open. No live provider write, credential request, runner, Scale Set, Docker or host operation occurred. Issue #1 remains OPEN and Project #2 remains In progress.

### Post-merge evidence reconciliation — 2026-11-04

- PR #163 and PR #164 are merged. PR #164 merged as `853d176766db50c55bbf84575c429ed4924db835`; Public CI run [41720512574](https://github.com/1XP-AI/gh-runnerd/actions/runs/41720512574) completed successfully on that exact main SHA.
- The selected path remains Go `1.27.3`, `github.com/actions/scaleset v0.5.0`, the high-level listener and independent reconciliation. The current upstream latest release remains [v0.5.0](https://github.com/actions/scaleset/releases/tag/v0.5.0).
- Independent review rejected removing `github.ref_protected`: pinning the reusable callee does not bind or authorize the mutable caller. The guard remains. Private branch protection is unavailable under the current repository plan; no workflow or repository policy was changed. See the [caller-protection review record](https://github.com/1XP-AI/gh-runnerd/issues/1#issuecomment-6616630311).
- The live canary remains unrun. Issue #1 remains OPEN and Project #2 remains In progress. Outstanding gates include a supported caller-protection path, production provenance and trust-root authority, broker-only execution, conditional Scale Set cleanup, trusted runtime/isolation/resource qualification, and separate concrete authorization plus evidence for the Linux ARM64/JIT canary. No live provider, credential, runner, Scale Set, Docker or host operation was performed for this update.