docs: complete Dadbod pilot

docs/plans/credential-consolidation.md

@@ -81,9 +81,9 @@ indefinitely.
   and listed its six root entries. No object content was downloaded and no
   rclone configuration was persisted.
 
-Dadbod's four display names are active, both MongoDB connections work, and the
-workbench environment now supplies successful Kulala response chaining. The two
-MariaDB examples still need visual confirmation in Dadbod.
+Dadbod's four display names are active, both MongoDB connections work, both
+MariaDB examples produce results through Dadbod UI, and the workbench environment
+supplies successful Kulala response chaining.
 
 ## Excluded from migration
 

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.

docs/workflow-discovery.md

@@ -162,10 +162,10 @@ and build configurations, then provide an activation command.
 
 ## Remaining pilots
 
-- Visually confirm the two MariaDB examples in Dadbod. The workbench environment,
-  four SOPS-derived Dadbod connections, both MongoDB connections, all four
-  read-only example-query runs, and Kulala response chaining already passed. Add
-  a Marimo report only for a real cross-system investigation.
+- Run one real cross-system investigation. The workbench environment, all four
+  SOPS-derived Dadbod connections, read-only example-query runs, and Kulala
+  response chaining have passed. Add a Marimo report only when the investigation
+  gives it durable value.
 - Add another ephemeral read-only rclone remote only when credentials for a new
   Leafcloud project become available. Irristaud listing has passed; do not upload.
 - Use the reviewed local Yookr OpenAPI contract while the accepted malformed