dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: done 288_bug_ambient_mode_state_lost_on_server_restart

Browse Source
This commit is contained in:
Dave
2026-03-18 15:01:44 +00:00
parent 8fcfadcb04
commit 3923aafb71
5 changed files with 29 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
.story_kit/work/5_done/273_story_matrix_bot_sends_typing_indicator_while_waiting_for_claude_response.md
View File

@@ -1,24 +0,0 @@
---
name: "Matrix bot sends typing indicator while waiting for Claude response"
---
# Story 273: Matrix bot sends typing indicator while waiting for Claude response
## User Story
As a user chatting with the Matrix bot, I want to see a typing indicator in Element while the bot is processing my message, so that I know it received my request and is working on a response.
## Acceptance Criteria
- [ ] Bot sets m.typing on the room as soon as it starts the Claude API call
- [ ] Typing indicator is cleared when the first response chunk is sent to the room
- [ ] Typing indicator is cleared on error so it doesn't get stuck
- [ ] No visible delay between sending a message and seeing the typing indicator
## Notes
- **2026-03-18**: Moved back to current from done. Previous attempt went through the full pipeline but merged with an empty diff — no typing indicator code was actually implemented. Needs a real implementation this time.
## Out of Scope
- TBD

22
.story_kit/work/5_done/284_story_matrix_bot_status_command_shows_pipeline_and_agent_availability.md
View File

@@ -1,22 +0,0 @@
---
name: "Matrix bot status command shows pipeline and agent availability"
---
# Story 284: Matrix bot status command shows pipeline and agent availability
## User Story
As a user in a Matrix room, I want to type "{bot_name} status" and get a formatted summary of the full pipeline (upcoming through done) with agent assignments, plus which agents are currently free, so that I can check project status without leaving chat.
## Acceptance Criteria
- [ ] Chat command "{bot_name} status" triggers a pipeline status display (bot name comes from display_name in bot.toml)
- [ ] Output shows all stages: upcoming, current, qa, merge, done — with story names and IDs
- [ ] Each active story shows its assigned agent name and model
- [ ] Output includes a section showing which agents are free (not currently assigned to any story)
- [ ] Response is formatted for readability in Matrix (monospace or markdown as appropriate)
- [ ] Command is handled at the bot level — does not require a full Claude invocation
## Out of Scope
- TBD

29
.story_kit/work/5_done/288_bug_ambient_mode_state_lost_on_server_restart.md Normal file
View File

@@ -0,0 +1,29 @@
---
name: "Ambient mode state lost on server restart"
---
# Bug 288: Ambient mode state lost on server restart
## Description
Story 282 implemented ambient mode toggle but only in-memory. The acceptance criterion requiring persistence in bot.toml was not implemented. Every server restart (including rebuild_and_restart) clears ambient mode for all rooms.
## How to Reproduce
1. Type "timmy ambient on" — get confirmation
2. Restart server (or rebuild_and_restart)
3. Send unaddressed message — bot ignores it, ambient mode is gone
## Actual Result
Ambient mode state is lost on server restart.
## Expected Result
Ambient mode per-room state is persisted in bot.toml and restored on startup.
## Acceptance Criteria
- [ ] Ambient mode per-room state is saved to bot.toml when toggled
- [ ] Ambient mode state is restored from bot.toml on server startup
- [ ] bot.toml.example includes the ambient_rooms setting with a comment