test(e2e): add setup_scenarios aliases for 13 layered test_plans (epic #3588 Phase 4) #4378

Summary

Add setup_scenarios aliases in test/e2e-scenario/nemoclaw_scenarios/scenarios.yaml for the 13 layered test_plans that currently have no user-friendly scenario ID. This unblocks deletion of the legacy scenarios/run.ts TS framework and removes a hidden coupling where the only thing that knew these IDs was the deleted listScenarios() registry.

This is Phase 4 (Onboarding Matrix Expansion) follow-up work for epic #3588. The onboarding profiles and test_plans already exist; only the user-friendly aliases are missing.

Background

While cleaning up the obsolete test/e2e-scenario/scenarios/run.ts runner (replaced by test/e2e-scenario/runtime/run-scenario.sh), we found that the OLD TS registry (scenarios/scenarios/baseline.ts) defined 23 user-friendly scenario IDs, but the new nemoclaw_scenarios/scenarios.yaml only declares 10 under setup_scenarios. The remaining 13 exist only as test_plans with internal __-form IDs.

Several places still reference the missing user-friendly IDs and currently rely on the OLD registry to resolve them:

• .github/workflows/e2e-scenarios.yaml — ROUTES table maps these IDs to runner types.
• test/e2e-scenario-advisor.test.ts — advisor test asserts ubuntu-repo-cloud-openclaw-telegram resolves.
• tools/e2e-advisor/scenarios.mts — enumerates scenarios for the advisor.

Missing user-friendly IDs (13)

Each maps 1:1 to an existing test_plans entry via alias_for_plan:

(That's 12 in the table — the 13th depends on whether ubuntu-repo-cloud-openclaw and the negative-path IDs are reconciled separately. Confirm during implementation.)

Acceptance criteria

• Each ID above exists as a setup_scenarios: entry with alias_for_plan: <plan-id>.
• bash test/e2e-scenario/runtime/run-scenario.sh <each-id> --plan-only succeeds for all 13 IDs.
• .github/workflows/e2e-scenarios.yaml ROUTES table is unchanged (every ID still maps).
• tools/e2e-advisor/scenarios.mts enumerates these IDs from YAML (no TS registry dependency).
• test/e2e-scenario-advisor.test.ts passes against the YAML resolver (currently fails on ubuntu-repo-cloud-openclaw-telegram).
• Framework-tests under test/e2e-scenario/framework-tests/ continue to pass.

Context — companion cleanup

This issue is the prerequisite for landing the cleanup PR that deletes the obsolete run.ts path:

• Deletes test/e2e-scenario/scenarios/ (entire OLD TS framework, 33 files)
• Deletes test/e2e-scenario/manifests/ (only consumed by OLD framework)
• Deletes test/e2e-scenario/onboarding_assertions/ (dead in NEW path)
• Deletes 6 framework-tests that only test the OLD framework
• Switches .github/workflows/e2e-scenarios.yaml from npx tsx ...run.ts to bash ...run-scenario.sh

That cleanup PR can land now (with the advisor test deferred). Once this issue lands, the advisor test will pass against the YAML resolver and the migration is fully complete.

Parent

Epic #3588 (Phase 4: Onboarding Matrix Expansion).