Surfaces_team/surfaces
4
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

docs(05-03): complete shared-volume attachment hardening plan

Browse source 
- add 05-03 summary with task commits and verification details
- update roadmap and state for completed Phase 05 plan 03
This commit is contained in:
Mikhail Putilovskij 2026-04-28 01:07:35 +03:00
parent a75b26a1cb
commit 6693d72cbd
3 changed files with 145 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

38
.planning/STATE.md
View file

@ -2,14 +2,13 @@
gsd_state_version: 1.0
milestone: v1.0
milestone_name: — Production-ready surfaces
status: Phase 04 complete — deployment architecture clarified, Phase 05 ready to plan
last_updated: "2026-04-27T18:44:51Z"
status: Executing Phase 05
last_updated: "2026-04-27T22:06:43.419Z"
progress:
total_phases: 5
total_phases: 6
completed_phases: 2
total_plans: 12
completed_plans: 9
percent: 75
total_plans: 16
completed_plans: 10
---
# State
@ -19,21 +18,18 @@ progress:
See: .planning/PROJECT.md (updated 2026-04-02)
**Core value:** Пользователь ведёт диалог с Lambda через любой мессенджер без изменения ядра
**Current focus:** Phase 04 multi-agent routing follow-up fully implemented; ready for live validation or Phase 05 planning
**Current focus:** Phase 05 — mvp-deployment
## Current Phase
**Phase 4** implementation complete: Matrix MVP + multi-agent routing
**Phase 05** in progress: MVP deployment hardening
All 5 tasks of the multi-agent routing follow-up are committed on `feat/matrix-direct-agent-prototype`:
Plan `05-03` is complete. Shared-volume attachment handling now keeps Matrix file references room-safe on disk and relative across the `/agents` deployment boundary.
- `7627012` / `242f4aa` / `9ccba16` — agent registry loader, RoutedPlatformClient facade, fail-fast on missing registry in real mode
- `a65227e` — dispatch chat_id contract alignment
- `74cf028` — `!agent` command, `selected_agent_id` persistence, unbound-room binding on first selection
- `7623039` — attachment normalization in core message handler
- `e733119` — stale room blocking, `agent_id` binding on `!new`, durable restart state tests
- `cafb0ec` — failing regressions for `/agents` workspace paths and send-file normalization
- `9a03160` — runtime normalization of `/workspace` and `/agents` absolute paths back to relative `workspace_path` values
135 Matrix tests pass. The branch is ready for review and merge.
Verified with `UV_CACHE_DIR=/tmp/uv-cache uv run pytest tests/adapter/matrix/test_files.py tests/platform/test_real.py tests/adapter/matrix/test_send_outgoing.py -v`.
## Decisions
@ -60,6 +56,9 @@ All 5 tasks of the multi-agent routing follow-up are committed on `feat/matrix-d
- [Phase 04 follow-up]: agent_routing_enabled flag on MatrixRuntime activates stale-room check only in real multi-agent mode (RoutedPlatformClient).
- [Phase 04 follow-up]: !new binds agent_id at room creation time using selected_agent_id from user metadata.
- [Phase 04 follow-up]: platform_chat_seq (PLATFORM_CHAT_SEQ_KEY) is stored in SQLiteStore and survives restart — confirmed by test.
- [Phase 05 reset]: Discard the single-chat / DM-first deployment direction. Replan around Space+rooms, per-room `platform_chat_id`, real `!clear`, reconciliation, and split prod/fullstack compose artifacts.
- [Phase 05]: Keep adapter/matrix/files.py as the sole path builder; sdk/real.py only normalizes shared-volume attachment references.
- [Phase 05]: Normalize /workspace and /agents absolute file paths back to relative workspace_path values before agent transport and Matrix file rendering.
## Blockers
@ -72,7 +71,7 @@ All 5 tasks of the multi-agent routing follow-up are committed on `feat/matrix-d
- Phase 01.1 inserted after Phase 01: Matrix restart reconciliation and dev reset workflow (URGENT)
- Phase 4 added: Matrix MVP: shared agent context and context management command
- Phase 04 follow-up added inline: multi-agent routing (RoutedPlatformClient, !agent, stale room blocking, restart persistence)
- New platform signal: upcoming proper `chat_id` support should enable file-level context separation and stronger context management in a future follow-up phase.
- Phase 05 reset on 2026-04-28: erroneous single-chat deployment artifacts were removed before fresh planning.
## Performance Metrics
@ -88,9 +87,10 @@ All 5 tasks of the multi-agent routing follow-up are committed on `feat/matrix-d
| 04 | 02 | 1 session | 2 commits + summary | 8 | 2026-04-17 |
| 04 | 03 | 1 session | 1 commit + summary | 4 | 2026-04-17 |
| 04 | follow-up | 1 session | 5 tasks | 10+ | 2026-04-24 |
| 05 | 03 | 3 min | 2 | 3 | 2026-04-27T22:06:43Z |
## Session
- Last session: 2026-04-24T14:10:00Z
- Stopped at: Deployment architecture clarified with platform team; docs/deploy-architecture.md written; Phase 05 ready to plan
- Resume file: .planning/.continue-here.md
- Last session: 2026-04-27T22:06:43Z
- Stopped at: Completed 05-03-PLAN.md
- Resume file: .planning/phases/05-mvp-deployment/.continue-here.md