docs: complete Dadbod pilot

docs/plans/workflow-system.md

@@ -55,7 +55,8 @@ restarted Kitty and closed the user's terminal session.
   native client with narrowly scoped certificate-verification exceptions; their
   exact example queries passed over TLS 1.3 in both environments. Direct test
   login and authenticated reads still return HTTP 200 for Yookr, rules, and
-  management. Kulala login and response chaining are confirmed in Neovim.
+  management. Kulala login and response chaining are confirmed in Neovim, and
+  both MariaDB examples produced results through Dadbod UI.
 - Herdr ran the issue 197 planning pilot in two predictable, non-overlapping
   dashboard worktrees. Codex produced frontend commit `20f9d0f`; Claude produced
   backend commit `bd965ea`. Short, long, done, fallback-agent, and genuinely
@@ -70,8 +71,8 @@ restarted Kitty and closed the user's terminal session.
 
 These gates do not block work on each other.
 
-- Visually confirm the MariaDB examples in Dadbod. Create a Marimo-to-HTML report
-  only when a concrete cross-system investigation gives it durable value.
+- Run one real cross-system investigation. Create a Marimo-to-HTML report only
+  when that investigation gives it durable value.
 - Keep Bruno, DBeaver, and PIM clients until their separate pilots decide them.
 - Route issue 197 to the actual account repositories before implementation;
   leave the two local dashboard planning branches available as evidence.
@@ -183,5 +184,4 @@ the fresh-shell GitHub read and restarted-Codex Context7 lookup must both work.
 
 ## Next step
 
-Confirm the two MariaDB examples inside Dadbod, then run one real cross-system
-investigation without mutating company GitHub.
+Run one real cross-system investigation without mutating company GitHub.