Milestone 0: import zappier billing, Verae middleware, and Zapier research

Compose-ready workspace: packages/zappier (rate card, portal, Stripe),
packages/verae-zapier-middleware (timestamp + NATS), packages/verae-zapier
(CLI app), vendor/zapier-platform, and research/zapier vendor corpus.

Gate 0 structure checks pass. Product code and research are not yet wired.

research/zapier/raw/docs/integrations/news/2026/version-promotion-guardrails.md

@@ -0,0 +1,43 @@
+> ## Documentation Index
+> Fetch the complete documentation index at: https://docs.zapier.com/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# New platform guardrails for safer integration versioning
+
+> The platform now checks for breaking changes during promotion and guides you toward the correct semantic version, helping protect your users from unexpected disruptions.
+
+*Effective: 2026-05-12*
+
+## What's new
+
+The platform now automatically checks for breaking changes when you [promote](/integrations/manage/promote) a new integration version. If breaking changes are found and the version doesn't increment the major number, promotion is paused with a clear explanation of what was detected and which version number to use instead.
+
+This helps you catch issues **before** they reach users — no more accidentally shipping a removal or auth change under a patch bump.
+
+## What gets checked
+
+When you promote, the platform compares the new version against the current public version at the **schema level** — looking at the structure of your triggers, actions, searches, and authentication. The following schema-level breaking changes are detected automatically:
+
+* **Removed triggers, actions, or searches** — a key present in the current public version is missing in the new version
+* **Authentication type change** — the auth type (e.g., `oauth2`, `apiKey`, `session`) differs between versions
+* **Trigger type change** — a trigger switched between polling and hook type
+* **Removed searchOrCreate keys** — a searchOrCreate present in the current version is missing
+* **Removed input field keys** — an input field key on an existing trigger/action was removed
+* **Optional input field made required without a default** — an existing optional field is now required but has no default value
+* **Authentication field changes** — removing an auth field, adding a new required auth field, or changing an auth field's type
+* **Input field type changes** — changing the type of an input field (e.g., `string` → `list`)
+* **Incompatible JSON field schema changes** — backward-incompatible changes to `json`-type input field schemas
+
+If any of these are detected, you'll see a message explaining the specific changes found and the minimum major version required.
+
+<Note>
+  These checks cover **schema-level** changes only. Some breaking changes happen outside the schema — for example, removing or renaming output field keys, changing the behavior of a perform function, or altering response structures. These are still your responsibility to catch. Review the full [versioning matrix](/integrations/manage/planning-changes) before promoting.
+</Note>
+
+## What this means for you
+
+* **If you're already following semver**, nothing changes. You're good.
+* **If a promotion is paused**, read the message — it tells you exactly which changes triggered the check and what version number to use. Bump the major version and promote again.
+* **If you need to phase out a trigger, action, or search without a major bump**, [hide it](/integrations/manage/versions#what-counts-as-a-breaking-change) instead of removing it. Hidden items continue to work for existing Zap workflows but are no longer available to new users.
+
+For the full list of what gets detected and how to choose the right version number, see [Version numbering](/integrations/manage/versions#version-numbering).