Faster startup routing with unchanged governance coverage
Aegis v2.9.1 reduces startup routing pressure while preserving the existing
method-pack semantics and verification contracts.
Highlights
- Reduced the
using-aegisstartup router from 3,434 to 2,712 bytes, below the
approved 2,800-byte target. - Kept startup routing focused on primary workflow-owner selection and moved
detailed strict/light TDD semantics to the existing on-demand discipline
reference. - Kept explanation-only and read-only diagnosis tasks outside implementation,
TDD, and write gates to avoid unnecessary routing work in high-reasoning
Codex sessions. - Preserved goal framing, brainstorming, debugging, change-necessity,
task-snapshot, architecture-review, workspace, evidence-hygiene, and
traceability contracts through deterministic regression coverage. - Restored the approved context-budget thresholds of 2,800 bytes (warning
target) and 3,200 bytes (hard fail).
Verification
- Context-budget, TDD-policy, manifest JSON, diff, boundary, governance,
skill-parser, and Codex plugin-sync checks passed. - Governance completion, Layer 2, and Layer 3 of the full E2E release command
passed. - Layer 1 retained the documented Windows/Git Bash limitation for the offline
Codex benchmark fixture. - Natural and explicit Codex
brainstormingrouting smokes passed through the
host boundary, loading bothusing-aegisandbrainstormingfrom the release
candidate.
After updating or reinstalling Aegis, start a fresh host session so cached or
copied skill views do not retain the previous router. No manual global routing
prefix migration is required.