diff options
Diffstat (limited to 'docs/superpowers/specs/2026-07-15-linear-task-chains-design.md')
| -rw-r--r-- | docs/superpowers/specs/2026-07-15-linear-task-chains-design.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/superpowers/specs/2026-07-15-linear-task-chains-design.md b/docs/superpowers/specs/2026-07-15-linear-task-chains-design.md index 98198b2..16e5337 100644 --- a/docs/superpowers/specs/2026-07-15-linear-task-chains-design.md +++ b/docs/superpowers/specs/2026-07-15-linear-task-chains-design.md @@ -61,3 +61,14 @@ Store-layer tests for: creating a chain seeds positions correctly (only position - Looping chains for ongoing practice — always terminates, per the interview. - Interaction with maintenance buckets ([[doot-future-task-scheduling-ideas]] item 3) — independent concepts, not designed to compose. - Web UI specifics for the chain/checklist view. + +## Deferred: Android chain-checklist screen + +Not built as of 2026-07-17. What exists today: a row-level "N/M" badge on the currently-unlocked task (`WidgetRows.kt`'s `TaskRow`), and the data layer to fetch the full ordered list (`WidgetRepository.fetchChain(id)` → `ChainDetail{chain, tasks}`, hitting `GET /api/widget/chains/{id}`; `Chain`/`ChainTask` models already defined in `WidgetItem.kt`). What's missing is the actual screen: tapping the badge does nothing yet (no `clickable`/`actionStartActivity` wired on it). + +Rough shape for whoever picks this up: +- A new Activity (matching the existing pattern of `TaskDetailActivity`/`EventDetailActivity`-style popups — check current detail-popup activities for the `taskAffinity` fix mentioned in the 2026-07-12 worklog entry, so it doesn't reopen behind Settings) launched via `actionStartActivity` from the chain badge, passing the chain id. +- On launch: call `WidgetRepository.fetchChain(id)`, render `tasks` in `chain_position` order — locked items dimmed/non-interactive (no due date, not completable from here), the one `chain_unlocked` item shown with its existing Complete affordance. +- Chain-level actions (pause/resume/abandon) as a small menu or buttons — repository methods `pauseChain`/`resumeChain`/`abandonChain` already exist and are ready to call. +- No automated Compose UI test harness in this project (established convention) — verify by building and a manual on-device/emulator check, same as every prior widget UI task this session. +- Web gets nothing here per the original spec ("Web UI specifics... out of scope") — this is Android-only follow-up work. |