test(federation): standalone regression canary — no breakage from M1 (FED-M1-09) #478
Reference in New Issue
Block a user
Delete Branch "feat/federation-m1-regression"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
FED-M1-09 — Standalone regression canary. Verifies the existing
standaloneandlocaltier behaviors did not break under M1's shared-path changes (packages/storage/,packages/db/test-utils, gateway tier-detector wiring, config schema additions).Approach
This is a verification milestone, not a code milestone. No new tests, no new code paths — re-ran the existing test suites that exercise the standalone/local paths against the current
main(with M1-01 → M1-08 all merged).Results
__tests__/(4 target files)pnpm test(top-level)Quality gates:
pnpm typecheckPASS ·pnpm lintPASS ·pnpm format:checkPASSCoverage notes
conversation-persistence.test.ts— standalone conversation write/read cyclecross-user-isolation.test.ts— cross-user data boundary enforcementresource-ownership.test.ts— resource ACL for standalone tiersession-hardening.test.ts— session token validationtier-detection.spec.ts— standalone/local tier path detection (along with federated)pglite.test.ts— PgliteAdapter CRUD/transaction/migratepostgres.spec.ts— PostgresAdapter unit testsConclusion
No regression in standalone or local tier behavior. Federation M1 changes are non-disruptive to the existing tier paths. M1 implementation can proceed to M1-10 (security review) and M1-11 (docs) before milestone close.
Test plan
Refs #460