test(e2e): validate M3 acceptance criteria for v3.2.0 milestone closure #527

Closed
hurui200320 wants to merge 1 commits from test/m3-acceptance-gate into master

1 Commits

Author SHA1 Message Date
hurui200320 80d5b92090 test(e2e): validate M3 acceptance criteria for v3.2.0 milestone closure
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 15s
CI / quality (pull_request) Successful in 18s
CI / build (pull_request) Successful in 19s
CI / typecheck (pull_request) Successful in 33s
CI / security (pull_request) Successful in 34s
CI / unit_tests (pull_request) Successful in 2m13s
CI / integration_tests (pull_request) Successful in 2m47s
CI / docker (pull_request) Successful in 41s
CI / coverage (pull_request) Successful in 3m44s
CI / benchmark-regression (pull_request) Successful in 23m51s
Ran the M3 E2E verification suite (robot/m3_e2e_verification.robot) against
the complete v3.2.0 implementation. All 10 tests pass without modification:

- Plan execution generates decisions during Strategize
- Decision tree view via plan tree
- Decision explain shows full context snapshot
- Invariant add and list via CLI and service
- Correction dry-run via plan correct
- Correction live revert executes and re-creates decisions
- Decisions recorded with full context snapshot (round-trip)
- Decision tree persists to database and renders correctly
- Correction revert re-executes from decision point
- Invariants enforced during strategize (merge precedence)

Quality gates verified: lint clean, pyright 0 errors, 7817 BDD scenarios
pass, coverage at 97%.

Added acceptance criteria tags (success_criteria, technical_criteria) and
milestone tags (m3, acceptance_gate, v3.2.0) to the robot suite for
filtering and discoverability. Enhanced suite and test documentation with
milestone cross-references.

ISSUES CLOSED: #494
2026-03-03 08:44:35 +00:00