WS6 Collapsed-Schema Dev Environment
WS6 endgame produces — before the live schema rename has happened. This lets the
code plan (
internal/superpowers/plans/2026-06-22-ws6-endgame-collapse-code.md) bedeveloped and tested TDD-style against the post-collapse world.
The idea
public). The live cutover renamed theold substrate schema to
public (executed; procedure in git history). The collapsedcode carries no schema-qualified SQL and no per-connection search_path hooks — it
issues plain unqualified SQL against the connection default.
is executed; the current dev env uses
public directly (the standard DATABASE_URL).The legacy
public.* schema was retired with the cutover.The dev loop
1.
00_namespace_reset + 01_schema + 02_functions (the substrateinstall), the same load preamble used before the rename.
2.
DATABASE_URL — the connection default search_path pointedat the substrate (pre-rename):
3.
cargo make check, focused cargo nextest). Everysqlx::query! macro and runtime query resolves against the substrate, because itis the connection default — no schema qualification, no
SET LOCAL search_pathneeded.
Why this mirrors the runbook
now executed — the substrate lives in
public everywhere (local, CI, production).The current standard
DATABASE_URL (postgresql://temper:temper@localhost:5437/temper_development)is the dev default; no search_path option is needed.
pre-rename collapsed env ships identically post-rename.
Modified at 2026-08-19 17:59:49