Aegis v2.7.2
Highlights
Maintenance release tightening the routing descriptions that gate documentation, branch/worktree, and subagent decisions.
What's New
Fix: Routing Descriptions Tightened Across Three Decision Themes
- Document creation:
establishing-project-contexttrigger narrowed (removed the broad "vague term", now conflicting/renamed/deprecated, plus "Routine small tasks stay on the fast path");first-principles-review"repeated fixes" replaced with "high-risk decisions" plus an exclusion. Small tasks no longer get pulled into formal modeling/review flows. - Branch/worktree:
finishing-a-development-branchnow reads "integration or cleanup of an existing task-created branch/worktree", aligned with ADR-0003 exception-only discipline instead of implying Aegis creates branches by default. - Subagent/session routing: the cross-session (
executing-plans) vs current-session (subagent-driven-development) distinction is now written into both descriptions;dispatching-parallel-agentsis scoped to "2+ independent tasks without a written plan", removing the routing overlap with SDD; SDD points ad-hoc tasks to dispatching-parallel-agents.
All six descriptions stay within the 240-char Kimi Code limit. Validation: 22 Kimi-visible skill metadata files valid, context budget, workflow quality, and TDD policy checks pass.