chore/integrations-roadmap, HEAD 2ff18f82dc. No code changed, nothing pushed, no prod writes.roadmap.md (v8). It is v7 with the partner-API verification applied: every statement about a partner's API was checked against that partner's official documentation, the wrong ones are corrected, and the partner constraints v7 did not state are written into the target architecture and the items. The structure is unchanged: the integrations in use, the current architecture and infrastructure from code, the prod-log findings, the target, the work in five groups, one timeline and a short list of decisions. It carries no effort figures (user decision, 20/11). Earlier versions: roadmap-v2.md to roadmap-v5.1.md, roadmap-v6.md and roadmap-v7.md.| Step | Output |
|---|---|
| Read the two input documents (local copies) | tong-quan-integration-va-ha-tang.md, ke-hoach-phat-trien-integrations.md, brief.md |
| Prod log analysis, 18 days (bucket retention limit), read-only via the support service account | Roadmap section 4 (findings per integration, root-cause rollup in the user's five types) |
| Research: new apps, designs, existing integrations, infrastructure (with the per-integration map), architecture (today and target), potential apps | research-*.md (6 reports) |
| Draft v1, then one normal review | review-roadmap-v1.md |
| Cross-critique: 2 claude + 2 codex, two rounds | critique-*.md, critique-*-round2.md |
| Reconcile (union of verified findings) | reconcile-v3.md |
| Final verification on fable, every section against HEAD | verify-final-fable.md |
| Independent critique on gpt-6-astra | critique-astra.md |
| Scope pass: integrations only | scope-review-fable.md (v6) |
| Rewrite into a work-first document | roadmap-v7.md, rewrite-v7-report.md |
| Partner-API verification against official documentation, 32 claims in two reports (no partner API called) | verify-partner-api-A.md (marketing and messaging), verify-partner-api-B.md (Shopify, helpdesk, social, reviews, subscriptions, new apps) |
| Apply the verification to the roadmap | roadmap.md v8, apply-partner-verify-report.md (every change, with its source claim) |
Of the 32 claims checked, by the two reports' own summaries, 11 were confirmed, 18 were partly right, 1 was wrong as the roadmap used it and 2 could not be verified from documentation. No item was added or removed. The changes that alter a fix, not only its wording:
Retry-After rule does not exist. Only Klaviyo documents that header. Each adapter now owns its retry timing, and the worker never answers 429 or 503 to Cloud Tasks, because Cloud Tasks would slow the whole queue.deliveryId must be a UUID./v5 for a date-versioned API, sends no Retry-After header, and limits a brand to 400 requests a minute shared by all its integrations. The new adapters target the new version (decision 7).X-Shopify-Webhook-Id, and Joy dedupes on X-Shopify-Event-Id; a GraphQL throttle is HTTP 200 with a THROTTLED error; the existing bulk tag code replaces the whole tag array; Flow resends for 36 hours after a timeout, a 429 or a 5xx; the mandatory compliance webhooks must answer 401 to a bad HMAC.invalid_client on 8 of 58 accounts points at the accounts before it points at Joy's client; an Instagram token must be refreshed before its 60-day expiry; Loop's topic is return and its payload has no "customer chose exchange" field; Okendo's trigger fires before moderation; the health UI shows one banner at most.Every item states what to do, why, where in code, when it is done and what it depends on. Section 7 places the items in Wave 0 (20/11 → 01/12), Wave 1 (02/12 → 18/12), Wave 2 (21/12 → 18/01/2027) and Wave 3 (19/01 → 17/02/2027), and lists the seven safety gates (G-0 to G-6) that guard each production change.
external_id and Attentive externalEventId dedupe; the Omnisend /v5 retirement date; what Gorgias means by invalid_client; what Tapcart's customerSession carries. Each is a "Check during the spike" line on its item or a decision./v5 retires; the new adapters target the date-versioned API. Before the delivery-worker slice 1 is built.Decision 3 now carries its test (refresh one healthy Gorgias account and compare), and decision 5 now also covers Omnisend events and PushOwl pushes, with a replay-age limit per partner.