22a3a2b60a
docs(05-04): document split deployment artifacts
...
- document prod vs fullstack compose usage
- align operator docs with shared /agents contract
2026-04-28 01:15:41 +03:00
8ffbe7b6b3
wip: deployment architecture research — Phase 05 ready to plan
...
- docs/deploy-architecture.md: full deployment topology, agent API, file transfer via shared volume
- .planning/HANDOFF.json + .continue-here.md: session state for Phase 05 planning
2026-04-27 21:46:27 +03:00
32b03becc8
docs: clarify matrix multi-agent routing specs
2026-04-24 12:42:58 +03:00
59fbb52c20
docs: add matrix multi-agent and restart state specs
2026-04-24 12:28:53 +03:00
7d58dd1caf
fix: use direct agent api per request
2026-04-22 15:31:28 +03:00
0c2884c2b1
refactor: use thin upstream transport adapter
2026-04-22 01:25:11 +03:00
4d917ac794
docs: add thin transport adapter plan
2026-04-22 00:17:15 +03:00
3a3fcdc695
docs: add thin transport adapter design
2026-04-22 00:11:20 +03:00
4524a6abc8
feat: finalize matrix platform audit and docs
2026-04-21 15:35:03 +03:00
105ecc68ed
docs: add matrix staged attachments design
2026-04-20 16:05:28 +03:00
8b04fcaf77
docs: add matrix shared workspace file flow design
2026-04-20 15:04:20 +03:00
9bb93fbbda
docs: add matrix per-chat context design
2026-04-19 16:37:41 +03:00
c004d96785
docs: add exact run commands for matrix prototype
2026-04-08 02:57:45 +03:00
9c73266ea5
docs: add matrix direct-agent prototype runbook
2026-04-08 02:51:25 +03:00
1fdb5bf303
docs: add matrix direct-agent prototype design
2026-04-08 00:22:20 +03:00
6ced154124
feat(matrix): land QA follow-ups and refresh docs
...
- harden Matrix onboarding/chat lifecycle after manual QA
- refresh README and Matrix docs to match current behavior
- add local ignores for runtime artifacts and include current planning/report docs
Closes #7
Closes #9
Closes #14
2026-04-05 19:08:58 +03:00
319ea08da9
docs: add known limitations for Telegram Threaded Mode
2026-04-02 17:18:03 +03:00
6cfdfba2f4
docs: add implementation plan for telegram forum redesign
2026-04-02 00:39:39 +03:00
bb690a3c38
docs: add forum-first redesign spec for Telegram adapter
...
Replaces DM+Forum hybrid design with Bot API 9.3 Threaded Mode
as the sole interaction model.
2026-04-02 00:27:29 +03:00
1c6e028e48
docs: add final progress report for 2026-04-01
2026-04-01 02:14:17 +03:00
bcdaea5143
docs: Forum Topics implementation plan
2026-03-31 23:02:56 +03:00
a8885aeaa1
docs: Forum Topics mode design spec
2026-03-31 22:54:44 +03:00
41660fe84a
refactor: rename platform/ → sdk/ to avoid stdlib conflict
...
platform/ shadowed Python's stdlib platform module, breaking
aiogram/aiohttp/multidict at import time. Renamed to sdk/ and
updated all imports across core/, tests/, and adapter/telegram/.
2026-03-31 21:57:23 +03:00
c979f96c3c
docs: fix matrix adapter spec — attachments, returning user, get_or_create_user
2026-03-31 21:34:54 +03:00
09919b2463
docs: matrix adapter design spec
2026-03-31 21:31:57 +03:00
a3449fc864
docs: telegram adapter design spec + remove soul style presets from mock
2026-03-31 19:49:13 +03:00
67499daa61
feat: extend platform mock + add research docs
...
platform/interface.py:
- Add Attachment, MessageChunk, AgentEvent types
- Add stream_message() to PlatformClient Protocol (door open for streaming)
- Add WebhookReceiver Protocol
platform/mock.py:
- Add attachment_mode config (url/binary/s3)
- Implement stream_message() — single chunk, ready for real streaming
- Add register_webhook_receiver() + simulate_agent_event() for testing
docs/research/:
- telegram-forum-topics.md — aiogram 3.x Forum Topics API, FSM patterns, UX analysis
- fsm-patterns.md — FSM storage options, StateData best practices
- matrix-spaces.md — matrix-nio Space API, room ordering, invite flow
- matrix-events.md — reactions, threads, typing, sync loop pitfalls
- telegram-chat-alternatives.md — 7 alternatives for multi-chat UX, virtual chats in DM recommended
2026-03-30 14:04:34 +03:00
4f5c5679d5
docs: sync all markdown with current architecture
...
Remove session management concepts (no create_session/close_session/
DELETE /sessions — Master handles container lifecycle automatically).
Update PlatformClient contract, ChatContext, project structure tree,
and FSM diagrams across all docs to match the implemented core/.
- README.md: fix core/ structure tree + PlatformClient snippet
- docs/surface-protocol.md: remove session.py/_template.py, fix
ChatContext (drop session_id), fix PlatformClient contract, fix
"free features" list
- docs/telegram-prototype.md: remove "создаёт сессию на платформе"
- docs/matrix-prototype.md: same + remove !sessions, fix FSM
(SessionCreated → ChatCreated), fix status block
- docs/user-flow.md: rewrite sequence diagram to POST /users/{id}/
chats/{id}/messages; update FSM states
2026-03-29 21:42:02 +03:00
36730ae716
feat: implement core/ and platform/ with full test coverage
...
- platform/interface.py: PlatformClient Protocol + Pydantic models (User,
MessageResponse, UserSettings) — no explicit session management, Master
handles container lifecycle
- platform/mock.py: MockPlatformClient with simulated latency, [MOCK]
responses, is_new correctly True only on first creation
- core/protocol.py: unified dataclasses for all events and responses
(IncomingMessage/Command/Callback, OutgoingMessage/UI/Notification,
AuthFlow, ChatContext, SettingsAction, etc.)
- core/store.py: StateStore Protocol + InMemoryStore (tests) + SQLiteStore
(prod) with JSON serialization
- core/chat.py: ChatManager — chat metadata (C1/C2/C3), not container
lifecycle (that's the platform's job)
- core/auth.py: AuthManager — start_flow / confirm / is_authenticated
- core/settings.py: SettingsManager — get/apply with store cache
- core/handler.py: EventDispatcher — registry-based routing with keys
(command name, action name, attachment type, "*" catch-all)
- core/handlers/: register_all() + start/new/message/callback/settings
handlers; voice slot falls back to stub text until voice_handler added
- conftest.py: sys.path fix so local platform/ shadows stdlib platform
- docs/api-contract.md: rewritten for Lambda Lab 3.0 container model
46 tests passing, 0 warnings.
2026-03-29 21:42:02 +03:00
ce8af9fa41
docs: add core implementation plan
2026-03-29 21:42:02 +03:00
53685747f6
docs: update core design and api-contract with platform container architecture
2026-03-29 21:42:02 +03:00
8e955045b2
docs: add core design spec (Registry + Handlers approach)
2026-03-29 21:42:02 +03:00
b6df29bd9b
init: surfaces-bot — Telegram & Matrix prototype
...
- Surface Protocol: unified IncomingMessage/OutgoingUI/ChatContext
- Telegram: Forum Topics (group + topics per chat)
- Matrix: Space + rooms per chat
- MockPlatformClient with PlatformClient Protocol
- docs: surface-protocol, telegram/matrix specs, api-contract, claude-code-guide
- project scaffold: src/, tests/, pyproject.toml
Co-Authored-By: Claude Sonnet 4-6 <noreply@anthropic.com>
2026-03-27 00:35:42 +03:00
