From d6858b690b4e3783e3b4d342e385c9b60fd48b12 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 11:58:50 +0000 Subject: [PATCH] story-kit: done 306_story_replace_manual_qa_boolean_with_configurable_qa_mode_field --- ...down_in_expanded_work_item_detail_panel.md | 20 -------------- ...boolean_with_configurable_qa_mode_field.md | 26 +++++++++++++++++++ 2 files changed, 26 insertions(+), 20 deletions(-) delete mode 100644 .story_kit/work/1_backlog/309_story_show_token_cost_breakdown_in_expanded_work_item_detail_panel.md create mode 100644 .story_kit/work/5_done/306_story_replace_manual_qa_boolean_with_configurable_qa_mode_field.md diff --git a/.story_kit/work/1_backlog/309_story_show_token_cost_breakdown_in_expanded_work_item_detail_panel.md b/.story_kit/work/1_backlog/309_story_show_token_cost_breakdown_in_expanded_work_item_detail_panel.md deleted file mode 100644 index 3d26c3c..0000000 --- a/.story_kit/work/1_backlog/309_story_show_token_cost_breakdown_in_expanded_work_item_detail_panel.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -name: "Show token cost breakdown in expanded work item detail panel" ---- - -# Story 309: Show token cost breakdown in expanded work item detail panel - -## User Story - -As a project owner viewing a work item in the web UI, I want to see a per-agent token cost breakdown in the expanded detail panel, so that I can understand where tokens were spent on that story. - -## Acceptance Criteria - -- [ ] WorkItemDetailPanel fetches token cost data using the existing /work-items/:story_id/token-cost endpoint -- [ ] Shows per-agent session breakdown: agent name, model, token counts (input/output/cache), cost in USD -- [ ] Shows total cost for the story -- [ ] Shows empty state when no token data exists for the story - -## Out of Scope - -- TBD diff --git a/.story_kit/work/5_done/306_story_replace_manual_qa_boolean_with_configurable_qa_mode_field.md b/.story_kit/work/5_done/306_story_replace_manual_qa_boolean_with_configurable_qa_mode_field.md new file mode 100644 index 0000000..b08b3ac --- /dev/null +++ b/.story_kit/work/5_done/306_story_replace_manual_qa_boolean_with_configurable_qa_mode_field.md @@ -0,0 +1,26 @@ +--- +name: "Replace manual_qa boolean with configurable qa mode field" +--- + +# Story 306: Replace manual_qa boolean with configurable qa mode field + +## User Story + +As a project owner, I want to configure QA mode per-story and set a project-wide default, so that I can choose between human review, server-only gate checks, or full agent QA on a per-story basis. + +## Acceptance Criteria + +- [ ] Replace manual_qa: true/false front matter field with qa: human|server|agent +- [ ] qa: server — skip the QA agent entirely, rely on server's automated gate checks (clippy + tests + coverage). If gates pass, advance straight to merge +- [ ] qa: agent — current behavior, spin up a QA agent (Claude session) to review code and run gates +- [ ] qa: human — hold in QA for human approval after server gates pass (current manual_qa: true behavior) +- [ ] Default qa mode is configurable in project.toml (e.g. default_qa = "server") +- [ ] Set the initial default in project.toml to "server" +- [ ] Per-story front matter qa field overrides the project default +- [ ] Backwards compatible: existing stories without a qa field use the project default +- [ ] Remove the old manual_qa field handling and replace with the new qa field throughout pool.rs, story_metadata.rs, and any other references +- [ ] Update bot.toml.example and project.toml documentation to reflect the new field + +## Out of Scope + +- TBD