BINKY-WP-0003-T01: company email → OpenBao integration plan (AWQ-007 prep)

Vault path prod/binky/company-email/imap, secrets-engine catalog draft,
email-connect read-only IMAP wiring. Credential handover stays a single
Red-lane founder step.

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

AutopilotWorkQueue.md

@@ -51,18 +51,6 @@ lane: green
 pulls_from: [EcosystemMap.md cartography v0 caveat]
 ```
 
-```yaml
-id: AWQ-007
-title: "Onboard company email (bernd.worsch@binky-hedgehog.com) into Net Kingdom / OpenBao"
-lane: blue
-pulls_from: [audits/OK-Audit-v0-binky.md digital presence, identity-and-access capability]
-notes: "Store credentials in OpenBao; wire mailbox into agent event loop (email-connect
-  is the natural capability). Credential handover from founder is Red-lane — prepare
-  the vault path and integration plan first, then request the secret once. Goal:
-  real-world events (StB replies, Qonto notices) reach the control plane. Direct
-  dogfood of the net_kingdom + railiance pillars."
-```
-
 ```yaml
 id: AWQ-008
 title: "Design weekly paper-mail scan intake pipeline"
@@ -82,4 +70,8 @@ with a one-line outcome.
 
 ## Completed
 
-*(none yet)*
+- **AWQ-007** (2026-07-16, BINKY-WP-0003-T01): company-email → OpenBao
+  integration prepared — vault path, secrets-engine catalog draft, and
+  email-connect wiring in `integrations/company-email-openbao.md`. Remaining
+  steps (provider facts, Red-lane credential handover) tracked in that
+  document's checklist.