test(e2e): add migration inventory deletion gates

[cv]

Summary

Adds an initial migration inventory and deletion-readiness gates for converting legacy E2E coverage into Vitest scenarios. Stack PR 7/7. cc @jyaunches for review.

Related Issue

Refs #4941.

Changes

• Adds test/e2e-scenario/migration/legacy-inventory.json covering every direct legacy test/e2e/test-*.sh entrypoint plus the existing Brev Vitest bridge.
• Adds framework tests that fix the migration status vocabulary, validate inventory path existence, require target Vitest scenario and bridge probe paths to exist, and fail if a current direct legacy shell entrypoint is not represented.
• Updates migration docs and README to describe the narrow repo-local deletion-gate exception, including its Phase 11: Final Audit Reconciliation (E2E audit-coverage) #4357 removal/audit condition.

Type of Change

• Code change (feature, bug fix, or refactor)
• Code change with doc updates
• Doc only (prose changes, no code sample modifications)
• Doc only (includes code sample changes)

Verification

• npx vitest run --project e2e-scenario-framework test/e2e-scenario/framework-tests/e2e-migration-inventory.test.ts --silent=false --reporter=default
• npx vitest run --project e2e-scenario-framework --silent=false --reporter=default
• npm run typecheck:cli
• npx prek run --files test/e2e-scenario/docs/MIGRATION.md test/e2e-scenario/docs/README.md test/e2e-scenario/framework-tests/e2e-migration-inventory.test.ts test/e2e-scenario/migration/legacy-inventory.json
• Pre-push hooks passed during git push
• Tests added or updated for new or changed behavior
• No secrets, API keys, or credentials committed
• Docs updated for user-facing behavior changes
• npm run docs builds without warnings (doc changes only)
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: Carlos Villela cvillela@nvidia.com

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[coderabbitai]

Warning

Review limit reached

@cv, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 53 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ea980398-dc81-497d-a400-ee576ca3948b

📥 Commits

Reviewing files that changed from the base of the PR and between b65a7e0 and 1482662.

📒 Files selected for processing (4)

• test/e2e-scenario/docs/MIGRATION.md
• test/e2e-scenario/docs/README.md
• test/e2e-scenario/framework-tests/e2e-migration-inventory.test.ts
• test/e2e-scenario/migration/legacy-inventory.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/e2e-4941-stack-07-migration-inventory

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• None. No live E2E is required. The PR is limited to E2E migration documentation, a machine-readable legacy test inventory, and a framework metadata test; it cannot affect installer/onboarding, sandbox lifecycle, credentials, security boundaries, network policy, inference routing, deployment, or real assistant user flows. The relevant validation is the existing non-live Vitest project e2e-scenario-framework, not an E2E job.

Optional E2E

• None.

New E2E recommendations

• None.

[github-actions]

E2E Scenario Advisor Recommendation

Required scenario E2E: None
Optional scenario E2E: None

Workflow run

Full scenario advisor summary

E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required scenario E2E

• None. Changes are limited to scenario migration documentation, a framework test for the legacy migration inventory, and the inventory data itself. They do not modify scenario workflows, runtime/runner code, scenario or expected-state metadata, suite metadata/scripts, onboarding/install helpers, or live scenario behavior.

Optional scenario E2E

• None.

Relevant changed files

• test/e2e-scenario/docs/MIGRATION.md
• test/e2e-scenario/docs/README.md
• test/e2e-scenario/framework-tests/e2e-migration-inventory.test.ts
• test/e2e-scenario/migration/legacy-inventory.json

[github-actions]

PR Review Advisor

Findings: 0 needs attention, 0 worth checking, 0 nice ideas
Since last review: 4 prior items resolved, 0 still apply, 0 new items found

Consider writing more tests for

• **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 issue Adopt Vitest fixtures as the E2E scenario execution model #4941 body or comments, so no issue-specific acceptance clauses could be extracted or mapped beyond the reference.

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.