Plan — MT-14: Run full E2E suite on rc/multi-tenant and fix regressions#

Summary#

Validate the rc/multi-tenant release branch by triggering the full E2E test suite via workflow_dispatch on e2e-full.yml, triaging any failures as regressions vs pre-existing, fixing regressions in-branch, and confirming the RC is merge-ready. Note: rc/multi-tenant is currently at the same commit as master (386bd31), so any failures found are pre-existing rather than regressions from the refactor.

Files#

File	Action	Description
`.github/workflows/e2e-full.yml`	inspect	Verify workflow accepts `ref` input for targeting RC branch
`src/*/.ts` (regression fixes)	modify	Fix any regressions surfaced by E2E failures
`test/*/.e2e-spec.ts`	inspect	Verify local E2E tests pass against RC branch

Steps#

Run local E2E tests — Execute npm run test:e2e against the rc/multi-tenant branch to catch issues before the full external suite.
Trigger full E2E suite — Dispatch e2e-full.yml workflow via gh workflow run with ref=rc/multi-tenant to run the complete agent-core-e2e scenarios.
Collect and triage results — Wait for the E2E workflow to complete, fetch results via gh run view, classify each failure as regression (from refactor) or pre-existing (also fails on master).
Fix regressions — For any failure caused by the multi-tenant refactor, apply a fix in the RC branch, re-run affected tests to confirm.
Document pre-existing failures — List any pre-existing failures in the PR description with links to backlog issues if significant.
Confirm merge readiness — Once all E2E scenarios pass (or only pre-existing failures remain), confirm the RC branch is ready to merge to master.

Verification#

All local E2E tests (npm run test:e2e) pass with exit code 0
Full E2E workflow run completes green (or only pre-existing failures documented)
RC branch has no behavioral regressions compared to master

Risks#

E2E infrastructure flakiness — Self-hosted runner timeouts or CI infra issues may produce false negatives; re-trigger once before investigating code (per AGENTS.md convention).
No divergence detected — rc/multi-tenant and master are currently identical; if prior refactor PRs haven't been merged into RC yet, the validation is incomplete — verify branch state before running.

Summary#

File

Action

Description

.github/workflows/e2e-full.yml

inspect

Verify workflow accepts ref input for targeting RC branch

src/**/*.ts (regression fixes)

modify

Fix any regressions surfaced by E2E failures

test/**/*.e2e-spec.ts

inspect

Verify local E2E tests pass against RC branch

Steps#

Run local E2E tests — Execute npm run test:e2e against the rc/multi-tenant branch to catch issues before the full external suite.

Trigger full E2E suite — Dispatch e2e-full.yml workflow via gh workflow run with ref=rc/multi-tenant to run the complete agent-core-e2e scenarios.

Collect and triage results — Wait for the E2E workflow to complete, fetch results via gh run view, classify each failure as regression (from refactor) or pre-existing (also fails on master).

Fix regressions — For any failure caused by the multi-tenant refactor, apply a fix in the RC branch, re-run affected tests to confirm.

Document pre-existing failures — List any pre-existing failures in the PR description with links to backlog issues if significant.

Confirm merge readiness — Once all E2E scenarios pass (or only pre-existing failures remain), confirm the RC branch is ready to merge to master.

Risks#

E2E infrastructure flakiness — Self-hosted runner timeouts or CI infra issues may produce false negatives; re-trigger once before investigating code (per AGENTS.md convention).

No divergence detected — rc/multi-tenant and master are currently identical; if prior refactor PRs haven't been merged into RC yet, the validation is incomplete — verify branch state before running.