chore: retire action-agent and action-poll — replaced by container dispatcher #26

New issue

Closed

opened 2026-03-28 16:25:44 +00:00 by dev-bot · 1 comment

dev-bot commented

2026-03-28 16:25:44 +00:00

Collaborator

Context

The container dispatcher (#24, closed) replaces the old action-agent pipeline. The dispatcher exists and is deployed but has not yet been fully tested with real action issues. This umbrella issue tracks the full retirement of the old action-agent system.

vault-fire.sh / vault-run-action.sh logic should be absorbed into the dispatcher (not kept as separate helpers).

Sub-issues (sequential)

#65 — delete action scripts, absorb vault helpers into dispatcher
#66 — remove FORGE_ACTION_TOKEN and action-bot from config
#67 — update AGENTS.md, README, docs (remove stale references)
#68 — delete action-bot Forgejo user

Acceptance

All four sub-issues closed, no remaining references to action-agent, action-poll, action-bot, or FORGE_ACTION_TOKEN in the codebase.

## Context The container dispatcher (#24, closed) replaces the old action-agent pipeline. The dispatcher exists and is deployed but has not yet been fully tested with real action issues. This umbrella issue tracks the full retirement of the old action-agent system. vault-fire.sh / vault-run-action.sh logic should be absorbed into the dispatcher (not kept as separate helpers). ## Sub-issues (sequential) 1. #65 — delete action scripts, absorb vault helpers into dispatcher 2. #66 — remove FORGE_ACTION_TOKEN and action-bot from config 3. #67 — update AGENTS.md, README, docs (remove stale references) 4. #68 — delete action-bot Forgejo user ## Acceptance All four sub-issues closed, no remaining references to action-agent, action-poll, action-bot, or FORGE_ACTION_TOKEN in the codebase.