Summary
Aegis v2.1.7 improves method-pack requirements readiness and tightens native-host TDD trigger boundaries.
Requirements Baseline Readiness
- Expanded the public Product / Requirement Baseline model to include requirement sources, goals and scope, users and scenarios, requirement categories, acceptance and verification criteria, open questions, and change records.
- Added a lightweight Requirement Ready Check to the design, planning, and completion workflows without creating a runtime gate or completion authority.
- Updated brainstorming, writing-plans, and verification-before-completion to surface missing requirement context before design recommendations, task decomposition, or completion claims.
- Clarified that completed tasks or slices must not be overstated as accepted requirement satisfaction.
TDD Trigger Boundary
- Narrowed native-host entry into test-driven-development to explicit markers such as
TDD Route: strict,strict TDD,test-first, orRED / GREEN / REFACTOR. - Documented the AEGIS_TDD_MODE=off boundary for Codex and native direct-skill hosts.
- Added policy samples preventing strict TDD from being inferred from risky implementation wording alone when TDD mode is off.
Release Surface
- Bumped package and host manifest versions to 2.1.7.
- Extended workflow-quality and TDD policy checks for the new readiness and trigger boundaries.
Verification
git diff --checkpython tests/helpers/test_parse_codex_skills.pyscripts/bump-version.sh --checktests/e2e/workflow-quality-check.shtests/e2e/tdd-policy-check.shtests/e2e/trigger-health-check.shtests/e2e/layer1-fast-check.sh --host-profile none