fix: correct API module paths from byte_bot to byte_api

Updated all references to use the correct microservices module path:
- .env.example: LITESTAR_APP=byte_api.app:create_app
- services/api/Dockerfile: uvicorn byte_api.app:create_app --factory
- services/api/README.md: documentation references

This fixes the "Module not found" error when starting the API service.
Note: .env also needs manual update (not tracked in git).

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

Co-Authored-By: Claude <[email protected]>

Author: JacobCoffee

.env.example

@@ -8,7 +8,7 @@ DISCORD_DEV_USER_ID=IDOfYourDevUser
 
 # --- Project Settings
 # No Prefix for Project settings
-LITESTAR_APP=byte_bot.app:create_app
+LITESTAR_APP=byte_api.app:create_app
 WEB_URL=https://byte-bot.app
 SECRET_KEY=ThisIsNotAProductionToken
 ENVIRONMENT=dev

services/api/Dockerfile

@@ -80,4 +80,4 @@ HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
 
 # Run database migrations and start server
 # Note: In production, consider running migrations separately in an init container
-CMD ["sh", "-c", "alembic upgrade head && uvicorn byte_api.app:app --host 0.0.0.0 --port 8000 --workers 2"]
+CMD ["sh", "-c", "alembic upgrade head && uvicorn byte_api.app:create_app --factory --host 0.0.0.0 --port 8000 --workers 2"]

services/api/README.md

@@ -191,9 +191,9 @@ services/api/
 This service is part of Phase 1 (API Layer Extraction) of the microservices migration. It consolidates functionality
 from:
 
-- `byte_bot/app.py` - Litestar app factory
-- `byte_bot/server/` - Web service logic
-- `byte_bot/server/domain/` - Business domains
+- `byte_api/app.py` - Litestar app factory
+- `byte_api/domain/` - Business domains
+- `byte_api/lib/` - Infrastructure code (database, settings, etc.)
 
 The Discord bot will communicate with this service via HTTP rather than direct database access.