docs: 업데이트된 문서 내용 반영 및 Redis 통합 설명 추가

docs/architecture/overview.md

@@ -21,8 +21,8 @@ monorepo plan is prepared alongside it.
 ## Current Implementation Notes
 
 - `packages/infra` is live with Prisma/Postgres connectors used by game services.
-- `app/game-engine` implements an in-memory turn daemon with DB flush hooks.
-- `app/game-api` exposes tRPC endpoints for reserved turns, messages, and battle sims.
+- `app/game-engine` implements an in-memory turn daemon with DB flush hooks and Redis control transport.
+- `app/game-api` exposes tRPC endpoints for reserved turns, messages, and battle sims, communicating with the daemon via Redis.
 - Gateway/game frontends are still placeholders (not part of current runtime).
 
 ## Legacy Data Migration Policy

docs/architecture/rewrite-plan.md

@@ -19,6 +19,7 @@ Vue 3 frontends.
 
 - `packages/infra` is live and used by game-api/game-engine services.
 - `app/game-api` and `app/game-engine` have initial implementations (tRPC endpoints, turn daemon loop).
+- Redis transport for turn daemon control is implemented and wired.
 - Frontend apps remain placeholders while backend/runtime stabilizes.
 
 ## Runtime Stack (Planned)

docs/architecture/runtime.md

@@ -82,8 +82,8 @@ Gateway runs a lightweight cron loop (setInterval) that:
 ## Current Implementation Status
 
 - Turn daemon lifecycle + in-memory state live in `app/game-engine` with DB flush hooks.
-- Control queue is in-process only; Redis transport exists on API side but is not wired into the daemon.
-- API server already exposes turn-daemon commands (run/pause/resume/status) via tRPC.
+- Redis transport for daemon control is implemented and wired into the daemon.
+- API server already exposes turn-daemon commands (run/pause/resume/status) via tRPC, communicating via Redis Streams.
 - API server writes reserved turns and messages directly to the DB; daemon focuses on world state/logs.
 
 ## Turn Daemon and API Server Behavior (Outline)

docs/architecture/turn-daemon-lifecycle.md

@@ -12,9 +12,10 @@ from the API server.
 
 ## Current Implementation Status
 
-- The daemon loop handles scheduled runs plus in-process control queue commands
-  (run/pause/resume/shutdown). It does not drain API mutation requests between turns.
-- `getStatus` is supported by API transports but not yet handled by the daemon loop.
+- The daemon loop handles scheduled runs plus Redis-based control queue commands
+  (run/pause/resume/shutdown/getStatus).
+- API mutation requests (troopJoin, vacation, etc.) are drained and handled by the daemon loop between turns.
+- `getStatus` is fully supported and responds via Redis.
 - API server currently writes reserved turns and messages directly to the DB.
 
 ## Responsibilities