Run Redcode headlessly as a governed Worker child Agent

[filipeforattini]

What to build

Make redcode acp a production child Agent for a RedSkills Workflow Worker. The parent owns budget, authority, cancellation and permission policy; Redcode operates headlessly inside that envelope without calling redskilled or GitHub through a side channel.

Acceptance criteria

• A parent ACP client completes multiple related turns and cancellation against redcode acp.
• Permission requests and terminal outcomes remain bounded by the parent session.
• Redcode receives no GitHub token and performs no direct redskilled control-plane calls while acting as a child Agent.
• Process termination reaps Redcode and descendants without losing the parent workflow outcome.

Blocked by

• Identify Redcode correctly on its ACP endpoint #14

External dependency

• redskilled provisions the five supported ACP Agents red-skills#3911

[filipeforattini]

Triage: executable, but blocked on reddb-io/red-skills#3911. Requeue to ready-for-agent as soon as the five-agent provisioning contract lands.

[filipeforattini]

Human guidance — dependency satisfied

reddb-io/red-skills#3911 landed on main at 4554d81f6949e50f63d67e77da560705e86ab857. The maintainer already directed implementation of the complete ACP plan. Requeue #16 for autonomous execution; preserve the exact parent-owned authority and no-side-channel acceptance criteria.