feat(fleet): enhancer role + two-agent floor (orchestrator + enhancer) #615
Reference in New Issue
Block a user
Delete Branch "feat/fleet-enhancer-floor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fleet enhancer role + two-agent floor (closes #614)
Implements Jason's north-star (
docs/fleet/north-star.md, #613): every fleet has a two-agent floor — orchestrator + enhancer minimum. Builds directly on my #612 init-R5 work.Changes
enhancer— claude,class: enhancer,persistent_persona: true— as a core always-on agent alongside the orchestrator.minimal/local-canaryunchanged.fleet.ts:countEnhancershelper.removeAgentFromRosterrefuses to drop the sole enhancer (symmetric with the existing sole-orchestrator guard), so the floor holds at runtime, not just at init.framework/fleet/roles/enhancer.md— the enhancer mandate: monitor → analyze → plan remediation → upgrade tools/skills/harness with the orchestrator → file Mosaic Stack bug reports. Boundaries: does NOT code or review.Verification
countEnhancers; sole-enhancer remove guard; remove-allows-when-another; init two-agent-floor; every-non-minimal-preset-has-enhancer; updated preset-roster assertions. tsc/eslint/prettier/sanitize clean. TDD on the init guarantee + remove protection.Stacking (for the batch)
This is stacked on #612 (
feat/fleet-polish-bundle) — its init code is #612's. The branch currently carries #612's commit too. Merge order: #612 → this. After #612 merges (squash), I'll rebase this ontomain(the dup #612 work drops) so the final diff is enhancer-only. Ping me to rebase, or retarget on merge.🤖 Generated with Claude Code
f27371be7ato5e73481f0a