Vibecode Wabery

You are building a lean indie version of Wabery.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Wabery indie build

## Goal

Build the smallest trustworthy replacement for the core Wabery workflow for one developer or a tiny team.

## Scope

For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox

If those capabilities are essential, use Meta WhatsApp Cloud API instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements:

- Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy
  HTTPS on my always-on VPS.
- One Meta WhatsApp Business Account and phone number only. Keep the Cloud API
  access token, app secret, verify token, and phone number ID in .env.
- An authenticated REST API to send text, template, and media messages. Accept
  an Idempotency-Key and return both the local record and Meta message ID.
- Implement Meta webhook verification and verify POST signatures with the app
  secret. Persist each event before responding, deduplicate it, and normalize
  inbound messages, delivery statuses, and errors into PostgreSQL.
- Use pg-boss for outbound jobs with three retries and exponential backoff.
  Failed jobs go to a dead-letter view and can be replayed manually.
- Forward normalized events to one configured webhook, signed with HMAC. Store
  every attempt, response status, and next retry time.
- A small admin inbox behind one ADMIN_TOKEN: conversations, message status,
  failed jobs, webhook health, and a reply box. No public user accounts.
- Add health/readiness endpoints, structured logs, migrations, rate limits,
  daily database backups, and tests for signatures, deduplication, and retries.
- No telemetry beyond calls to Meta. Secrets must never be logged or committed.
- Out of scope: multi-tenant customer onboarding, Embedded Signup, billing,
  Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted
  functions, MCP, and production SLAs. Those require infrastructure and Meta
  review or approval beyond what code can provide.
- README: exact Meta app, WABA, number, webhook, and template setup; business
  verification caveats; deployment, backup restore, and secret rotation.

## Required capabilities

- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Wabery.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Wabery indie build

## Goal

Build the smallest trustworthy replacement for the core Wabery workflow for one developer or a tiny team.

## Scope

For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox

If those capabilities are essential, use Meta WhatsApp Cloud API instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements:

- Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy
  HTTPS on my always-on VPS.
- One Meta WhatsApp Business Account and phone number only. Keep the Cloud API
  access token, app secret, verify token, and phone number ID in .env.
- An authenticated REST API to send text, template, and media messages. Accept
  an Idempotency-Key and return both the local record and Meta message ID.
- Implement Meta webhook verification and verify POST signatures with the app
  secret. Persist each event before responding, deduplicate it, and normalize
  inbound messages, delivery statuses, and errors into PostgreSQL.
- Use pg-boss for outbound jobs with three retries and exponential backoff.
  Failed jobs go to a dead-letter view and can be replayed manually.
- Forward normalized events to one configured webhook, signed with HMAC. Store
  every attempt, response status, and next retry time.
- A small admin inbox behind one ADMIN_TOKEN: conversations, message status,
  failed jobs, webhook health, and a reply box. No public user accounts.
- Add health/readiness endpoints, structured logs, migrations, rate limits,
  daily database backups, and tests for signatures, deduplication, and retries.
- No telemetry beyond calls to Meta. Secrets must never be logged or committed.
- Out of scope: multi-tenant customer onboarding, Embedded Signup, billing,
  Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted
  functions, MCP, and production SLAs. Those require infrastructure and Meta
  review or approval beyond what code can provide.
- README: exact Meta app, WABA, number, webhook, and template setup; business
  verification caveats; deployment, backup restore, and secret rotation.

## Required capabilities

- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Wabery.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Wabery product brief

## Problem

The core loop (send, receive, verify webhooks, retry, inspect conversations) is one-shottable for a single business using Meta's WhatsApp Cloud API. What you cannot one-shot is the reason managed WhatsApp providers exist as products: production messaging infrastructure must stay reliable, secure, monitored, and compliant, while onboarding other businesses requires Meta business verification, app review, and approval for the relevant Tech Provider and Meta Business Partner capabilities. The honest DIY move is to build for your own verified WhatsApp Business Account and phone number; matching Wabery as a multi-tenant provider means operating that infrastructure and completing Meta's approval process.

## Product outcome

For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups

## Explicit non-goals for v1

- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements:

- Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy
  HTTPS on my always-on VPS.
- One Meta WhatsApp Business Account and phone number only. Keep the Cloud API
  access token, app secret, verify token, and phone number ID in .env.
- An authenticated REST API to send text, template, and media messages. Accept
  an Idempotency-Key and return both the local record and Meta message ID.
- Implement Meta webhook verification and verify POST signatures with the app
  secret. Persist each event before responding, deduplicate it, and normalize
  inbound messages, delivery statuses, and errors into PostgreSQL.
- Use pg-boss for outbound jobs with three retries and exponential backoff.
  Failed jobs go to a dead-letter view and can be replayed manually.
- Forward normalized events to one configured webhook, signed with HMAC. Store
  every attempt, response status, and next retry time.
- A small admin inbox behind one ADMIN_TOKEN: conversations, message status,
  failed jobs, webhook health, and a reply box. No public user accounts.
- Add health/readiness endpoints, structured logs, migrations, rate limits,
  daily database backups, and tests for signatures, deduplication, and retries.
