test(e2e): E2E acceptance criteria for M2 (v3.1.0) — actor compiler and LLM integration #793

Closed
freemo wants to merge 1 commits from test/e2e-m2-acceptance into master

1 Commits

Author SHA1 Message Date
freemo d879ba1f96 test(e2e): E2E acceptance criteria for M2 (v3.1.0) — actor compiler and LLM integration
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 15s
CI / quality (pull_request) Successful in 20s
CI / build (pull_request) Successful in 19s
CI / security (pull_request) Successful in 35s
CI / typecheck (pull_request) Successful in 36s
CI / e2e_tests (pull_request) Failing after 52s
CI / integration_tests (pull_request) Successful in 2m58s
CI / unit_tests (pull_request) Successful in 3m36s
CI / docker (pull_request) Successful in 35s
CI / coverage (pull_request) Successful in 4m41s
CI / benchmark-regression (pull_request) Failing after 40m8s
Add Robot Framework E2E test suite robot/e2e/m2_acceptance.robot exercising
M2 acceptance criteria with zero mocking. Test creates a temp git repo with
sample project files, registers a custom actor via CLI, sets up resource and
project, creates an action referencing the actor, and runs the full plan
lifecycle (use → execute strategize → execute → diff → apply). Validates
actor YAML compilation, skill registry, tool lifecycle, and LLM integration
through real CLI invocations with real provider API keys. Uses flexible
structural assertions and expected_rc=None for LLM-dependent commands.

ISSUES CLOSED: #742
2026-03-13 23:10:21 +00:00