guide: Zapier

[walker-tx]

Closes #147

Factory draft of guides/zapier/ via draft-guide (pipeline agents).

Pipeline converged — ready for human review (agents never commit; this Action did).

Pipeline review (zapier)

Outcome: Reviewers passed after 1 round(s). Still skim the open questions below before merging.

Open questions (2)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• Zapier’s public documentation does not publish the exact labels or content of the browser sign-in and authorization prompts presented after DCR; the Setup Guide should direct the reader to complete the on-screen prompts without inventing labels.
• Zapier has not reconciled its direct-connect page with documentation that still requires creating a client-specific server. The direct DCR route is supported by live discovery metadata, but it was not completed end to end because that requires client registration and authorization with a Zapier account.

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json