[Fleet incident] Disable orphaned PR rebuild and repair workflow identities

[seonghobae]

Live Actions registry drift

The repository's GitHub Actions API currently reports 19 workflow identities. Many historical bootstrap, PR rebuild, and PR-specific repair records remain in state: active, including examples such as:

• bootstrap-speaker-reconciliation.yml;
• pr246-apply-review-fixes.yml;
• rebuild-pr-317.yml and rebuild-pr-317-clean.yml;
• rebuild-pr-318.yml, rebuild-pr-331.yml, rebuild-pr-339.yml, and rebuild-pr-346.yml;
• repair-pr-345.yml;
• repair-pr-353.yml and v2;
• repair-pr-361.yml.

Fresh protected-main contents lookup returns 404 Not Found for sampled active path .github/workflows/rebuild-pr-317-clean.yml. The source file is absent, but GitHub still advertises the workflow identity as active.

The supported CI, fuzzing, CodeQL, Dependabot, and GitHub-owned agent workflows must be preserved. This issue does not authorize disabling those production or dynamic identities.

Root cause

Temporary PR reconstruction and repair workflows were removed from the repository tree after their bounded purpose, while their independent GitHub Actions registry records were not disabled. File deletion was treated as complete workflow lifecycle cleanup. Current source-level tests cannot detect orphaned control-plane records after the YAML disappears.

Realistic remediation

Do not restore historical YAML and do not create another self-deleting cleanup workflow. Under the repository's owner loop:

1. paginate the complete Actions registry;
2. bind evidence to the exact protected-main SHA and tree;
3. distinguish present repository workflows, active orphan records, disabled records, GitHub-owned dynamic workflows, and unresolved records;
4. refetch exact branch/workflow state immediately before mutation;
5. disable active orphan repository-path identities through an authorized operator or normal reviewed control-plane action;
6. preserve current CI/security/fuzz/dependency and supported product workflows;
7. retain immutable before/after evidence.

Coordinate with central lifecycle issue ContextualWisdomLab/.github#945 and AppGuardrail detector issue ContextualWisdomLab/appguardrail#929. Do not introduce another PAT, COPILOT_GITHUB_TOKEN, broad secrets: inherit, or workflow-disable authority into an untrusted scanner.

Acceptance criteria

• complete paginated inventory and exact default-branch binding;
• every reviewed active repository-path workflow absent from protected main disabled or explicitly justified;
• no current production or GitHub-owned dynamic workflow disabled by name-only matching;
• no historical rebuild/repair source reintroduced;
• read-only recurrence detector emits workflow ID, path, state, default-branch SHA, observation time, and pagination receipts;
• adversarial tests cover pagination truncation, permission loss, transient 403/404/5xx, branch movement, path case/encoding, renamed/reused workflow IDs, GitHub-owned dynamic workflows, and a legitimate present rebuild workflow owned by an active PR;
• exact-head CI/security/review gates;
• normal protected-main integration;
• post-remediation live inventory proves orphan identities disabled while supported Codec Carver automation remains operational.

This issue is part of the organization-wide GitHub Actions fleet incident. The fleet audit remains read-only and tracks protected-main operational evidence.