Write Instagram documentation from released evidence

Documentation cannot promote a planned adapter to live

Well-formed endpoint tables and code examples can look authoritative even when no provider path exists. DewEngine's Instagram surface remains unimplemented and unapproved. The documentation system must not hide scraping, evasion, or anti-detection behind neutral API language. Every published operation needs an authorized account product, schema, conformance record, known limitations, and release state. Research pages should remain clearly separated from generated reference material.

Begin with account eligibility and method status

Reference documentation should first explain which Instagram product is connected, which customer purpose was approved, which accounts qualify, and what status each resource, method, and event has. A reader needs to see unavailable and decision-gated behavior, not only successful examples. Capability discovery in the runtime, OpenAPI extensions, console controls, SDK methods, and public tables should derive from one versioned manifest so they cannot drift independently.

Document the grant without exposing its secret

The auth chapter should cover short-lived intents, redirect allowlists, state protection, eligible account selection, scopes, consent, callback results, identity-safe reconnect, grant health, and disconnect. Customer applications store only a DewEngine account ID. Screenshots and troubleshooting examples must use synthetic values and should never invite readers to paste provider tokens into tickets, environment snippets committed to source, or general support email.

Describe native extensions, absence, and partial state

Each resource page needs stable fields, provider-specific extensions, identifier scope, timestamps, pagination, freshness, null and missing semantics, size limits, and permission requirements. Examples should show unsupported capability and partial synchronization, not only ideal objects. Write methods need idempotency and command-state documentation, while events need authority, ordering, duplicate, and replay expectations. A generated schema is the starting point, not the entire developer explanation.

Teach developers what to do when truth is uncertain

A useful error catalog distinguishes customer input, missing permission, account health, policy block, provider throttle, transient outage, non-retryable rejection, and indeterminate dispatch. It explains which reads are safe to retry and why writes require idempotency and reconciliation. Operational docs should cover request IDs, webhook verification, dead-letter replay, rate feedback, reconnect, deletion, and support-safe diagnostics without exposing private message content or grant material.

Version reference text with the adapter evidence

CI should compare documentation, OpenAPI, SDKs, console, and marketing claims against the released connector manifest. Examples run against deterministic mocks and, within the provider conformance suite, consented accounts. Permission or policy changes trigger review, changelog entries, migration guidance, and capability fallback where required. Until an Instagram adapter passes those gates, this route remains original educational copy and must not display working credentials or fabricated responses.

• Date every provider-specific fact and link it to the governing release record
• Show one failure and one unsupported example beside each successful workflow