FED-M1-09 — Standalone regression canary. Verifies the existing standalone and local tier 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).
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
CI green
No further validation needed — this PR is the validation record itself
Formatting drift in docs/scratchpads/mvp-20260312.md caused format:check
to fail; applied pnpm format to bring it into compliance.
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
M1-09 standalone regression canary ran clean against current main:
- 4 gateway __tests__ files (148 tests)
- Full gateway suite (351 tests, 4 FEDERATED_INTEGRATION-gated skipped)
- All 5 storage unit specs (85 tests, 1 integration skipped)
- Top-level pnpm test all green
No standalone regression. Federation M1 implementation does not break
existing standalone or local tier behavior.
Refs #460
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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