mail triage 2026-07-18 (founder) + AWQ-010 Qonto MCP integration

- E-mail triage log section added: jamesandersons spam resolved by
  founder; IHK Sommerfest invitation (August, founder calendar call);
  Qonto MCP mailing -> actionable
- AWQ-010: Qonto MCP integration prep (read scopes first, ops-warden/
  OpenBao credential lane, no native integrations; complements DUO =
  DATEV Unternehmen Online as main accounting, does not replace it)
- OH-2026-003 enriched: MCP integration is an argument FOR keeping
  Qonto; check API/plan prerequisites while in the dashboard

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

AutopilotWorkQueue.md

@@ -5,6 +5,26 @@
 
 ## Queue
 
+```yaml
+id: AWQ-010
+title: "Qonto MCP integration: connect the company bank account to our agent infrastructure"
+lane: green
+pulls_from: [mailmeta/mail-log.md 2026-07-18, OH-2026-003]
+notes: "Founder direction 2026-07-18: 'integrations like this should help
+  with the automated company approach a lot' — arrange soon. Prepare the
+  integration package: (a) Qonto MCP capabilities/docs review (read scopes
+  first; payments are Red-lane forever); (b) credential lane via ops-warden/
+  OpenBao (tenants/binky/qonto — same custody pattern as company-email;
+  provisioning founder Red lane; NO claude.ai native integrations, harness/
+  MCP lane only); (c) consumer design: rhythm sessions + finance/
+  CostRunRate.md feeds (real balance/transactions replace manual Qonto
+  pulls, part of OH-2026-003's cost-vs-usage answer — the MCP is an
+  argument FOR keeping Qonto); (d) note main accounting stays DATEV
+  Unternehmen Online (DUO) — Qonto MCP complements, does not replace,
+  the DUO/StB lane. Output: integrations/qonto-mcp.md design + DecisionQueue
+  entry for the Red-lane provisioning."
+```
+
 ```yaml
 id: AWQ-002
 title: "Map self-billed Eigenentwicklung invoices to ecosystem capabilities as IP evidence"