huskies: create 488_story_web_ui_shows_project_name_in_browser_tab_with_huskies_favicon
This commit is contained in:
-24
@@ -1,24 +0,0 @@
|
|||||||
---
|
|
||||||
name: "CRDT state backend replacing filesystem pipeline state"
|
|
||||||
agent: coder-opus
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 477: CRDT state backend replacing filesystem pipeline state
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a developer, I want the pipeline state (stages, agent assignments, retry counts, blocked flags) stored in a BFT JSON CRDT document backed by SQLite instead of filesystem directories, so the state model is ready for multi-node distribution.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] Pipeline state (which stage a story is in, agent assignments, retry counts, blocked flags) stored in CRDT doc, not .huskies/work/ directories
|
|
||||||
- [ ] CRDT state persisted to SQLite so it survives container restarts
|
|
||||||
- [ ] BFT CRDT crate integrated from crates/bft-json-crdt/
|
|
||||||
- [ ] Story markdown files (content/AC), worktrees, and config remain on filesystem
|
|
||||||
- [ ] All existing pipeline operations (move story, start agent, block, unblock) work against the CRDT backend
|
|
||||||
- [ ] Single-node behaviour unchanged from the user's perspective
|
|
||||||
- [ ] Rollback commit: 5561b9c6
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
-17
@@ -1,17 +0,0 @@
|
|||||||
---
|
|
||||||
name: "Display story dependencies in web UI and chat commands"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 487: Display story dependencies in web UI and chat commands
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a user managing stories with dependencies, I want to see dependency information in the web UI story panel and in chat/slash command output, so I can understand which stories are blocked and why without reading the raw markdown files.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] TODO
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
+17
@@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
name: "Web UI shows project name in browser tab with huskies favicon"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 488: Web UI shows project name in browser tab with huskies favicon
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a user running huskies on multiple projects, I want the browser tab to show the project name (e.g. "Reclaimer") instead of the hardcoded "Huskies", and I want a huskies favicon derived from the website logo, so I can distinguish tabs and have proper branding.
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] TODO
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user