ci(actions): disable orphaned workflow registrations

[proerror77]

This was generated by AI during triage.

Parent

None.

What to change

Disable the ten GitHub Actions workflow registrations whose files are absent
from main but whose API state remains active. Preserve run history and leave
every workflow still present on main enabled.

Runtime contract

• Target: proerror77/monday Actions workflow IDs 173243005,
  315720624, 315663508, 315752598, 315745544, 315625712,
  315785486, 315726161, 315690315, and 315718040.
• Controller: Codex task /root.
• Candidate/configuration: change each exact workflow from active to
  disabled_manually; no repository file changes.
• Rollback: call the GitHub Actions enable endpoint for the same IDs.
• Stop rule: stop and restore already changed IDs if any target path exists
  on current main, any target has a queued or in-progress run, or any API
  mutation does not succeed.
• Cleanup: verify all current main workflows remain active, the ten target
  states are disabled, and historical runs remain readable.

Acceptance criteria

• The ten orphaned registrations report disabled_manually.
• Every workflow file present on main remains active.
• No run history is deleted.
• Rollback commands and post-change evidence are recorded on this issue.

Blocked by

None.

Out of scope

Deleting workflow runs, changing current workflow files, disabling a workflow
present on main, or changing CI gates and repository merge policy.

[proerror77]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Disable stale Actions registrations left behind after temporary
workflow files were removed from main.

Current behavior:
Ten deleted workflow paths still appear as active through the GitHub Actions
API. They cannot be maintained from the current repository and add misleading
control-plane noise.

Desired behavior:
Only workflows backed by files on main remain active. Historical runs stay
available and every disabled registration has an explicit enable rollback.

Key interfaces:

• GitHub Actions workflow state API
• Exact path comparison against current main
• Exact run-state preflight before mutation

Acceptance criteria:

• Exact orphan set is disabled.
• Current workflows remain active.
• Historical runs remain readable.
• Runtime evidence and rollback are recorded before closure.

Out of scope:

• Workflow source changes
• Run-history deletion
• Merge-policy changes

[proerror77]

Runtime closure evidence

• Target: proerror77/monday Actions workflow IDs 173243005,
  315720624, 315663508, 315752598, 315745544, 315625712,
  315785486, 315726161, 315690315, and 315718040.
• Controller: Codex task /root only.
• Source/configuration: preflight used main@44ad7ef73e8a30cb30656a13037792ef4cfa678a;
  every target path was absent, every target state was active, and no target
  had a queued or in-progress run.
• Stop rule: not hit; all ten disable API calls succeeded.
• Result: all ten targets now report disabled_manually.
• Current workflow protection: the sorted set of active API workflow paths
  exactly matches the sorted set of *.yml workflow files on current main.
• History: the latest historical run for every target remains readable;
  no run was deleted.
• Cleanup: no repository file, branch, worktree, PR, deployment, or runtime
  job was created for this control-plane change.

Rollback

Re-enable the exact set with:

for workflow_id in 173243005 315720624 315663508 315752598 315745544 315625712 315785486 315726161 315690315 315718040; do
  gh api --method PUT "repos/proerror77/monday/actions/workflows/$workflow_id/enable"
done