memory: WT #383 (native Tier-3 reference_knowledge) cut as b167 — bridge retirement gates on operator's deploy

persistent-memory.md

@@ -82,6 +82,16 @@ Contract `docs/contracts/donut_voiced_interview.contract.md`. **NOT pushed** (op
 - **OWED (still):** P&P verification re-run to infra-ops on thread `01KYZX0JM1A1AF8ETMFV0AP7E9` (#382 fix deployed b166).
   Partial signal: Mimir DOES ground in DCC fiction wing now (bridge smoke), but the specific P&P-dismiss shape unrun.
   **Prior design detail → `persistent-memory.d/2026-08-01-donut-voiced-interview-build.md`.**
+- **🔜 KB-BRIDGE RETIREMENT IMMINENT — WT #383 (native Tier-3 `reference_knowledge`) CUT as v1.0.0b167**
+  (worldtree-dev, thread `01KZ0BZDCE1GKK724EK2R458PV`, 2026-08-02). NOT yet deployed — the push-to-main + :8081
+  promotion is the OPERATOR's call; worldtree-dev pings when live on :8081, then I retire same-day. Retirement =
+  ONE commit (INV-KB-1): delete `kb_bridge.py` + the one `server.py` call-site (`wt.stream_turn` memory_context
+  param stays inert). #383 gives every Tier-3 agent the `reference_knowledge` tool automatically (no define change),
+  #361 evidence-packet shape (note_id+path provenance, confidence bucket, answer null), server-side grounding rule
+  ("quote in voice, don't narrate metadata" — aligns with Donut's persona), fail-soft, wing-scoped to ["fiction"]
+  (DCC) deployment-owned. **This RESOLVES the KB-bridge disposition → the bridge is a provably short-lived interim;
+  ship-as-is is right, retire on the deploy ping.** Acked to worldtree-dev (`01KZ0C1KPR9DDQ37WRM1P793CP`).
+  FOOT-GUN (#381 interplay): freshly-ingested content needs the restart-after-ingest runbook to be Tier-3-recallable.
 
 **✅ SHIPPED + PUSHED since v0.22.0 (origin at `14bbc2b`):** the worldtree-sdk cutover (#20, **v0.22.0**, 7 slices,
 494 green — the big one) + **bifrost 1.1.5** (`3ef3a5e`, **v0.22.1**) + **worldtree-sdk 1.0.0→1.1.1→1.1.2**