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

wip: 01.1-matrix-restart-reconciliation-and-dev-reset-workflow paused at task 1/2

Browse source
This commit is contained in:
Mikhail Putilovskij 2026-04-04 13:14:53 +03:00
parent 0299887924
commit 7fce4c9b3e
2 changed files with 135 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

87
.planning/HANDOFF.json Normal file
View file

@ -0,0 +1,87 @@
{
"version": "1.0",
"timestamp": "2026-04-04T10:13:58.720Z",
"phase": "01.1",
"phase_name": "matrix-restart-reconciliation-and-dev-reset-workflow",
"phase_dir": ".planning/phases/01.1-matrix-restart-reconciliation-and-dev-reset-workflow",
"plan": 3,
"task": 1,
"total_tasks": 2,
"status": "paused",
"completed_tasks": [],
"remaining_tasks": [
{
"id": 1,
"name": "Add a dev-only Matrix reset CLI with explicit modes",
"status": "not_started"
},
{
"id": 2,
"name": "Replace the README reset ritual with the new restart and reset workflow",
"status": "not_started"
}
],
"blockers": [
{
"description": "Phase 02 SDK integration remains blocked because platform control-plane contract is not stable yet; current platform repos only clearly expose the direct agent WebSocket layer.",
"type": "external",
"workaround": "Keep the current consumer-facing bot flows and mock-backed facade for now; use Matrix as the internal testing surface and revisit integration once master user/chat/session access is clarified."
}
],
"human_actions_pending": [
{
"action": "Confirm with the platform team the minimal control-plane contract for user/chat/session access and whether settings/attachments will exist in master.",
"context": "Current evidence shows agent_api is usable, but master is not yet a stable consumer-facing API.",
"blocking": true
}
],
"decisions": [
{
"decision": "Do not start a full rewrite of the consumer-facing bot integration yet.",
"rationale": "Platform direction is visible, but too many pieces outside the direct agent WebSocket protocol are still undefined or inconsistent.",
"phase": "02"
},
{
"decision": "Treat sdk/mock.py as a temporary local integration facade rather than a near-drop-in replacement for the real platform.",
"rationale": "The current mock assumes a unified platform API, while the real platform is split between control plane and direct agent session.",
"phase": "02"
},
{
"decision": "Use Matrix as the internal testing surface while waiting for the platform contract to stabilize.",
"rationale": "This preserves product iteration without coupling the bot too early to a moving platform backend.",
"phase": "02"
}
],
"uncommitted_files": [
".planning/config.json",
"adapter/matrix/bot.py",
"adapter/matrix/handlers/__init__.py",
"adapter/matrix/handlers/auth.py",
"adapter/matrix/handlers/chat.py",
"adapter/matrix/handlers/settings.py",
"adapter/telegram/bot.py",
"sdk/mock.py",
"tests/adapter/matrix/test_chat_space.py",
"tests/adapter/matrix/test_dispatcher.py",
"tests/adapter/matrix/test_invite_space.py",
"tests/platform/test_mock.py",
".planning/phases/01-matrix-qa-polish/01-01-SUMMARY.md",
".planning/phases/01-matrix-qa-polish/01-04-SUMMARY.md",
".planning/phases/01-matrix-qa-polish/01-05-PLAN.md",
".planning/phases/01-matrix-qa-polish/01-06-PLAN.md",
".planning/phases/01-matrix-qa-polish/01-VERIFICATION.md",
".planning/phases/01.1-matrix-restart-reconciliation-and-dev-reset-workflow/.gitkeep",
"bot-examples/",
"docs/reports/2026-04-01-surfaces-progress-report.md",
"docs/superpowers/plans/2026-03-31-matrix-adapter.md",
"docs/workflow-backup-2026-04-01.md",
"forum_topics_research.md",
"image copy 2.png",
"image copy.png",
"image.png",
"lambda_bot.db",
"lambda_matrix.db"
],
"next_action": "When resuming, either execute Phase 01.1 Plan 03 Task 1 (Matrix reset CLI) or continue the platform-integration design by defining a split MasterClient/AgentSession boundary without changing consumer adapters yet.",
"context_notes": "This session was research-heavy rather than implementation-heavy. The key conclusion is that the real platform currently exposes a direct agent WebSocket SDK plus an unfinished master control plane; our mock models a richer unified platform than what exists today. That means future work should isolate the integration boundary, not rush a full rewrite."
}