Mikhail Putilovskij 80800be60c 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

2026-04-03 12:29:44 +03:00

gsd_state_version

milestone

milestone_name

status

last_updated

progress

1.0

v1.0

— Production-ready surfaces

Executing Phase 01

2026-04-03T09:28:47.448Z

total_phases	completed_phases	total_plans	completed_plans
3	0	6	5

State

Project Reference

See: .planning/PROJECT.md (updated 2026-04-02)

Core value: Пользователь ведёт диалог с Lambda через любой мессенджер без изменения ядра Current focus: Phase 01 — matrix-qa-polish

Phase 1 of 3: Matrix QA & Polish

Продолжаем с Threaded Mode несмотря на баги Mac клиента (2026-04-02)
Invite flow Matrix переведён на idempotent-проверку через user_meta.space_id, а не через invite-room metadata (2026-04-02)
Неизвестные Matrix rooms больше не auto-register в роутере; используется явный fallback unregistered:{room_id} с warning-логом (2026-04-02)
[Phase 01]: Use ChatContext.surface_ref as the Matrix room identifier for !rename updates.
[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.

Phase	Plan	Duration	Tasks	Files	Recorded
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