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

story-kit: create 313_story_improve_htop_output_formatting_for_mobile_matrix_clients

Browse Source
This commit is contained in:
Dave
2026-03-19 19:20:42 +00:00
parent 8074e3b420
commit 11a6be4b45
2 changed files with 21 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
.story_kit/work/1_backlog/312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories.md
View File

@@ -1,37 +0,0 @@
---
name: "Auto-assign assigns mergemaster to coding-stage stories"
---
# Bug 312: Auto-assign assigns mergemaster to coding-stage stories
## Description
Auto-assign picks agents whose configured stage doesn't match the pipeline stage of the story. Observed multiple mismatch types:
- **Mergemaster assigned to coding-stage stories**: Story 310 was in `2_current/` but got mergemaster instead of a coder (2026-03-19)
- **Coders assigned to QA-stage stories**: Coders (stage=coder) have been observed running on stories in `3_qa/`
- **QA agents assigned to merge-stage stories**: QA agents (stage=qa) have been observed running on stories in `4_merge/`
The `auto_assign_available_work` function doesn't enforce that the agent's configured stage matches the pipeline stage of the story it's being assigned to. Story 279 (auto-assign respects agent stage from front matter) was supposed to fix stage matching, but the check may only apply to front-matter preferences, not the fallback assignment path.
## How to Reproduce
1. Move a story to any pipeline stage with no agent front matter preference
2. Wait for auto_assign_available_work to run
3. Observe that agents from the wrong stage get assigned (e.g. mergemaster to coding, coder to QA)
## Actual Result
Agents are assigned to stories in pipeline stages that don't match their configured stage. Mergemaster codes, coders do QA, QA agents attempt merges.
## Expected Result
Only coder-stage agents should be assigned to stories in 2_current/. Mergemaster should only be assigned to stories in 4_merge/.
## Acceptance Criteria
- [ ] auto_assign_available_work checks that the agent's configured stage matches the pipeline stage of the story before assigning
- [ ] Coder agents only assigned to stories in 2_current/
- [ ] QA agents only assigned to stories in 3_qa/
- [ ] Mergemaster only assigned to stories in 4_merge/
- [ ] Fallback assignment path respects stage matching (not just front-matter preference path)

21
.story_kit/work/1_backlog/313_story_improve_htop_output_formatting_for_mobile_matrix_clients.md Normal file
View File

@@ -0,0 +1,21 @@
---
name: "Improve htop output formatting for mobile Matrix clients"
---
# Story 313: Improve htop output formatting for mobile Matrix clients
## User Story
As a project owner checking htop from my phone, I want the htop dashboard output to be readable on a narrow screen, so that I can monitor system load and agent status from mobile Matrix clients like Element.
## Acceptance Criteria
- [ ] htop output uses compact single-line format per agent instead of wide table columns
- [ ] Load average is on its own short line
- [ ] Agent entries show name, story number, CPU%, and memory without wrapping on a ~40 character wide screen
- [ ] No unnecessary whitespace or padding that wastes horizontal space
- [ ] Still readable on desktop — compact is fine for both
## Out of Scope
- TBD