docs(05-04): complete split deployment artifacts plan

- add phase summary for split deployment artifacts
- update state with phase 05 completion context

.planning/STATE.md

@@ -2,8 +2,8 @@
 gsd_state_version: 1.0
 milestone: v1.0
 milestone_name: — Production-ready surfaces
-status: Executing Phase 05
-last_updated: "2026-04-27T22:15:58Z"
+status: Phase 05 Complete
+last_updated: "2026-04-27T22:17:10.233Z"
 progress:
   total_phases: 6
   completed_phases: 3
@@ -18,11 +18,11 @@ progress:
 See: .planning/PROJECT.md (updated 2026-04-02)
 
 **Core value:** Пользователь ведёт диалог с Lambda через любой мессенджер без изменения ядра
-**Current focus:** Phase 05 — mvp-deployment
+**Current focus:** Phase 05 complete — MVP deployment handoff is ready
 
 ## Current Phase
 
-**Phase 05** in progress: MVP deployment hardening
+**Phase 05** complete: MVP deployment hardening
 
 Plan `05-01` is complete. Matrix startup now reconciles managed Space rooms from synced topology before live traffic, restoring local metadata and deterministic legacy `platform_chat_id` bindings on restart.
 
@@ -38,6 +38,20 @@ Plan `05-02` is complete. Matrix room-local context commands now rely on repaire
 
 Verified with `MATRIX_AGENT_REGISTRY_PATH='' MATRIX_PLATFORM_BACKEND='' UV_CACHE_DIR=/tmp/uv-cache-surfaces uv run pytest tests/adapter/matrix/test_context_commands.py tests/adapter/matrix/test_routed_platform.py tests/adapter/matrix/test_dispatcher.py -v`.
 
+Plan `05-03` is complete. Shared-volume attachment handling now preserves relative agent paths while tolerating both `/workspace` and `/agents` absolute prefixes during normalization and Matrix file rendering.
+
+- `7a12a71` — failing regressions for shared-volume path normalization and room-safe attachment handling
+- `5eddf16` — `/agents` deployment path hardening for Matrix files and routed platform attachments
+
+Verified with `uv run pytest tests/adapter/matrix/test_files.py tests/platform/test_real.py tests/adapter/matrix/test_send_outgoing.py -v`.
+
+Plan `05-04` is complete. Production handoff now uses `docker-compose.prod.yml` for a bot-only runtime, while internal end-to-end verification uses `docker-compose.fullstack.yml` with shared `/agents` volume guidance and health-gated startup.
+
+- `df6d8bf` — split prod and full-stack compose artifacts with the shared `/agents` contract
+- `22a3a2b` — operator and deployment docs aligned to the split compose artifacts
+
+Verified with `docker compose -f docker-compose.prod.yml config`, `docker compose -f docker-compose.fullstack.yml config`, and docs grep checks for `docker-compose.prod.yml`, `docker-compose.fullstack.yml`, and `/agents`.
+
 ## Decisions
 
 - Продолжаем с Threaded Mode несмотря на баги Mac клиента (2026-04-02)
@@ -71,6 +85,7 @@ Verified with `MATRIX_AGENT_REGISTRY_PATH='' MATRIX_PLATFORM_BACKEND='' UV_CACHE
 - [Phase 05]: Expose `clear` only when prototype room-context support is available, while keeping `reset` as a compatibility alias.
 - [Phase 05]: Require recovered `platform_chat_id` for save/context/clear flows instead of falling back to shared local chat ids.
 - [Phase 05]: Split Compose artifacts by runtime intent: bot-only prod handoff vs internal full-stack verification.
+- [Phase 05]: Document /agents as the bot-side shared volume root while internal platform-agent keeps /workspace on the same named volume.
 
 ## Blockers
 
@@ -102,9 +117,10 @@ Verified with `MATRIX_AGENT_REGISTRY_PATH='' MATRIX_PLATFORM_BACKEND='' UV_CACHE
 | 05 | 03 | 3 min | 2 | 3 | 2026-04-27T22:06:43Z |
 | 05 | 01 | 8 min | 2 | 4 | 2026-04-27T22:09:28Z |
 | 05 | 02 | 16 min | 2 | 4 | 2026-04-27T22:15:58Z |
+| 05 | 04 | 3 min | 2 | 5 | 2026-04-27T22:17:10Z |
 
 ## Session
 
-- Last session: 2026-04-27T22:15:58Z
-- Stopped at: Completed 05-02-PLAN.md
+- Last session: 2026-04-27T22:17:10Z
+- Stopped at: Completed 05-04-PLAN.md
 - Resume file: .planning/phases/05-mvp-deployment/.continue-here.md