integrations, with status 

@invitation/tracker captures ?ref=CODE and supports no-credit test conversions. The hosted global bundle still depends on the API deployment carrying its built artifact.

@invitation/node covers campaigns, customer referrers, conversions, webhooks, and public reads. Source and release metadata exist; verify registry publication before installing outside this workspace.

Campaign and publisher tools share the API procedures. The target must enable FEATURE_AGENT_API; tools/list is the authority for the deployed tool set.

The native reference covers links, partners, commissions, leads, and sales. The API-served OpenAPI 3.1 document derives its server URL from the deployment that answered.

stripe is a supported validation value, not proof that a merchant metadata or webhook path is installed. Require one staging conversion.

The validation vocabulary reserves shopify, but the merchant app and orders/paid path are not a runnable integration.

Campaign delivery uses HMAC-SHA256 over the exact raw body. Verify the campaign secret, receiver, delivery log, and redelivery against staging.

A deterministic local e2e-program fixture exists, but it is not a public sandbox. Add a live demo only after its public URL, click, and no-credit conversion are captured.