summaryrefslogtreecommitdiff
path: root/docs/superpowers/plans/2026-07-17-linear-task-chains.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/superpowers/plans/2026-07-17-linear-task-chains.md')
-rw-r--r--docs/superpowers/plans/2026-07-17-linear-task-chains.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/superpowers/plans/2026-07-17-linear-task-chains.md b/docs/superpowers/plans/2026-07-17-linear-task-chains.md
index ebb576a..c0e2095 100644
--- a/docs/superpowers/plans/2026-07-17-linear-task-chains.md
+++ b/docs/superpowers/plans/2026-07-17-linear-task-chains.md
@@ -2,6 +2,8 @@
> Implements `docs/superpowers/specs/2026-07-15-linear-task-chains-design.md`.
> Backend (Go), web timeline indicator, and Android widget chain view — full stack, per user decision 2026-07-17.
+>
+> **Correction (2026-07-17, later same day):** Task 3/4 below originally under-implemented the spec's "an ordered list of task titles/descriptions" API line — `CreateChain`/`POST /api/widget/chains` only accepted bare title strings, with priority hardcoded to 1. Fixed to accept `[]models.ChainTaskInput{Content, Description, Priority}` per position, matching the spec.
**Goal:** doot-native tasks can belong to a `task_chains` sequence with a WIP limit of exactly 1 — only one task in the chain is ever unlocked/actionable, and completing it unlocks the next. Locked tasks are hidden from date-based views; a dedicated checklist view shows the whole chain.