agy-fast-worker

Agy Fast Worker Compatibility Forwarder

This one-release compatibility entry point resolves to agy-worker in workspace-write mode. New dispatches use the canonical role; legacy callers retain requested_role=agy-fast-worker and effective_role=agy-worker through the immutable role contract.

Follow agents/agy-worker.md for prompt composition, recovery, verification, edited-file accounting, and reporting. Preserve its host-executable tools and replace its direct adapter invocation with the canonical launcher below.

Forward through the canonical launcher

Invoke only the repository-owned launcher; it resolves the alias before starting the provider adapter:

node "${CLAUDE_PLUGIN_ROOT}/skills/dhpk-cli-dispatch-context/scripts/launch-cli-dispatch.js" \
  --dispatching-agent "<dispatcher-role>" \
  --execution-provider agy \
  --requested-role agy-fast-worker \
  --mode workspace-write \
  --task-id "<task-id>" \
  --attempt-id "<attempt-id>" \
  --workdir "<absolute-workdir>" \
  --prompt "<absolute-prompt-file>" \
  --scope "<absolute-scope-json>" \
  --config-layer "<absolute-config-json>"

The dispatching agent may be Codex; that does not change the execution provider from AGY. Keep --dispatching-agent as the actual dispatcher identity and --execution-provider agy as the provider selection.

The resulting context must retain requested_role=agy-fast-worker, resolve effective_role=agy-worker, bind provider agy, and bind authority workspace-write. The launcher exports DHPK_CLI_TRANSPORT_CONTEXT and starts the selected adapter only after context construction returns READY. A missing or contradictory role, mode, provider, authority, path, scope, transport, model, or receipt is BLOCKED; never fabricate the context or call the adapter directly.

Mid-batch timeout recovery (multi-file dispatch only)

A runner exit 124 is timeout evidence only when the contained dhpk.cli.receipt.v1 has terminal TIMEOUT; a missing, invalid, or uncontained receipt is BLOCKED. On the first verified timeout, request exactly one same-backend, same-model recovery scoped to remaining ∪ unconfirmed. Never self-edit the unresolved files or repeat confirmed files. During recovery, never fall back to another backend because of a timeout.