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

story-kit: accept 242_story_status_slash_command

Browse Source
This commit is contained in:
Dave
2026-03-17 00:26:51 +00:00
parent a02ea3c292
commit 250f3ff819
3 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
.story_kit/work/5_done/240_story_btw_side_question_slash_command.md
View File

@@ -1,28 +0,0 @@
---
name: /btw Side Question Slash Command
---
## User Story
As a user, I want to ask the agent a quick side question using `/btw` so that I can get a fast answer from the current conversation context without disrupting the main chat thread.
## Acceptance Criteria
- [ ] User can type `/btw <question>` in the chat input
- [ ] The agent answers using the full conversation history as context
- [ ] The question and response are displayed in a dismissible overlay, not in the main chat thread
- [ ] The question and response are not added to the conversation history
- [ ] No tool calls are made when answering a `/btw` question — the agent responds only from what is already in context
- [ ] The overlay can be dismissed with Escape, Enter, or Space
- [ ] `/btw` can be invoked while the agent is actively processing a response without interrupting it
- [ ] The slash command detection and dispatch mechanism must be reusable — build a shared parser/router so future slash commands (e.g. /help, /status) can plug in without duplicating detection logic
## Out of Scope
- Follow-up turns within the side question
- Tool usage in side question responses
- Persisting side question history
## Rejection Notes
**2026-03-14:** Previous implementation was rejected. The frontend did nothing when the user typed `/btw` — the slash command was not wired up in the UI at all. The backend may have had changes but the feature was non-functional from the user's perspective. Ensure the full end-to-end flow works: typing `/btw <question>` in the chat input must visibly trigger the overlay with a response.

20
.story_kit/work/5_done/242_story_status_slash_command.md
View File

@@ -1,20 +0,0 @@
---
name: "/status Slash Command"
---
# Story 242: /status Slash Command
## User Story
As a user, I want to type /status in the chat input so that I can see the current state of the agent, active story, pipeline stage, and any running processes at a glance.
## Acceptance Criteria
- [ ] User can type /status in the chat input
- [ ] A status overlay or panel shows: current story (if any), pipeline stage, agent status, and running processes
- [ ] The overlay can be dismissed with Escape, Enter, or Space
- [ ] The slash command detection and dispatch mechanism is shared across all slash commands (reuse the same parser/router used by /btw and other slash commands — do not duplicate detection logic)
## Out of Scope
- TBD

21
.story_kit/work/5_done/246_story_enforce_cryptographic_identity_verification_for_matrix_commands.md
View File

@@ -1,21 +0,0 @@
---
name: "Enforce cryptographic identity verification for Matrix commands"
---
# Story 246: Enforce cryptographic identity verification for Matrix commands
## User Story
As the operator of a Story Kit instance, I want the Matrix bot to always require cryptographic device verification before executing commands, so that a compromised homeserver cannot be used to execute unauthorized commands.
## Acceptance Criteria
- [ ] Bot refuses to process commands from unencrypted rooms
- [ ] Bot always verifies the sending device is cross-signing-verified by a trusted identity before executing any command
- [ ] The require_verified_devices config option is removed — verification is always on with no way to disable it
- [ ] Messages from unverified devices are rejected with a clear log message
- [ ] Existing allowed_users check remains as a first-pass filter before the cryptographic check
## Out of Scope
- TBD