Document safe Zapier editor workflows

[harrisboatworks]

Summary

• document stable Zapier editor routes and selectors
• explain how to compare published and unpublished Zap definitions safely
• distinguish trigger-only sample refreshes from action tests that can send messages or mutate data

Why

Zapier can retain one unpublished draft containing unrelated work, while the editor's bootstrap data may become stale after autosave. These notes help agents preserve existing drafts, confirm saved state from the server, and inspect triggers without running downstream actions.

Impact

Documentation only. No runtime behavior changes.

Validation

• git diff --check
• confirmed the document contains no task-specific IDs, addresses, credentials, or customer data

---

Summary by cubic

Add a guide to the Zapier editor documenting stable routes/selectors and safe workflows to compare published vs draft and test triggers without running actions. Also covers server readbacks for fresh state, reliable edits to contenteditable fields, and tips for Zap history; documentation only, no runtime changes.

^{Written for commit 4be1d83. Summary will update on new commits.}

[Kastan97]

Ollie (CTO) Review: APPROVED ✅

What this does: Documents safe Zapier editor workflows — stable routes, selectors, comparing published vs draft Zaps, and testing triggers without running downstream actions. 68 lines of documentation.

Assessment: Clean, focused documentation. No code changes. The "test triggers without firing actions" guidance prevents a real class of agent errors. No credentials or customer data included.

Good to merge.