- Add MIT LICENSE to zapier-mem0 (package.json declared MIT but shipped no
file; every peer commits one) + keywords/author/homepage for parity.
- Document the n8n and Zapier checks workflows in the AGENTS.md CI table.
- Title-case the ci-gate job display names (n8n Node, Zapier App) to match
the other integration jobs.
Match the repo's per-integration CI/CD convention (vercel-ai / pi-agent
pattern):
- n8n-nodes-mem0-checks.yml (lint + build + dist verify) and
n8n-nodes-mem0-cd.yml (npm publish --provenance via OIDC, dispatched by
the release router on tag n8n-nodes-mem0-v*).
- zapier-mem0-checks.yml (zapier validate) and zapier-mem0-cd.yml (manual
zapier push; requires ZAPIER_DEPLOY_KEY). Zapier deploys to Zapier's
platform, not npm, so it is not in the release router.
- Wire both packages into ci-gate.yml (path filters + call jobs + gate).
- Register the n8n tag prefix in release.yml and document it + the Zapier
manual-deploy in AGENTS.md.
- Skip the Zapier E2E suite when MEM0_API_KEY is absent so CI is green
offline (it still runs locally with a key).
Himanshu-Sangshetti