fix: Resolve ADR-007 vs ADR-010 Temporal contradiction

Remove Temporal from the architecture in favor of the simpler
transitions + PostgreSQL + Celery approach. This aligns ADR-007
with ADR-010 based on user preference for simpler operations.

Key changes:
- ADR-007 now recommends transitions library instead of Temporal
- Added explicit "Why Not Temporal?" section explaining the trade-off
- Added "Reboot Survival" section documenting durability guarantees
- Updated architecture diagrams and component responsibilities
- Updated ARCHITECTURE.md summary matrix

The simpler approach is more appropriate for Syndarix's scale (10-50
concurrent agents) and uses existing PostgreSQL + Celery infrastructure.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

docs/architecture/ARCHITECTURE.md

@@ -90,7 +90,7 @@ Syndarix is an autonomous AI-powered software consulting platform that orchestra
 | ADR-004 | LLM Provider | LiteLLM with failover |
 | ADR-005 | Tech Stack | PragmaStack + extensions |
 | ADR-006 | Agent Orchestration | Type-Instance pattern |
-| ADR-007 | Framework Selection | Hybrid (LangGraph + custom) |
+| ADR-007 | Framework Selection | Hybrid (LangGraph + transitions + Celery) |
 | ADR-008 | Knowledge Base | pgvector for RAG |
 | ADR-009 | Agent Communication | Structured messages + Redis Streams |
 | ADR-010 | Workflows | transitions + PostgreSQL + Celery |