ci: add workflow_dispatch so CI can be re-fired without a dummy commit

[UnbreakableMJ]

Context

Between 2026-08-05T21:03Z and 2026-08-07 this repository created no workflow run at all — not for a pull request, not for a push to main — while:

• the workflow reported state=active
• Actions reported enabled (allowed_actions: all)
• the triggers were pull_request + push: [main]
• the file parsed cleanly

Sibling repositories in the same org ran normally in that window — Standard's push to main ran and passed, and a fresh Engram PR ran all five of its checks — so this was specific to this repository and invisible from the API: nothing queued, nothing waiting, and no failed run to notice.

Two merges landed here unvalidated as a result (#31 and the Guile-mirror commit). Their gates were run by hand against merged main instead — reuse lint clean, validate-configs 302/0, description cap clean, check-skill-refs OK, steelbore.scm in sync — but "run it by hand and trust the transcript" is not a gate.

What this changes

Adds workflow_dispatch: to the existing triggers, so the recovery path is a command rather than a commit:

gh workflow run ci.yml --ref main

The alternative was a commit whose only purpose is to produce an event, pushed straight to main — exactly what the branch-and-PR rule forbids.

Worth having permanently rather than as a one-off: the lint job is what enforces the §5.6 description cap and the steelbore.scm drift check, and both fail silently when unenforced. That is the same class of gap that let §3.2.1 sit unpublished for months.

No job, step, or trigger behavior changes. This only adds a way to start the existing workflow by hand.

Verification

• The workflow parses with all three triggers present (pull_request, push, workflow_dispatch) and the lint job's 8 steps intact
• validate-configs.py — which walks this very file — 302 checked, 0 failed
• reuse lint clean

Note: workflow_dispatch only becomes invocable once it is on the default branch, so this PR itself cannot demonstrate the manual trigger. If CI is still not firing on this PR, that is the bug this exists to work around — and dispatching after merge is the test.

🤖 Generated with Claude Code

https://claude.ai/code/session_014X5VySpBN97Nu8YjHy7gwo

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.