huskies: merge 503_bug_depends_on_pointing_at_an_archived_story_is_silently_treated_as_deps_met_surprising_users

2026-04-09 18:27:25 +00:00
parent 8b2e068d3e
commit 41515e3b8f
6 changed files with 393 additions and 3 deletions
@@ -88,6 +88,14 @@ Items move through stages by moving the file between directories:

 Items in `5_done` are auto-swept to `6_archived` after 4 hours by the server.

+### Dependency Semantics (`depends_on`)
+
+Work items can declare `depends_on: [N, M]` in their front matter. The auto-assign loop promotes a backlog item to current only when every listed dependency has reached `5_done` **or** `6_archived`.
+
+**Archived = satisfied (recorded decision, bug 503):** A dep in `6_archived` counts as satisfied. Stories auto-sweep from `5_done` to `6_archived` after 4 hours, so by the time a dep is archived the dependent story is normally already in current. Changing this to "archived = abandoned" would re-block already-promoted stories when their deps sweep, which is a worse regression.
+
+**When the dep is already archived at creation time:** If you create a story whose `depends_on` points at a story already in `6_archived`, `create_story` will emit a visible warning. The dep will resolve immediately on the next promotion tick. If the archived dep was abandoned rather than cleanly completed, remove the `depends_on` field or move the new story back to backlog manually after promotion fires.
+
 ### Filesystem Watcher

 The server watches `.story_kit/work/` for changes. When a file is created, moved, or modified, the watcher auto-commits with a deterministic message and broadcasts a WebSocket notification to the frontend. This means: