docs(01-05): complete matrix confirmation scope plan

- add 01-05 summary with self-check results
- update planning state and roadmap progress for phase 01
This commit is contained in:
Mikhail Putilovskij 2026-04-03 12:29:44 +03:00
parent 716dec5dfd
commit 80800be60c
3 changed files with 117 additions and 9 deletions

View file

@ -2,13 +2,13 @@
gsd_state_version: 1.0
milestone: v1.0
milestone_name: — Production-ready surfaces
status: in_progress
last_updated: "2026-04-02T19:57:34.111Z"
status: Executing Phase 01
last_updated: "2026-04-03T09:28:47.448Z"
progress:
total_phases: 3
completed_phases: 0
total_plans: 4
completed_plans: 3
total_plans: 6
completed_plans: 5
---
# State
@ -18,7 +18,7 @@ progress:
See: .planning/PROJECT.md (updated 2026-04-02)
**Core value:** Пользователь ведёт диалог с Lambda через любой мессенджер без изменения ядра
**Current focus:** Phase 01 — matrix-qa-polish (next: 01-04)
**Current focus:** Phase 01 — matrix-qa-polish
## Current Phase
@ -33,6 +33,10 @@ See: .planning/PROJECT.md (updated 2026-04-02)
- [Phase 01]: Keep !archive limited to core archive state in Phase 1; Space child removal remains deferred.
- [Phase 01]: Matrix OutgoingUI no longer emits reactions; confirmation state is persisted and resumed via `!yes` / `!no`.
- [Phase 01]: `!settings` now renders a dashboard snapshot instead of advertising mutable subcommands.
- [Phase 01]: Split Matrix regression coverage into dedicated invite/chat/send_outgoing/confirm test modules.
- [Phase 01]: Kept 01-04 scoped to test coverage without widening into production-code changes.
- [Phase 01]: Matrix command callbacks now include room_id in payload for !yes and !no so confirm handlers can resolve runtime state without changing core protocol types.
- [Phase 01]: Pending confirmations are stored under the D-08 composite key of matrix user id plus room id, with a narrow legacy fallback only for callers that omit room context.
## Blockers
@ -45,8 +49,10 @@ See: .planning/PROJECT.md (updated 2026-04-02)
| 01 | 01 | 1 min | 3 | 3 | 2026-04-02T19:50:50Z |
| 01 | 02 | 1 min | 2 | 2 | 2026-04-02 |
| 01 | 03 | 3 min | 2 | 5 | 2026-04-02T19:57:34Z |
| 01 | 04 | 3 min | 2 | 7 | 2026-04-02T20:03:38Z |
| 01 | 05 | 2 min | 2 | 7 | 2026-04-03T09:28:47Z |
## Session
- Last session: 2026-04-02T19:57:34Z
- Stopped at: Completed 01-03-PLAN.md
- Last session: 2026-04-03T09:28:47Z
- Stopped at: Completed 01-05-PLAN.md