feat(operations): restack runner-assignment audit on current main

[seonghobae]

Purpose

Create a clean protected-main successor for stale/diverged Draft #94 without rebasing or force-pushing its history. This successor starts directly from protected main 11a0bb0c50bda5edaef944b1c1e4102bc2739363 and preserves the runner-assignment source/tests/operator slice without replaying stale protected-main documentation state.

Exact source / ancestry

• protected-base parent: 11a0bb0c50bda5edaef944b1c1e4102bc2739363;
• current successor head: 05dcac4d390810c474a3c45014b1b34e5be999a0;
• source predecessor: PR feat(operations): restack runner-assignment audit on deterministic toolchain #94 exact head f33930dcbd800ba1018a82de0151b7579d4d1b74;
• predecessor ancestry had diverged from current main: merge base ebde3720ee27292be0ce3315986e0438dd66af9f, 16 commits ahead / 175 behind;
• the final current-main delta is 9 files, 1,146 additions, 0 deletions: the runner-assignment doctoring file, three implementation/source files, four regression suites, and the single additive package.json command;
• every other path, including protected-main CHANGELOG.md, is inherited from live main unchanged.

Restack RCA

The first direct-blob staging commit (9e89577aad44772539dee41eb426bdfbe5abbb27) deliberately exposed a stale-lineage hazard instead of hiding it: copying #94's historical CHANGELOG.md would have downgraded the protected-main package-manager contract from schema v3 back to schema v2. Exact live-base comparison showed 2 changelog additions / 1 deletion, including loss of the v3 package-set and metadata-digest controls. The follow-up fast-forward correction restored protected-main changelog blob c0d116d584b82de42ed03328649d8b01b8c27651. Final exact comparison from live main to 05dcac4d390810c474a3c45014b1b34e5be999a0 is ahead-only with zero deletions. No force push or destructive rebase was used.

Implemented evidence boundary

The operator remains read-only and exact-source-head/workflow-run-ID bound. Fully paginated filter=all job evidence separates runner assignment from later workflow/test conclusions and from dependency/environment-protection waiting. Fresh unassigned queues are non-passing, bounded-grace expiry fails closed, and an assigned runner followed by workflow failure does not convert the workflow failure into success.

The gh subprocess receives only bounded PATH, explicit read-only GH_TOKEN, pinned GH_HOST=github.com, and NO_COLOR=1; ambient GITHUB_TOKEN, model credentials, App private material, proxy variables, HOME, and unrelated process state do not cross the diagnostic subprocess boundary. Reports carry no required-check, formal-review, merge, release, deployment, production, KPI, licensing, IP, or acquisition authority.

Evidence transfer

No predecessor CI, reviewer, scanner, model, operational, or production evidence transfers from #94 or from the superseded staging head. This Draft must obtain fresh exact-head application CI, reviewer CI, and protected-base-eligible central Security Scan evidence against unchanged head 05dcac4d390810c474a3c45014b1b34e5be999a0 and the live protected base. Pending, skipped, absent, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Before any merge, independently resolve live base/head again, re-read the live organization ruleset and central .github Security Scan authority, require zero valid unresolved findings, verify exact checkout SHA evidence, and exercise the read-only operator from protected source against realistic assignment/wait/failure cases. No independent approval requirement is invented if live policy does not require it.

Supersedes #94 only after fresh exact-head validation establishes the current-main successor as technically sound.

Related: #27, #30, #77, #79, #88, #91, #94

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9d14c2e3-b410-483c-bafe-191a64ac3fae

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}