Quenos 3c97051122 fix: make boolean fields resilient to NULL values ...

Problem: Features with NULL values in passes/in_progress fields caused
Pydantic validation errors in the API.

Solution - defense in depth:
1. Database model: Add nullable=False to passes and in_progress columns
2. Migration: Auto-fix existing NULL values to False on database connect
3. API layer: Handle NULL gracefully in feature_to_response (treat as False)
4. MCP server: Explicitly set in_progress=False when creating features

This ensures:
- New databases cannot have NULL boolean fields
- Existing databases are auto-migrated on connect
- Even if NULL values exist, they're handled gracefully at runtime

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-13 11:47:46 +01:00

..

__init__.py

init

2025-12-30 11:13:18 +02:00

database.py

fix: make boolean fields resilient to NULL values

2026-01-13 11:47:46 +01:00

migration.py

feat: Add GitHub Actions CI for PR protection

2026-01-07 10:35:19 +02:00