Test: Increase pool size to trigger DECISION-DB-001

[decispher]

This PR changes the database pool size from 20 to 50 connections. Should trigger DECISION-DB-001 Critical alert and potentially block the PR.

[github-actions]

⚠️ Decision Context Alert

This PR modifies 1 file(s) that trigger 1 architectural decision(s).

🔴 Critical Decisions (1)

DECISION-DB-001: Database Connection Pool Configuration

File	src/database/connection\.js
Pattern	max:\\s\*\(?\!20\\b\)\\d\+
Type	Rule-based
Date	2024-03-15
Source	.decispher/decisions.md

We fixed the connection pool size at **20 connections** after extensive load testing. This decision was made because:

1. **Memory constraints**: Each...

📖 Read full context

We fixed the connection pool size at **20 connections** after extensive load testing. This decision was made because:

1. **Memory constraints**: Each connection uses ~5MB of memory
2. **Database limits**: Our PostgreSQL instance supports max 100 connections
3. **Performance testing**: Higher values caused connection leaks under sustained traffic (5K req/s)

**Alternatives rejected:**
- Dynamic pooling: Added latency spikes during scaling
- MongoDB: Billing requires ACID compliance

[!WARNING]
Do not modify pool size without load testing. Contact @senior-engineer before changes.

**Related:**
- [Load Test Results](https://internal\-docs/load\-tests\)
- [Architecture Decision Record](https://internal\-docs/adr\-001\)

---

---

🤖 Generated by Decision Guardian. Update decisions in your .decispher/ folder if needed.