Merge branch 'yath-db-schema' into 2.0

Author: exodist

AI_DOCS/2026-05-07-schema-redesign.md

@@ -522,9 +522,13 @@ Reproduced from `SCHEMA_REDESIGN_DECISIONS.md`:
 - **`events.jsonl.zst` still stored as artifact bytes.** No `events`
   table; events stay in `artifacts.payload` as zstd-compressed
   JSONL. Out of scope for this redesign.
-- **App::Yath2DB DBIC sync** — the dist isn't written yet; when it
-  is, it'll consume this schema directly. No external-dist coupling
-  in this redesign.
+- **App::Yath2::DB DBIC consumption** — `App::Yath2::DB::DBIC` ships
+  in this dist (see `AI_DOCS/2026-05-08-yath-db-namespace.md`) and
+  consumes this schema via hand-written Result classes under
+  `App::Yath2::DB::DBIC::Result::*`. Bootstrap is still
+  `share/schema/$flavor.sql`-driven; DBIC's `deploy()` is never
+  called. External `App::Yath2::UI` would consume the same DBIC
+  schema if/when it is written.
 
 ## Pre-existing follow-up surfaced
 

AI_DOCS/2026-05-08-yath-db-namespace.md

@@ -1,3 +1,12 @@
+**Superseded by `AI_DOCS/2026-05-08-yath-db-rebuild.md`.** Decisions in
+this document are historical; the architecture they describe was
+replaced by the DB rebuild (App::Yath2::DB::Internal* deleted in favor
+of App::Yath2::DB + App::Yath2::DB::SQL + App::Yath2::DB::DBIC). See
+the rebuild plan for current state.
+
+----
+(original content below)
+
 # Yath DB Namespace — Design Spec
 
 **Status:** approved 2026-05-08