Mode 2 (client-local) of hyperguild's three-mode routing is live and serving 5 MCP tools from gitea.d-ma.be/mathias/routing at routing-mcp.d-ma.be — see infra commit a0f2d39 and docs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.md for the audit.
The supervisor pod still ships the old skill surface (full set including tdd_red/green/refactor, spec, tier) on :30320 plus the ingestion service on :30330. Supervisor was always scheduled for retirement once Mode 2 stabilized — that's the forward-reference Plan 7 in 2026-05-04-mode-2-routing-pod-design.md.
This issue tracks writing that Plan 7 and executing it.
Scope
Retire the supervisor MCP (the skill-worker half), keep the ingestion service (the brain-write half).
In scope:
Delete the supervisor binary's MCP-server code path
Delete the supervisor manifests that expose :30320
Delete internal/skills/{tdd,spec}/ — these were supervisor-only, never adopted by the routing pod. The note in the Mode 2 spec is explicit that only these two skill packages are removed; internal/skills/{review,debug,retrospective,trainer}/ are reused by routing and must stay.
Free NodePort :30320
Update any per-project .mcp.json files that still point at koala:30320 to point at routing (koala:30310 / https://routing-mcp.d-ma.be).
Out of scope:
ingestion service itself (the brain pod at :30330 / brain-mcp.d-ma.be). Stays.
Mode 1 (cloud) and Mode 3 (sovereign) plumbing.
Any changes to the routing pod itself (Plan 6 already shipped).
Acceptance criteria
Plan 7 document written in ~/dev/AGENTS/hyperguild/docs/superpowers/plans/2026-05-supervisor-retirement.md covering the scope above plus rollback steps
Supervisor MCP code path removed from the supervisor binary
Infra manifests under k3s/apps/supervisor/ no longer expose :30320
Search for any .mcp.json consumers of :30320 / supervisor MCP, migrate them to routing
After deploy: flux get kustomizations Ready=True, curl :30320/healthz returns connection-refused, routing :30310 tools/list still returns the 5 tools
Brain ingestion at :30330 still healthy (separate concern; should be unaffected)
Cross-references
2026-05-04-mode-2-routing-pod-design.md — Plan 6 spec, the constraint "internal/skills/{review,debug,retrospective,trainer}/ survives Plan 6", and the forward reference to Plan 7
docs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.md — audit of current routing-mcp surface
docs/superpowers/specs/2026-05-homelab-architecture-review.md — routing's KEEP decision references Plan 7 completion
Note
This is a hyperguild-repo concern with a small infra-repo trailing edge (delete supervisor's MCP manifests once the binary stops serving). File a corresponding infra issue when Plan 7 is ready to start; the manifest delete is a separate small commit on mathias/infra.
## Background
Mode 2 (`client-local`) of hyperguild's three-mode routing is live and serving 5 MCP tools from `gitea.d-ma.be/mathias/routing` at `routing-mcp.d-ma.be` — see infra commit `a0f2d39` and `docs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.md` for the audit.
The `supervisor` pod still ships the old skill surface (full set including `tdd_red/green/refactor`, `spec`, `tier`) on `:30320` plus the ingestion service on `:30330`. Supervisor was always scheduled for retirement once Mode 2 stabilized — that's the forward-reference Plan 7 in `2026-05-04-mode-2-routing-pod-design.md`.
This issue tracks writing that Plan 7 and executing it.
## Scope
Retire the supervisor MCP (the skill-worker half), keep the ingestion service (the brain-write half).
In scope:
- Delete the supervisor binary's MCP-server code path
- Delete the supervisor manifests that expose `:30320`
- Delete `internal/skills/{tdd,spec}/` — these were supervisor-only, never adopted by the routing pod. The note in the Mode 2 spec is explicit that **only** these two skill packages are removed; `internal/skills/{review,debug,retrospective,trainer}/` are reused by routing and must stay.
- Free NodePort `:30320`
- Update any per-project `.mcp.json` files that still point at `koala:30320` to point at routing (`koala:30310` / `https://routing-mcp.d-ma.be`).
Out of scope:
- ingestion service itself (the brain pod at `:30330` / `brain-mcp.d-ma.be`). Stays.
- Mode 1 (cloud) and Mode 3 (sovereign) plumbing.
- Any changes to the routing pod itself (Plan 6 already shipped).
## Acceptance criteria
- [ ] Plan 7 document written in `~/dev/AGENTS/hyperguild/docs/superpowers/plans/2026-05-supervisor-retirement.md` covering the scope above plus rollback steps
- [ ] Supervisor MCP code path removed from the supervisor binary
- [ ] `internal/skills/{tdd,spec}/` packages deleted
- [ ] `internal/skills/{review,debug,retrospective,trainer}/` packages explicitly preserved (per Mode 2 spec's constraint)
- [ ] Infra manifests under `k3s/apps/supervisor/` no longer expose `:30320`
- [ ] Search for any `.mcp.json` consumers of `:30320` / `supervisor` MCP, migrate them to routing
- [ ] After deploy: `flux get kustomizations` Ready=True, `curl :30320/healthz` returns connection-refused, `routing :30310 tools/list` still returns the 5 tools
- [ ] Brain ingestion at `:30330` still healthy (separate concern; should be unaffected)
## Cross-references
- `2026-05-04-mode-2-routing-pod-design.md` — Plan 6 spec, the constraint "internal/skills/{review,debug,retrospective,trainer}/ survives Plan 6", and the forward reference to Plan 7
- `docs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.md` — audit of current routing-mcp surface
- `docs/superpowers/specs/2026-05-homelab-architecture-review.md` — routing's KEEP decision references Plan 7 completion
## Note
This is a hyperguild-repo concern with a small infra-repo trailing edge (delete supervisor's MCP manifests once the binary stops serving). File a corresponding infra issue when Plan 7 is ready to start; the manifest delete is a separate small commit on `mathias/infra`.
Discovered 2026-05-22 during S1 spike that Plan 7 already shipped on 2026-05-12 — see ~/dev/AGENTS/hyperguild/CLAUDE.md (the file itself documents the retirement).
Current state verifies:
cmd/supervisor/ no longer exists in the hyperguild repo (only cmd/hyperguild and cmd/routing).
internal/skills/{tdd,spec}/ no longer exists (per the Plan 7 spec; tdd + spec moved to SKILL.md files).
internal/skills/ retains brain, debug, org, project, retrospective, review, sessionlog, trainer — all reused by routing or the brain MCP.
supervisor k8s namespace hosts only the ingestion service now. No :30320 listener; supervisor-MCP deployment manifests are gone.
Only lingering :30320 references are in historical context files (.aider.conventions.md, AGENTS.md, .context/PROJECT.md, .cursorrules, system-prompt.txt). None are active manifests.
Closing as already-done. The five context-file mentions of :30320 are stale text and worth a small cleanup pass in a follow-up commit, but not load-bearing — the actual binary, manifests, and skills are gone.
Discovered 2026-05-22 during S1 spike that Plan 7 already shipped on 2026-05-12 — see `~/dev/AGENTS/hyperguild/CLAUDE.md` (the file itself documents the retirement).
Current state verifies:
- `cmd/supervisor/` no longer exists in the hyperguild repo (only `cmd/hyperguild` and `cmd/routing`).
- `internal/skills/{tdd,spec}/` no longer exists (per the Plan 7 spec; `tdd` + `spec` moved to SKILL.md files).
- `internal/skills/` retains brain, debug, org, project, retrospective, review, sessionlog, trainer — all reused by routing or the brain MCP.
- supervisor k8s namespace hosts only the ingestion service now. No `:30320` listener; supervisor-MCP deployment manifests are gone.
- Only lingering `:30320` references are in historical context files (`.aider.conventions.md`, `AGENTS.md`, `.context/PROJECT.md`, `.cursorrules`, `system-prompt.txt`). None are active manifests.
Closing as already-done. The five context-file mentions of `:30320` are stale text and worth a small cleanup pass in a follow-up commit, but not load-bearing — the actual binary, manifests, and skills are gone.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Background
Mode 2 (
client-local) of hyperguild's three-mode routing is live and serving 5 MCP tools fromgitea.d-ma.be/mathias/routingatrouting-mcp.d-ma.be— see infra commita0f2d39anddocs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.mdfor the audit.The
supervisorpod still ships the old skill surface (full set includingtdd_red/green/refactor,spec,tier) on:30320plus the ingestion service on:30330. Supervisor was always scheduled for retirement once Mode 2 stabilized — that's the forward-reference Plan 7 in2026-05-04-mode-2-routing-pod-design.md.This issue tracks writing that Plan 7 and executing it.
Scope
Retire the supervisor MCP (the skill-worker half), keep the ingestion service (the brain-write half).
In scope:
:30320internal/skills/{tdd,spec}/— these were supervisor-only, never adopted by the routing pod. The note in the Mode 2 spec is explicit that only these two skill packages are removed;internal/skills/{review,debug,retrospective,trainer}/are reused by routing and must stay.:30320.mcp.jsonfiles that still point atkoala:30320to point at routing (koala:30310/https://routing-mcp.d-ma.be).Out of scope:
:30330/brain-mcp.d-ma.be). Stays.Acceptance criteria
~/dev/AGENTS/hyperguild/docs/superpowers/plans/2026-05-supervisor-retirement.mdcovering the scope above plus rollback stepsinternal/skills/{tdd,spec}/packages deletedinternal/skills/{review,debug,retrospective,trainer}/packages explicitly preserved (per Mode 2 spec's constraint)k3s/apps/supervisor/no longer expose:30320.mcp.jsonconsumers of:30320/supervisorMCP, migrate them to routingflux get kustomizationsReady=True,curl :30320/healthzreturns connection-refused,routing :30310 tools/liststill returns the 5 tools:30330still healthy (separate concern; should be unaffected)Cross-references
2026-05-04-mode-2-routing-pod-design.md— Plan 6 spec, the constraint "internal/skills/{review,debug,retrospective,trainer}/ survives Plan 6", and the forward reference to Plan 7docs/superpowers/handoffs/2026-05-21-routing-mcp-consumers.md— audit of current routing-mcp surfacedocs/superpowers/specs/2026-05-homelab-architecture-review.md— routing's KEEP decision references Plan 7 completionNote
This is a hyperguild-repo concern with a small infra-repo trailing edge (delete supervisor's MCP manifests once the binary stops serving). File a corresponding infra issue when Plan 7 is ready to start; the manifest delete is a separate small commit on
mathias/infra.Discovered 2026-05-22 during S1 spike that Plan 7 already shipped on 2026-05-12 — see
~/dev/AGENTS/hyperguild/CLAUDE.md(the file itself documents the retirement).Current state verifies:
cmd/supervisor/no longer exists in the hyperguild repo (onlycmd/hyperguildandcmd/routing).internal/skills/{tdd,spec}/no longer exists (per the Plan 7 spec;tdd+specmoved to SKILL.md files).internal/skills/retains brain, debug, org, project, retrospective, review, sessionlog, trainer — all reused by routing or the brain MCP.:30320listener; supervisor-MCP deployment manifests are gone.:30320references are in historical context files (.aider.conventions.md,AGENTS.md,.context/PROJECT.md,.cursorrules,system-prompt.txt). None are active manifests.Closing as already-done. The five context-file mentions of
:30320are stale text and worth a small cleanup pass in a follow-up commit, but not load-bearing — the actual binary, manifests, and skills are gone.