override would disable the other required proposals.
Use `resolveGitHubSessionUri` to validate and derive the deployment base; never
parse an account's display label or infer its host from
review instructions
- During code review, flag any change that newly disables, skips, or omits deploy-mode tests or assertions, including `skipDeployment: true` and `isNextDeploy` conditionals. Only allow this when
workflow path unless a maintainer explicitly expands the allowlist. `comment.atom.yml`, `autofix.atom.yml`, `report.atom.yml`, release workflows, deployment workflows, and any workflow with trusted secrets or write permissions must stay outside fork auto
generated-artifact delivery](CONTRIBUTING.md#generated-artifacts-in-pull-requests).
Merge, auto-merge, and deployment require explicit authorization in the current conversation. Do not request reviewers, invoke review automation, or send
sibling with its own package boundary; check the package docs before assuming a publication, deployment, or local-install surface.
## ROLE MAP
| Role | Count | Packages |
|------|-------|----------|
| **Platform launcher packages
delete.
- **`zapier-mem0/`** is a Zapier Platform CLI app: add, search, get, delete. It deploys to Zapier, not npm, so it is **not** in the release router. Deploy it with
about pages, Go module paths, package names, import paths, Docker image names, CI/CD references, deployment configs, comments, documentation, and changelog entries.
If asked to remove, rename, or replace these protected
version and intended dist-tag agree; CI, CodeQL, and the release-only Pages deployment for the exact released commit are green; live catalog and legacy-bridge surfaces match; and every
public git history.
## Pull Requests
Frontend (`static/`) and backend (`src/`, `tests/`) are **not atomically deployed**. A CI check enforces this.
- If your changes touch both frontend and backend, split them
exact tag and updates `distribution/latest.json`. The resulting master commit triggers the private website deployment.
Normal feature and fix work must not edit `docs/next/CHANGELOG.md`; this keeps long-lived branches from conflicting
data manipulation here.
- **Data migrations** (`data-migrations/`): any data manipulation that must run on deployment goes here, never in schema migrations.
- Data migrations MUST log progress — `{MIGRATION_NAME}: [START] {action
products/ /` — owned by one product
- `tools/` — dev/CI tooling, not shipped at runtime
- `services/` — independently deployed
- `packages/` — a clean, published-style leaf with **no back-edges into app code** (see `packages/quill
will be replaced/supplemented by extracted SVGs)
- **Styling:** Tailwind CSS v4 with oklch design tokens
- **Deployment:** Vercel
## Commands
- `npm run dev` — Start dev server
- `npm run build` — Production build
modal is progressively disclosed.** An unset global config
starts on the Buzz Agent-first deployment fallback and carries that visible
harness into the next saved edit. The `progressive-defaults` disclosure
produce a Vercel cost/performance report.
Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.
## Requirements
- Node.js 20+
- Vercel
Core behavior
- Prefer the docs MCP tools for factual questions about APIs, features, configuration, deployment, MCP, memory, tools, middleware, LangGraph, and Deep Agents.
- Search first, then open the most relevant