Handoff: phase-2 foundation + payment-connect spec/roadmap

ROADMAP.md

@@ -9,6 +9,16 @@ Longer-term backlog. Near-term state lives in `AGENTS.md` → Current state.
 - Keysat-side dedup cache for Zaprite contacts (same buyer purchasing recurring twice can create duplicate Zaprite contacts).
 - Zaprite declined-card / expired-profile failure-body shapes are undocumented — harden `try_auto_charge_zaprite` once observed in production.
 
+## Agent compatibility & scoped API keys
+
+- **Agent-delegable payment-provider connect** (approved, not urgent — see
+  `plans/agent-payment-connect-scope.md`). Add an à-la-carte `payment_providers:write` scope
+  (never bundled into `merchant-onboard`), gated by a daemon-level **sandbox-mode flag** as the
+  outer gate (production daemons reject scoped connect entirely) with a **network gate** inner
+  defense (regtest/testnet/signet only, fail-closed to mainnet). BTCPay network is derived from
+  an on-chain address prefix (no `server/info` field exists). Feeds the doc-harness Path 2
+  (regtest buyer-pays). Ships after doc-harness Path 1.
+
 ## Packaging & distribution
 
 - Start9 Community Registry submission — criteria are unpublished; contact Start9 directly when ready.