Bootstrap EDEN: Fase 0 (arquitetura) e Fase 1 (monorepo + infra)

Fase 0 — descoberta e arquitetura:
- Inventário do projeto, glossário de domínio, arquitetura com bounded
  contexts e topologia de containers, threat model inicial.
- 12 ADRs cobrindo modular monolith, topologia de containers (Postgres
  isolado + eden-core/parceiros/assinante em containers e portas
  distintos), auth/sessões, modelo de permissões, criptografia/segredos,
  contrato first-class, stock ledger, separação billing/finance/fiscal,
  outbox transacional, adapters SaperX e Focus NFe, e identidade
  compartilhada entre as 3 apps.
- 14 subagentes e 7 skills especializados por domínio em .claude/.
- Hooks de segurança (PreToolUse/PostToolUse/Stop) testados via pipe.

Fase 1 — plataforma (em andamento):
- Monorepo pnpm workspaces + Turborepo: apps/{api,worker,core-web,
  reseller-web,subscriber-web} + 9 packages compartilhados.
- apps/api: NestJS mínimo com /health/live e /health/ready (checando
  Postgres real via @eden/database).
- 3 frontends Vite + React + TypeScript + Tailwind, com o favicon
  oficial do EDEN.
- packages/database: migration baseline (node-pg-migrate) criando
  roles/role_permissions/applications/users/user_applications/sessions/
  audit_log — audit log append-only com hash-chain, testado ao vivo
  (UPDATE/DELETE bloqueados pelo trigger).
- compose.yaml implementando a topologia da ADR-0002, validada de ponta
  a ponta: os 6 containers sobem e ficam saudáveis com um único
  `docker compose up`.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

.claude/skills/eden-finance/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: eden-finance
+description: Billing, receivables, and reconciliation conventions for EDEN. Load when implementing billing runs, invoices, AR/AP, boleto/PIX, dunning, or bank reconciliation.
+---
+
+# EDEN finance skill
+
+## When to use
+- Designing a billing run or invoice consolidation flow → `references/billing.md`.
+- Modeling receivables/boleto/dunning → `references/receivables.md`.
+- Bank/OFX reconciliation → `references/reconciliation.md`.
+- Dunning rule engine specifics → `references/dunning.md`.
+
+## Rule
+Billing (what's owed) ≠ Finance/AR-AP (collecting) ≠ Fiscal (documents) — see ADR-0008. Never let one module's table double as another's; never let a consolidated invoice be silently edited.

.claude/skills/eden-finance/references/billing.md

@@ -0,0 +1,7 @@
+# Billing engine conventions (ADR-0008, Master Prompt §6.10)
+
+- Entities: `billing_accounts`, `billing_cycles`, `subscriptions/services`, `charge_components`, `usage_charges`, `invoices`, `invoice_items`, `invoice_adjustments`, `billing_runs`, `billing_run_logs`.
+- Supports: mensalidade, pró-rata, implantação, locação, SaaS por usuário, franquia, consumo de telefonia, serviços avulsos, descontos contratados, ajustes manuais auditados.
+- A billing run must be idempotent and safely re-runnable **before** final consolidation.
+- After consolidation, an invoice is never silently edited — use adjustment/credit-debit note or a controlled re-billing flow instead.
+- Test explicitly: billing run repeated does not duplicate an invoice (Master Prompt §15.3).

.claude/skills/eden-finance/references/dunning.md

@@ -0,0 +1,4 @@
+# Dunning / cobrança conventions (Master Prompt §6.9)
+
+- Configurable rules as data, not hardcoded logic: X days before due date, on due date, X days after, escalations, suspension/alert where policy allows, channels and templates.
+- n8n consumes dunning events without querying tables directly — publish via the transactional outbox (ADR-0009), event catalog owned by `eden-api-integrations`.

.claude/skills/eden-finance/references/receivables.md

@@ -0,0 +1,6 @@
+# Accounts receivable conventions (Master Prompt §6.9)
+
+- A receivable title carries: parcela, competência, emissão, vencimento, juros, multa, desconto, baixa (full/partial), estorno, negociação, status, origem, cliente, contrato, fatura, conta bancária/gateway.
+- Boleto: provider abstraction from day one — the bank/gateway must be swappable without rewriting the domain. Store nosso-id, provider, external id, linha digitável, código de barras, PDF/URL, PIX copia-e-cola/QR when the provider offers it, status, provider events, timestamps.
+- Webhooks from bank/gateway: idempotent and authenticated, always.
+- Test explicitly: a repeated webhook never duplicates a payment (Master Prompt §15.3).

.claude/skills/eden-finance/references/reconciliation.md

@@ -0,0 +1,6 @@
+# Reconciliation conventions (Master Prompt §6.9)
+
+- Import OFX/CSV and/or bank API.
+- Automatic matching by value/date/document; anything ambiguous goes to an exception queue for human review — never silently auto-match an ambiguous case.
+- Keep a reconciliation trail (what matched what, when, by whom/what process).
+- Same philosophy applies to SaperX × EDEN invoice reconciliation (see `eden-telecom` skill) — reuse the exception-queue pattern rather than inventing a second one.