E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• e2e-branch-validation:full (Brev CPU instance credits; workflow header estimates about $0.10/run, typically around 10-30 minutes for full suite provisioning plus execution): Required because the PR changes the exact workflow and Vitest gating that enable the Brev branch-validation E2E. Running the existing full branch-validation suite verifies the sentinel is present, the e2e-branch-validation Vitest project includes test/e2e/brev-e2e.test.ts, and the clean Brev source install/onboard/live-inference path still executes instead of silently matching no tests.

Optional E2E

• e2e-scenarios:ubuntu-repo-cloud-openclaw (Moderate; GitHub-hosted Ubuntu runner with live scenario setup and NVIDIA API secret): Optional adjacent confidence for the live scenario framework path because the PR introduces an e2e-scenarios-live Vitest project gate. The existing typed scenario workflow remains the authoritative live scenario runner, and this representative OpenClaw source-install scenario can confirm scenario dispatch still works, but the PR does not change scenario runtime code so it should not block merge.

New E2E recommendations

• e2e-scenarios-live-vitest-project (medium): The PR adds a gated e2e-scenarios-live Vitest project pointing at test/e2e-scenario/live/**/*.test.ts, but this checkout does not currently contain that live test directory and no workflow appears to invoke NEMOCLAW_RUN_E2E_SCENARIOS=1 npx vitest run --project e2e-scenarios-live. Consider adding a future workflow-level smoke or contract once live Vitest scenario tests exist so this project cannot remain configured but unexercised.
  • Suggested test: Add a workflow-dispatched e2e-scenarios-live smoke that sets NEMOCLAW_RUN_E2E_SCENARIOS=1 and verifies at least one live scenario test is collected/executed.

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: medium

Required scenario E2E

• None. No scenario E2E dispatch is recommended. The scenario-relevant changes add Vitest gating/config tests for live scenario project selection, but they do not change the scenario runner/runtime used by .github/workflows/e2e-scenarios.yaml, scenario catalog metadata, expected-state contracts, suite catalog metadata, or suite scripts. The branch-validation workflow change belongs to the non-scenario/general E2E surface and is intentionally not considered here.

Optional scenario E2E

• None.

Relevant changed files

• test/e2e-scenario/framework-tests/e2e-live-project-config.test.ts
• test/e2e-scenario/framework/live-project-gate.ts
• vitest.config.ts

• **Runtime validation** — Import `vitest.config.ts` with no CI or opt-in env and verify `installer-integration`, `e2e-scenarios-live`, and `e2e-branch-validation` include arrays are all empty.. The helper-level and workflow-contract coverage is adequate for the PR, and the prior CI-dependent test failure is resolved. Because `vitest.config.ts` computes include arrays at import time from `process.env`, controlled config-import permutations would improve confidence for this workflow/test-runner infrastructure.
• **Runtime validation** — Import `vitest.config.ts` with `CI=true` and verify `installer-integration` includes `test/install-preflight.test.ts` and `test/install-openshell-version-check.test.ts` while live and branch-validation projects remain empty absent their gates.. The helper-level and workflow-contract coverage is adequate for the PR, and the prior CI-dependent test failure is resolved. Because `vitest.config.ts` computes include arrays at import time from `process.env`, controlled config-import permutations would improve confidence for this workflow/test-runner infrastructure.
• **Runtime validation** — Import `vitest.config.ts` with `NEMOCLAW_RUN_INSTALLER_TESTS=1` and no CI env and verify installer integration includes both installer tests.. The helper-level and workflow-contract coverage is adequate for the PR, and the prior CI-dependent test failure is resolved. Because `vitest.config.ts` computes include arrays at import time from `process.env`, controlled config-import permutations would improve confidence for this workflow/test-runner infrastructure.
• **Runtime validation** — Import `vitest.config.ts` with `NEMOCLAW_RUN_E2E_SCENARIOS=1` and verify `e2e-scenarios-live` includes `test/e2e-scenario/live/**/*.test.ts`.. The helper-level and workflow-contract coverage is adequate for the PR, and the prior CI-dependent test failure is resolved. Because `vitest.config.ts` computes include arrays at import time from `process.env`, controlled config-import permutations would improve confidence for this workflow/test-runner infrastructure.
• **Runtime validation** — Import `vitest.config.ts` with `NEMOCLAW_RUN_BRANCH_VALIDATION_E2E=1` and no Brev auth env and verify `e2e-branch-validation` includes `test/e2e/brev-e2e.test.ts`.. The helper-level and workflow-contract coverage is adequate for the PR, and the prior CI-dependent test failure is resolved. Because `vitest.config.ts` computes include arrays at import time from `process.env`, controlled config-import permutations would improve confidence for this workflow/test-runner infrastructure.
• **Acceptance clause:** Refs Adopt Vitest fixtures as the E2E scenario execution model #4941. — add test evidence or identify existing coverage. The deterministic context did not include linked issue Adopt Vitest fixtures as the E2E scenario execution model #4941 body or comments (`linkedIssues: []`), so issue-specific clauses could not be mapped. Repository docs confirm Adopt Vitest fixtures as the E2E scenario execution model #4941 is the Vitest fixture/single-runner execution-model decision context.