huskies: done 493_bug_story_dependency_chain_not_firing_due_to_front_matter_format_issues

2026-04-07 13:32:42 +00:00
parent a3a3942b0a
commit c64577eff0
4 changed files with 34 additions and 64 deletions
@@ -1,21 +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
-
- [ ] The `UpcomingStory` API response includes a `depends_on` field (list of story numbers) when the story has dependencies in its front matter
- [ ] The `status <number>` chat command shows `depends_on` in the front matter fields section when present
- [ ] The web UI pipeline stage cards show a "Depends on: #N, #M" badge when a story has dependencies
- [ ] Stories with no `depends_on` field show no dependency indicator (no regressions)
-
-## Out of Scope
-
- Rendering the dependency status (done/not done) in the UI — only the raw list of numbers is shown
- Adding or removing dependencies via the web UI (the existing `depends` chat command handles that)
@@ -1,17 +0,0 @@
---
-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
@@ -1,26 +0,0 @@
---
-name: "CRDT state layer backed by SQLite"
-agent: coder-opus
-depends_on: [489]
---
-
-# Story 490: CRDT state layer backed by SQLite
-
-## User Story
-
-As a developer, I want the BFT JSON CRDT document backed by SQLite for persistence, so CRDT ops survive restarts and the state layer is ready for multi-node sync.
-
-## Acceptance Criteria
-
- [ ] BFT CRDT crate (crates/bft-json-crdt/) integrated into the server
- [ ] CRDT ops persisted to SQLite via sqlx (backend-agnostic schema)
- [ ] Pipeline state reads switch from filesystem to CRDT document
- [ ] Pipeline state writes go through CRDT ops (which persist to SQLite)
- [ ] Filesystem .huskies/work/ directories still updated as a secondary output for backwards compat during transition
- [ ] CRDT state reconstructed from SQLite on startup
- [ ] agent: coder-opus
- [ ] depends_on: [489]
-
-## Out of Scope
-
- TBD