feat(operations): gate orphan workflow disablement by exact evidence - #274
feat(operations): gate orphan workflow disablement by exact evidence#274seonghobae wants to merge 19 commits into
Conversation
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 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. Comment |
|
@coderabbitai review Review exact current head |
Rate Limit Exceeded
|
|
Superseded by clean current-line successor #308, which preserves the bounded exact-evidence orphan-workflow planner/executor, adversarial tests, and owned-coverage contract. Closing this predecessor; its historical checks/reviews do not transfer. |
Purpose
Advance #226 with a bounded operator boundary for disabling only GitHub Actions workflow-registry orphans that are proven by exact read-only evidence. This is a pure planner/executor module, not a self-modifying workflow and not a batch mutation engine.
Exact identities
4573a6f7eaf904e19a6e3198c8cabcfd4be40c40acaee82abf54ffbe2f50bb50718438f59d33a3ee8ed0e9e251db358eaeaf3014e1534003981bf83afeat/workflow-registry-disable-planGREEN contract
The planner fails closed unless all of the following hold:
ContextualWisdomLab/noemaand the expected protected-main SHA;active_orphan_workflowfailures and no other failure type;.github/workflows/*.yml|*.yamlpaths.Passing plans and nested records are frozen and registered as process-local authorities. Serialized clones or reconstructed lookalikes remain evidence but cannot authorize mutation. Execution accepts one exact planned candidate, immediately re-reads its live ID/path/state, invokes only the injected disable primitive for that workflow ID, and returns a frozen mutation receipt.
The module is included in owned production coverage and has adversarial tests for repository/SHA drift, malformed schemas, timestamps and pagination, mixed/empty authority, duplicate or stale identities, unsafe paths, forged plans, serialized clones, unplanned candidates, state changes, and one-at-a-time execution.
Restack and verification boundary
The branch was merged with protected
mainafter #272, #266, and #275. The current merge tree overlays only the planner, its two test files, and the owned-coverage configuration on current protected-main bytes.Historical RED and predecessor evidence does not transfer. Application
ci,reviewer-ci, protected-base-eligibleSecurity Scan, and fresh review must complete successfully on unchanged current head8ed0e9e251db358eaeaf3014e1534003981bf83abefore merge. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.No workflow is disabled by this PR, no secret or permission is added, and no repair/self-modifying workflow, protection bypass, version bump, release, or deployment claim is introduced.
Related: #226, #267.