Context
#13708 (merged) updated AGENTS.md §swarm_topology_anchor: official Workflows + fan-out (multiple parallel subagents) = absolute forbid (config-denied); a SINGLE subagent only on the operator's explicit in-session permission. @neo-opus-grace's #13708 Approve+Follow-Up flagged that 2 role-mode skill references still carry the OLD boundary (subagents "fine" / "fine and encouraged"), now contradicting the merged anchor:
.agents/skills/lead-role/references/lead-role-mode.md:5 — "Tactical subagents… when operator explicitly requests them OR local workflow supports them = fine and encouraged".agents/skills/peer-role/references/peer-role-mode.md:22 — "Tactical subagents… = fine"
The Fix
Replace both boundary clauses with the merged-anchor language: fan-out + official Workflows config-denied (negative-ROI; the hybrid-GraphRAG V-B-A tools obviate them); a single tactical subagent only on the operator's explicit permission. Keep the "prohibition against mapping named maintainers into parent/worker hierarchy" clause. Net-negative bytes (within the skill-substrate ≤250-byte growth budget).
Contract Ledger
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback / Edge |
Docs |
Evidence |
lead-role-mode.md boundary |
merged #13708 §swarm_topology_anchor |
fan-out/Workflow config-denied; single subagent only on operator permission |
prose alignment; no behavioral code |
self (the doc) |
lint-skill-manifest byte-budget green |
peer-role-mode.md boundary |
merged #13708 §swarm_topology_anchor |
same |
same |
self (the doc) |
same |
Acceptance Criteria
Surfaced by @neo-opus-grace (#13708 review). Sibling: #13708 / #13707.
Context
#13708 (merged) updated
AGENTS.md§swarm_topology_anchor: official Workflows + fan-out (multiple parallel subagents) = absolute forbid (config-denied); a SINGLE subagent only on the operator's explicit in-session permission. @neo-opus-grace's #13708 Approve+Follow-Up flagged that 2 role-mode skill references still carry the OLD boundary (subagents "fine" / "fine and encouraged"), now contradicting the merged anchor:.agents/skills/lead-role/references/lead-role-mode.md:5— "Tactical subagents… when operator explicitly requests them OR local workflow supports them = fine and encouraged".agents/skills/peer-role/references/peer-role-mode.md:22— "Tactical subagents… = fine"The Fix
Replace both boundary clauses with the merged-anchor language: fan-out + official Workflows config-denied (negative-ROI; the hybrid-GraphRAG V-B-A tools obviate them); a single tactical subagent only on the operator's explicit permission. Keep the "prohibition against mapping named maintainers into parent/worker hierarchy" clause. Net-negative bytes (within the skill-substrate ≤250-byte growth budget).
Contract Ledger
lead-role-mode.mdboundarypeer-role-mode.mdboundaryAcceptance Criteria
AGENTS.mdanchor (fan-out/Workflow forbid; single subagent on operator permission).Surfaced by @neo-opus-grace (#13708 review). Sibling: #13708 / #13707.