DEC-2026-004 approved: Qonto provisioning scheduled for next office hour

- DecisionQueue: DEC-2026-004 → resolved (approved, Bernd, 2026-07-19);
  hub decision a2a9de69 resolved
- OH-2026-003 enriched with the Red-lane provisioning steps (API key +
  bao kv put per integrations/qonto-mcp.md) for the dashboard visit
- qonto-mcp.md checklist: approval done, provisioning next

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

DecisionQueue.md

@@ -44,34 +44,31 @@ fallback_if_no_response: "cron bridge keeps running; no degradation, but
   workstation-independence milestone stalls"
 ```
 
+## Resolved decisions
+
 ### DEC-2026-004 — Qonto MCP: create API key, provision OpenBao lane (read-only use)
 
 ```yaml
 id: DEC-2026-004
 title: "Provision Qonto API credentials for the self-hosted Qonto MCP server (read-only harness lane)"
 lane: red
-status: prepared
+status: resolved
+outcome: approved
+resolved_at: "2026-07-19"
+resolved_by: Bernd
 state_hub_decision_id: "a2a9de69-5bc1-434a-9a61-508ff3c12edf"
-created_at: "2026-07-19"
-needed_by: "soft — pairs naturally with OH-2026-003 (next Qonto dashboard visit)"
-attention_cost: "~10 min: approve design, create API key in Qonto /settings/integrations, one bao kv put"
-agent_recommendation: "approve — self-hosted qonto/qonto-mcp-server via
-  ops-warden/OpenBao (tenants/binky/qonto/api), NOT the hosted mcp.qonto.com
-  OAuth connector (violates no-native-integrations policy). Qonto API keys
-  are full-scope, so read-only is enforced by harness tool allow-list;
-  payments stay founder-only forever. While in the dashboard: note plan tier
-  + monthly cost and API prerequisites (OH-2026-003). Main accounting stays
-  DUO — this complements, does not replace, the StB lane."
+consequence: "Founder executes the Red-lane provisioning at the next office
+  hour, bundled with OH-2026-003's Qonto dashboard review: API key under
+  /settings/integrations + bao kv put tenants/binky/qonto/api (procedure in
+  integrations/qonto-mcp.md), plus plan tier/fee note for CostRunRate row 4.
+  Design as approved: self-hosted qonto/qonto-mcp-server, read-only via
+  harness tool allow-list, payments founder-only forever. BINKY-WP-0005-T05
+  (first read-only pull) unblocks after provision."
 evidence:
   - integrations/qonto-mcp.md
   - workplans/BINKY-WP-0005-qonto-mcp-integration.md
-options: [approve, reject, revise, defer]
-fallback_if_no_response: "no degradation — CostRunRate TBC rows stay manual;
-  cost-vs-usage answer for OH-2026-003 stays unquantified"
 ```
 
-## Resolved decisions
-
 ### DEC-2026-002 — Agent harness: one shared runtime repo
 
 ```yaml