Goal Framing Continues by Default
- Clarified across the workflow guides, README surfaces, and the
goal-framingskill thatAegis goal:is a start protocol, not a stop
point. - Documented the default behavior: after producing the compact
TaskIntentDraft, Aegis should continue into the routed workflow in the same
turn when the user asked to do the work. - Locked the explicit stop boundary: frame-only behavior applies only when the
user clearly asks to only define the goal or stop condition, to not execute,
to not implement, to not write a plan, or to wait for confirmation.
Workflow Quality Contract Coverage
- Extended the workflow quality baseline and fixture matrix so
goal-framing
now requires a visibleContinuationcontract field. - Added matrix and harness checks that forbid stopping after
TaskIntentDraftin the default path and require continuation evidence in
the routed workflow. - Updated the workflow quality matrix validator so the
goal-framingcontract
explicitly checks bothStop conditionandContinuation.
Version
- Bumped all declared plugin, marketplace, package, and extension manifests to
1.9.5.
Verification
bash scripts/bump-version.sh 1.9.5bash scripts/bump-version.sh --auditpython -m py_compile tests/helpers/validate_workflow_quality_matrix.pypython tests/helpers/validate_workflow_quality_matrix.py tests/e2e/fixtures/workflow-quality-matrix.jsonbash tests/e2e/goal-framing-check.shbash tests/e2e/workflow-quality-check.shpython tests/helpers/test_parse_codex_skills.pybash tests/e2e/layer1-fast-check.sh --host-profile nonebash tests/e2e/run-all.sh --full --host-profile fastgit diff --check