rdev/internal/db/migrations/021_questions.sql
jordan a69eb7e587 feat(foundary): implement complete backend for conversational project design
Implements all 5 phases of Foundary Studio backend:

Phase 1: Chat Persistence (8 API endpoints)
- Conversations and messages with proper cascading deletes
- PostgreSQL schema with auto-update triggers
- Full CRUD operations with structured logging

Phase 2: Blueprint Entity (5 API endpoints)
- JSONB spec storage with GIN indexes
- Flexible structured data for project specifications
- Version-controlled blueprint management

Phase 3: Architect Service (3 API endpoints)
- Conversational AI orchestration with Claude
- Multi-turn dialogue with context building
- Blueprint spec extraction from conversations

Phase 4: Work Queue Integration
- Verified existing endpoint compatibility

Phase 5: Structured Questions (6 API endpoints)
- Four question types: text, choice, multichoice, yesno
- Answer validation with proper constraints
- Conversation-linked Q&A flow

Architecture:
- Textbook hexagonal architecture (domain → port → adapter → service → handler)
- Zero external dependencies in domain layer
- Consistent error handling with proper wrapping
- Auth scopes on all routes (projects:read, projects:execute)
- Structured logging with operation context and duration tracking
- NULL-safe DTO converters throughout

Database:
- 3 new migrations (019, 020, 021)
- UUIDs for all primary keys
- Proper foreign key constraints with ON DELETE CASCADE
- Optimized indexes including partial index for unanswered questions
- Auto-update triggers for timestamps

OpenAPI Documentation:
- Complete API documentation under 'Foundary' tag
- 22 new endpoints documented with examples
- Request/response schemas for all operations

Logging Improvements:
- Added operation field to all service logs
- Added duration_ms tracking for performance monitoring
- Log response_length instead of full response content
- Consistent use of logging field constants
- Execute-then-log pattern for delete operations

Files: 32 changed, 2800+ lines added
- 7 domain models
- 3 database migrations
- 3 port interfaces
- 3 postgres adapters
- 4 services (conversation, blueprint, question, architect)
- 4 handlers with DTOs
- OpenAPI documentation
- Integration in main.go

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2026-02-09 00:50:46 -07:00

30 lines
1.4 KiB
SQL

-- Questions table for structured architect questions
CREATE TABLE IF NOT EXISTS questions (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
conversation_id UUID REFERENCES conversations(id) ON DELETE CASCADE,
project_id TEXT NOT NULL,
question_type VARCHAR(20) NOT NULL, -- 'text', 'choice', 'multichoice', 'yesno'
text TEXT NOT NULL,
choices TEXT[], -- For choice/multichoice types
answer TEXT, -- User's text answer
answer_choices TEXT[], -- For multichoice answers
metadata JSONB DEFAULT '{}',
created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
answered_at TIMESTAMPTZ
);
-- Indexes
CREATE INDEX IF NOT EXISTS idx_questions_conversation
ON questions(conversation_id, created_at DESC);
CREATE INDEX IF NOT EXISTS idx_questions_project
ON questions(project_id, created_at DESC);
CREATE INDEX IF NOT EXISTS idx_questions_unanswered
ON questions(project_id, answered_at) WHERE answered_at IS NULL;
COMMENT ON TABLE questions IS 'Structured questions for architect service';
COMMENT ON COLUMN questions.question_type IS 'Question type: text, choice, multichoice, yesno';
COMMENT ON COLUMN questions.choices IS 'Available choices for choice/multichoice questions';
COMMENT ON COLUMN questions.answer_choices IS 'Selected choices for multichoice answers';