diff options
| author | Peter Stone <thepeterstone@gmail.com> | 2026-07-17 22:46:18 +0000 |
|---|---|---|
| committer | Peter Stone <thepeterstone@gmail.com> | 2026-07-17 22:46:18 +0000 |
| commit | be4d606e9a1f5b068abcc21bbac58d1e4705ea1f (patch) | |
| tree | 220aea277125aee4aa35a10201ab0a8a6c1caf89 /docs/superpowers | |
| parent | 9460b768335dcaf7f89020caf00f1a125de14b20 (diff) | |
Extend chain creation to accept per-task description and priority
CreateChain and POST /api/widget/chains previously only took bare
title strings, with priority hardcoded to 1 -- narrower than the
spec's "an ordered list of task titles/descriptions" API line. Now
accepts []models.ChainTaskInput{Content, Description, Priority} per
position, priority defaulting to 1 when omitted.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL
Diffstat (limited to 'docs/superpowers')
| -rw-r--r-- | docs/superpowers/plans/2026-07-17-linear-task-chains.md | 2 |
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. |