[thedogwiththedataonit]

What

GetBrew/brew-v2#2071 adds Brew events: triggers Brew starts itself. The first is a contact unsubscribing. GetBrew/typescript-sdk#66 exposes it as triggers.ensureBrewEvent, and this adds the command:

brew-cli automations triggers ensure-brew-event --scope domain --domain-id jd7f0c2a8w1x9m4n6p3q5r8s2t
brew-cli automations triggers ensure-brew-event --scope all

• Get or create: it returns the brand's trigger for that scope and prints the row with created. The same scope always prints the same row.
• Flags: --event defaults to contact.unsubscribed, the only Brew event so far. --idempotency-key makes a retry replay, since the route's x-brew-idempotency is replay.
• Usage errors (exit 2, no request sent): a missing or unknown --scope, --scope domain without --domain-id, and --domain-id with --scope all.
• Generated files: the bundled spec and generated types now carry provider: "brew_event", brewEvent, source: "brew_event" and TRIGGER_NOT_FIREABLE. The command reference is regenerated.

Why draft

This needs @brew.new/sdk ^12.2.0 (typescript-sdk#66), which is not on npm yet, so tsc and parity-sdk fail in CI against the published 12.1.0. Once 12.2.0 publishes:

1. Run bun add @brew.new/sdk@^12.2.0 and commit package.json + bun.lock.
2. Mark this ready.

Release order: brew-v2#2071 deployed → docs → SDK 12.2.0 → this CLI.

Spec vendoring

openapi/public-api-v1.yaml is this repo's main copy plus exactly brew-v2#2071's spec diff, byte-identical to typescript-sdk#66's. The consent-source integration change that brew-v2 main also has stays with #51.

Validation

Run locally with node_modules/@brew.new/sdk swapped for the SDK PR's 12.2.0 build. That swap is local only; package.json still says ^12.1.0.

• TDD: tests/commands/automations-brew-event-triggers.test.ts failed first and now passes. It covers the domain and all bodies, the idempotency key, four usage errors with no request, and 422 DOMAIN_PURPOSE_NOT_ALLOWED → exit 1.
• bun run tsc, bun run lint, bun run test (557 tests, including parity-sdk, parity-spec and idempotency-flags), bun run docs:commands:check and bun run build pass.
• node scripts/generate-types.mjs makes no changes to the committed types.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Confidence Score: 5/5

The changes since the previous review appear safe to merge, with no new blocking issue found.

Summary

Adds automations triggers ensure-brew-event for unsubscribe triggers.

• The CLI can get or create Brew’s contact-unsubscribe trigger.

No new actionable issues were found in the changes since the previous review. Tests were not run; dependencies are not installed locally.

_{Reviews (2) · Last reviewed commit: "Depend on @brew.new/sdk ^12.2.0 (trigger..." · Reviewed by Greptile}

[greptile-apps]

Comments Outside Diff

These findings could not be posted inline.

•  Backup spec gives conflicting examples openapi/public-api-v1.yaml.orig:38748 ▶

  openapi/public-api-v1.yaml.orig adds a second 67,829-line spec that already disagrees with the real spec: unsubscribe.reasons is optional here but required in openapi/public-api-v1.yaml. The type generator reads only the latter, so the backup adds misleading examples and unnecessary maintenance work. Remove the backup file.