- No telemetry beyond calls to Meta. Secrets must never be logged or committed.
- Out of scope: multi-tenant customer onboarding, Embedded Signup, billing,
  Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted
  functions, MCP, and production SLAs. Those require infrastructure and Meta
  review or approval beyond what code can provide.
- README: exact Meta app, WABA, number, webhook, and template setup; business
  verification caveats; deployment, backup restore, and secret rotation.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Wabery capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Wabery indie build

## Goal

Build the smallest trustworthy replacement for the core Wabery workflow for one developer or a tiny team.

## Scope

For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox

If those capabilities are essential, use Meta WhatsApp Cloud API instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements:

- Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy
  HTTPS on my always-on VPS.
- One Meta WhatsApp Business Account and phone number only. Keep the Cloud API
  access token, app secret, verify token, and phone number ID in .env.
- An authenticated REST API to send text, template, and media messages. Accept
  an Idempotency-Key and return both the local record and Meta message ID.
- Implement Meta webhook verification and verify POST signatures with the app
  secret. Persist each event before responding, deduplicate it, and normalize
  inbound messages, delivery statuses, and errors into PostgreSQL.
- Use pg-boss for outbound jobs with three retries and exponential backoff.
  Failed jobs go to a dead-letter view and can be replayed manually.
- Forward normalized events to one configured webhook, signed with HMAC. Store
  every attempt, response status, and next retry time.
- A small admin inbox behind one ADMIN_TOKEN: conversations, message status,
  failed jobs, webhook health, and a reply box. No public user accounts.
- Add health/readiness endpoints, structured logs, migrations, rate limits,
  daily database backups, and tests for signatures, deduplication, and retries.
- No telemetry beyond calls to Meta. Secrets must never be logged or committed.
- Out of scope: multi-tenant customer onboarding, Embedded Signup, billing,
  Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted
  functions, MCP, and production SLAs. Those require infrastructure and Meta
  review or approval beyond what code can provide.
- README: exact Meta app, WABA, number, webhook, and template setup; business
  verification caveats; deployment, backup restore, and secret rotation.

## Required capabilities

- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Wabery product brief

## Problem

The core loop (send, receive, verify webhooks, retry, inspect conversations) is one-shottable for a single business using Meta's WhatsApp Cloud API. What you cannot one-shot is the reason managed WhatsApp providers exist as products: production messaging infrastructure must stay reliable, secure, monitored, and compliant, while onboarding other businesses requires Meta business verification, app review, and approval for the relevant Tech Provider and Meta Business Partner capabilities. The honest DIY move is to build for your own verified WhatsApp Business Account and phone number; matching Wabery as a multi-tenant provider means operating that infrastructure and completing Meta's approval process.

## Product outcome

For one verified business and phone number, send WhatsApp messages, ingest and verify events, retry delivery, forward signed webhooks, and inspect conversations.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Meta Developer account and WhatsApp Cloud API access
- verified business, WhatsApp Business Account, and phone number
- always-on HTTPS server
- PostgreSQL
- monitoring and backups

## Explicit non-goals for v1

- Meta Business Partner status and approved Tech Provider onboarding path
- turnkey onboarding for multiple customer businesses and phone numbers
- managed queues, retries, monitoring, security, and production reliability
- WhatsApp Flows builder, encryption, and data-exchange hosting
- hosted functions, MCP tooling, and a production team inbox

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build me a single-business WhatsApp API gateway to replace Wabery for my own company. Requirements:

- Node 22 + TypeScript + Fastify + PostgreSQL; Docker Compose behind Caddy
  HTTPS on my always-on VPS.
- One Meta WhatsApp Business Account and phone number only. Keep the Cloud API
  access token, app secret, verify token, and phone number ID in .env.
- An authenticated REST API to send text, template, and media messages. Accept
  an Idempotency-Key and return both the local record and Meta message ID.
- Implement Meta webhook verification and verify POST signatures with the app
  secret. Persist each event before responding, deduplicate it, and normalize
  inbound messages, delivery statuses, and errors into PostgreSQL.
- Use pg-boss for outbound jobs with three retries and exponential backoff.
  Failed jobs go to a dead-letter view and can be replayed manually.
- Forward normalized events to one configured webhook, signed with HMAC. Store
  every attempt, response status, and next retry time.
- A small admin inbox behind one ADMIN_TOKEN: conversations, message status,
  failed jobs, webhook health, and a reply box. No public user accounts.
- Add health/readiness endpoints, structured logs, migrations, rate limits,
  daily database backups, and tests for signatures, deduplication, and retries.
- No telemetry beyond calls to Meta. Secrets must never be logged or committed.
- Out of scope: multi-tenant customer onboarding, Embedded Signup, billing,
  Meta Business Partner or Tech Provider status, WhatsApp Flows tooling, hosted
  functions, MCP, and production SLAs. Those require infrastructure and Meta
  review or approval beyond what code can provide.
- README: exact Meta app, WABA, number, webhook, and template setup; business
  verification caveats; deployment, backup restore, and secret rotation.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Wabery capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent