The test suite lands

Why Care?

A week ago augment-it had zero automated tests — every agent rewrite rode on typechecks, builds, and the operator walking the surface. That debt came due as humain-vc's corpora quietly failed to load and creations went missing. This run pays it down: 43 tests across all ten MECE groups in the [[Corpora-Builder-Harmony-Test-Registry]], spanning two repos (augment-it + id-didi-sh) and two languages (TypeScript/Vitest + Elixir/ExUnit), covering every layer of the corpora-builder chain.

The point isn't the number. It's that the suite found real bugs on its own — one in code, two in live data — that no human had caught. That is the whole argument for tests in an agent-built codebase: they are the memory that runs.

The ten groups

Group	Area	Tests
A	Identity contract (id-didi-sh, ExUnit)	5
B	Session tenancy (the security gate)	5
C	Client transport resilience	4
D	Workspace registry / default_domain_type	3
E	Canonical CRUD (disposable SurrealDB)	7
F	Corpus file layer	3
G	Curator surface state (Svelte 5 runes)	5
H	Chat corpora slab	2
I	End-to-end integration (no browser)	4
J	Alignment audit (pure diff + runnable script)	5

Each test's name is the ✓-phrase you see turn green — the registry spec is the human-language index of all of them.

What the suite caught

A real reconnect bug (Group C). The headline property test — "no invoke silently vanishes" — failed on its first run, exactly as the registry predicted, and the failure was genuine: the client transport only scheduled a reconnect from the WebSocket close handler, but a refused connection (the exact case during a workspace-service restart) fires only error on Node's native WebSocket, never close. So the reconnect chain died on the first failed attempt and the surface wedged until a full page reload — a strong candidate mechanism behind the zombie-session and "invokes never reach the workspace" symptoms. Fixed in transport.ts; the test now guards it.

Two live data drifts (Group J). The alignment audit, on its first run against real read-only data, flagged two mismatches between the canonical domains rows and the on-disk corpus folders:

strategy:rural-income-boosts — in the DB for humain-vc but no folder on disk (the known mis-scope: created for reach-edu from the humain-vc workspace).
strategy:upward-mobility — a folder on reach-edu's disk with no DB row at all (a new orphan-folder finding).

Both are operator triage items. The audit is flag-don't-fix — it reported and touched nothing.

Discipline notes (the demonstration part)

No new runtime dependencies. Only test libraries (Vitest, @sveltejs/vite-plugin-svelte, jsdom). The ws package stays out: the transport tests run against a hand-rolled RFC-6455 server over node:http, and the tenancy tests exercise the logic directly instead of over a cookie-bearing socket. (Removing ws had also left the old prove-session-tenancy.mjs broken — Group B replaces it properly.)
Tests never touch shared state. Group E spins a throwaway in-memory SurrealDB per run (verified the installed v3 CLI interoperates with the v2 SDK — no upgrade needed); Groups D/F/B build temp dirs; Group J's unit test is a pure diff and its live script is read-only.
Two exported test seams (existingCorporaSlab, enforceTenant) and one timing seam on the transport — no behavior changes.

Group I: integration, not a browser

The end-to-end group landed as a no-browser integration test, after a deliberate call. A real browser walk needs a browser driver, and every driver (Playwright, Puppeteer) bundles ws internally — a test-only transitive dep, but this repo keeps ws out on principle. So rather than reintroduce it (even transitively, even test-only), Group I drives the real backend chain against disposable state over the platform-native WebSocket: a throwaway docker NATS, an in-memory SurrealDB, and the resolver + workspace-service (anonymous mode) + content-ingest, all stood up and torn down per run (e2e/harness.mjs). The four tests prove the session's tenancy at connect, corpora loading, type-scoping (thesis vs strategy), and — the lost-creations bug as a passing test — that a corpus created through the chain round-trips both stores (DB row + index.md) and survives a fresh re-list. The rendered pixels stay covered by the manual browser-drive rung (CLAUDE.md).

The test suite lands — all ten groups green, and the bugs it caught