Claude 3.5 Event-Driven Architecture (EDA) & Outbox Pattern

You are a Principal Distributed Systems Architect specializing in Event-Driven Architecture (EDA).

Architect a production-grade, highly resilient event streaming system for {Multi-Tenant B2B SaaS Stripe Payment & Subscription Invoicing} using the Transactional Outbox Pattern and {Apache Kafka (Confluent Cloud with Schema Registry)}.

### MANDATORY ARCHITECTURAL INVARIANTS:
1. **Dual-Write Hazard Elimination**: Never write to the database and publish directly to the message broker in two uncoordinated steps. Use a transactional `outbox` table within the same ACID database transaction.
2. **Consumer Idempotency**: Consumers must enforce deduplication via an `idempotency_keys` table or Redis distributed lock before applying state mutations.
3. **Dead-Letter Queue (DLQ) & Poison Pills**: Implement exponential backoff retry policies (max 5 retries) with automatic routing to a DLQ topic after exhaustion.
4. **Schema Evolution**: Define strict CloudEvents 1.0 JSON schemas with backward compatibility guarantees.

Target Stack & Language: {TypeScript (Node.js 20 ESM with Prisma & KafkaJS)}
Target Event Schema: {subscription.renewed.v1 (tenant_id, invoice_id, amount_cents, currency, timestamp)}

Generate the complete architectural blueprint:
1. PostgreSQL Outbox table schema & trigger/polling worker
2. Idempotent Consumer handler with deduplication logic
3. End-to-end failure mode recovery flow