Skip to content

v2.2.5 Forge simplification, 05A/05B split, and E2E execution boundary

Choose a tag to compare

@Haaaiawd Haaaiawd released this 06 May 05:57
· 9 commits to main since this release

/forge

  • Removed the dedicated §3.5 Compliance section and its footer checklist row.
  • Step 4.2 wave recap now includes Code review (findings & fixes) with severity, fixed-in-wave scope, remaining follow-ups, and pointer to the §3.4.5 review block (or explicit CODE_REVIEW_DISABLED_BY_USER).
  • Wave records now explicitly carry a Code review status line as part of closure reporting, so review state is visible at the same layer as task progress.
  • Kept the §3.4.5.1 minimal delivery index embedded in the wave recap.
  • Strengthened §3.6 commit as an atomic mandatory step: commit first (including 3.3.4 compliance statement), then write back task progress.

Testing Standard Integration

  • blueprint now treats both Unit Test and API Interface Functional Test as required planning outputs for core business/API scope.
  • Added explicit planning constraints for normal/boundary/invalid inputs, state transitions, exception handling, API error semantics, permissions, and before/after assertions for data-changing interfaces.
  • System design testing guidance is aligned to produce executable test plans and evidence artifacts (cases/scripts/reports), not only descriptive text.

Task/Verification Two-Track Model (05A/05B)

  • Replaced single-file task model with:
    • 05A_TASKS.md (execution task list)
    • 05B_VERIFICATION_PLAN.md (verification plan)
  • Clear ownership split:
    • 05A: WBS, dependencies, sprint, INT, progress, User Story Overlay
    • 05B: verification layering, risk coverage, task-by-task verification, evidence requirements, traceability matrix
  • Mandatory traceability closure:
    • every 05A task requires Verification Reference
    • 05B must keep all three required sections:
      • Contract Coverage Overlay
      • Testing Coverage Overlay
      • Verification Traceability Matrix
  • Workflow and skill chain aligned to 05A/05B across blueprint, forge, change, challenge, reviewers, and AGENTS.md (zh/en templates).

E2E Execution Boundary

  • blueprint and task-planner only record E2E trigger assumptions, scope, and expected evidence in 05A/05B.
  • Planning phase must not execute e2e-testing-guide.
  • Actual E2E guide generation and real-browser execution are triggered in /forge.

Upgrade

npm install -g @haaaiawd/anws@latest
anws update