Create API route structure with empty handlers

[torresmateo]

Summary

Set up the foundational API route structure with placeholder handlers for all core endpoints. Created 9 route modules following Elysia framework patterns with type-safe request/response schemas.

Implementation

• Created /apps/server/src/routes/ directory with 9 route modules:
  • workspaces.ts - Workspace management (list, get, create, update)
  • sources.ts - Source data operations (list, get, create, delete)
  • personas.ts - Persona management (CRUD operations)
  • projects.ts - Project management (CRUD operations)
  • candidates.ts - Candidate content operations (CRUD operations)
  • publishing.ts - Publishing workflow (status, publish, schedule, history)
  • social-channels.ts - Social channel integrations (CRUD + test)
  • analytics.ts - Analytics data (overview, posts, channels, sync)
  • upload.ts - File uploads (image, video, document, delete)
• Registered all routes in apps/server/src/index.ts using Elysia's .use() pattern
• Each route includes:
  • Type-safe request/response stubs using Elysia's t schema validator
  • JSDoc comments describing purpose
  • Consistent response format: { success, data, message }
  • RESTful endpoint patterns

Testing

All route files are created with proper TypeScript syntax and Elysia patterns:

• ✅ All 9 route files created (526 total lines)
• ✅ Routes properly exported as Elysia plugins
• ✅ Type-safe schemas defined for request bodies
• ✅ Routes successfully registered in main server
• ✅ Consistent naming conventions (kebab-case paths, camelCase exports)

Review Checklist

• All route files created
• Basic Elysia route structure
• Routes registered in main server
• Type-safe request/response stubs
• Consistent naming conventions

Closes https://linear.app/megaforce/issue/MEG-12/create-api-route-structure-with-empty-handlers

🤖 Generated with Claude Code