From d3d6ae0b3332bd4cb5da465cff913a89fa3bed11 Mon Sep 17 00:00:00 2001 From: Jelle Spreeuwenberg Date: Sun, 6 Sep 2026 18:05:40 +0200 Subject: [PATCH] docs: complete authenticated API pilot --- docs/plans/credential-consolidation.md | 6 +++--- docs/plans/workflow-system.md | 29 ++++++++++++-------------- docs/workflow-discovery.md | 17 +++++++-------- 3 files changed, 24 insertions(+), 28 deletions(-) diff --git a/docs/plans/credential-consolidation.md b/docs/plans/credential-consolidation.md index e67ddcd..b718b7a 100644 --- a/docs/plans/credential-consolidation.md +++ b/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 and both MongoDB connections work. The -changed workbench `.envrc` still needs explicit re-authorization before the user -visually confirms the MariaDB fix. +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. ## Excluded from migration diff --git a/docs/plans/workflow-system.md b/docs/plans/workflow-system.md index 5a26b42..a296df5 100644 --- a/docs/plans/workflow-system.md +++ b/docs/plans/workflow-system.md @@ -55,7 +55,7 @@ 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. + management. Kulala login and response chaining are confirmed in Neovim. - 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 @@ -67,21 +67,19 @@ restarted Kitty and closed the user's terminal session. These gates do not block work on each other. -- Explicitly authorize the changed workbench `.envrc`, restart Neovim, and - visually confirm the MariaDB examples and Kulala response chaining. Create a - Marimo-to-HTML report only when a concrete cross-system investigation gives it - durable value. +- Visually confirm the MariaDB examples in Dadbod. Create a Marimo-to-HTML report + only when a concrete cross-system 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. -The remaining Herdr observations are that detach and reattach preserve output, -each completed event produces exactly one notification, and both worktree -`.envrc` files receive explicit authorization. Short, long, approval-blocked, -fallback-agent, predictable-path, non-overlapping-write, dirty-removal, and -branch-retention behavior already passed. If a remaining component fails, fall -back independently to native agent sessions and Codex TUI notifications or -native `git worktree add/list/remove`; do not add a wrapper or Worktrunk yet. +The remaining Herdr observations are that detach and reattach preserve output +and each completed event produces exactly one notification. Short, long, +approval-blocked, fallback-agent, predictable-path, non-overlapping-write, +dirty-removal, and branch-retention behavior already passed. If a remaining +component fails, fall back independently to native agent sessions and Codex TUI +notifications or native `git worktree add/list/remove`; do not add a wrapper or +Worktrunk yet. ## Deferred pilots @@ -186,7 +184,6 @@ the fresh-shell GitHub read and restarted-Codex Context7 lookup must both work. ## Next step -Activate the pending Neovim JavaScript-query mapping, authorize the changed -workbench and pilot-worktree `.envrc` files, and confirm the two MariaDB examples -inside Dadbod. Then confirm Herdr notifications and detach/reattach persistence, -and run one real cross-system investigation without mutating company GitHub. +Confirm the two MariaDB examples inside Dadbod. Then confirm Herdr notifications +and detach/reattach persistence, and run one real cross-system investigation +without mutating company GitHub. diff --git a/docs/workflow-discovery.md b/docs/workflow-discovery.md index 1674286..2ed9ce3 100644 --- a/docs/workflow-discovery.md +++ b/docs/workflow-discovery.md @@ -162,19 +162,18 @@ and build configurations, then provide an activation command. ## Remaining pilots -- Authorize the changed workbench `.envrc` and visually confirm its two MariaDB - examples. The four SOPS-derived Dadbod connections, both MongoDB connections, - and all four read-only example-query runs already passed. Add a Marimo report - only for a real cross-system investigation. +- 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. - 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 generated test document remains deployed. -- Finish only the notification, detach/reattach, and per-worktree direnv - observations for the Herdr pilot. Its Codex/Claude fallback, attention states, - local branches, parallel non-overlapping plans, and dirty-removal guard passed - with issue 197; the plans show that implementation belongs outside the - dashboard repository. +- Finish only the notification and detach/reattach observations for the Herdr + pilot. Its Codex/Claude fallback, attention states, local branches, parallel + non-overlapping plans, and dirty-removal guard passed with issue 197; the plans + show that implementation belongs outside the dashboard repository. - Keep Bruno, DBeaver, and existing PIM clients until their independent gates are resolved.