BINKY-WP-0005: OH/T05 runbook and lane-scaffold notes for Qonto MCP

Prepare first-pull path after DEC-2026-004: copy-paste founder provision,
CCR apply, catalog promote, and CostRunRate update steps. T05 still waits
on Red-lane API key provision.

officehour/2026-08-command-day-runbook.md

@@ -17,8 +17,23 @@
 2. **OH-2026-002 — DUO Belegablage**: log in, assess receipt backlog size,
    photograph/upload missing receipts, confirm access continuity through the
    mandate transition.
-3. **OH-2026-003 — Qonto**: verify access works, pull current plan + monthly
-   fee, note cheaper plan options (decision itself can wait — data only).
+3. **OH-2026-003 — Qonto** (DEC-2026-004 approved — **also Red-lane provision**):
+   - Verify dashboard access works.
+   - Note plan tier + monthly fee → `finance/CostRunRate.md` row 4.
+   - Note cheaper plan options (plan *change* itself can wait — data only).
+   - **Provision API key for MCP (unblocks BINKY-WP-0005-T05):**
+     1. `/settings/integrations` → create API key; note organization ID.
+     2. Private terminal only (never chat/agent):
+        ```bash
+        umask 077
+        # key → /tmp/qonto.key, org id → /tmp/qonto.org
+        bao kv put tenants/binky/qonto/api \
+          QONTO_API_KEY=@/tmp/qonto.key \
+          QONTO_ORGANIZATION_ID=@/tmp/qonto.org
+        shred -u /tmp/qonto.key /tmp/qonto.org
+        ```
+     3. Full procedure: `integrations/qonto-mcp.md` (OH/T05 runbook).
+     4. After provision: agent runs first read-only pull + CostRunRate update.
 4. **OH-2026-004 — Handelsregister**: pull current HR excerpt
    (handelsregister.de), verify registered address and GF details, download
    articles of association if retrievable; file everything in `2binky/`.