doot.git/docs, branch master

A guide for an agent creating doot tasks

2026-11-08T20:38:43+00:00

Written for a Claude instance with no access to this repo or the database, so it covers the whole path: get a session, create a task, and what the endpoint will not do. Checked against the live server rather than read off the handlers. The auth request and poll return the documented shapes, and an unauthenticated create is refused with 401. Three things it exists to say, because none are guessable from the outside: - A human approves every session in a browser, and it lasts an hour. There is no API key and no auto-approval; trust levels change how the prompt is labelled, not whether it appears. The approval request itself expires in five minutes, so asking early wastes it. - The create endpoint silently ignores description, labels, estimated_minutes and project_name. They are real fields on a doot task and they are dropped without complaint, so an agent that sends them gets a task that is missing things it thinks it set. - The response carries no task id, so a create cannot be chained into an update. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Finish the spec status update (previous commit only applied partially)

2026-09-03T02:36:35+00:00

The prior commit's edit to the open-questions section silently no-opped on a mismatched target, so the spec still carried the pre-implementation questions and claimed the duplicate "Yard work" task was outstanding after it had been deleted. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Update punch-list spec: record what shipped and what's still open

2026-09-03T02:36:10+00:00

Marks the core pull model as implemented and deployed, with the live verification results, and replaces the old open-questions section with the honest remaining list -- carry-over is unbuilt, there's still no dedicated review surface, buckets still push rather than being pulled, and ordinary undated backlog tasks have no commit control yet. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Update punch-list spec: correct the recurrence diagnosis, record progress

2026-09-03T00:46:40+00:00

The spec described skipped recurrences as an accidental "double-book." It isn't: generating the successor regardless of completion is deliberate (so skipping doesn't stall the series). The actual defect was that nothing retired the superseded occurrence, so skips accumulated as permanent overdue items. Recorded the intended semantics -- an occurrence not done before its successor lands is stale, and the newer one stands. Also marked the bucket pool as populated and flagged the leftover duplicate "Yard work" recurring task as needing an explicit decision, since deleting it ends its series. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Add design spec for the pull-based punch list

2026-09-02T23:49:21+00:00

Written from measurements against production rather than from the symptom report: the free-standing task list is actually fine (19 genuinely today-sized items); what breaks it is due_date carrying two incompatible meanings, with chains stamping due_date=now on every unlock so milestones are born looking like deadlines. Proposes splitting due_date (real deadlines only) from a new committed_date ("I chose this today"), moving chain steps and bucket items behind an explicit pull, and adding a short review surface. Not yet implemented -- capturing the design before building. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Add bucket CRUD and read-only Projects/Labels to Settings page

2026-07-18T09:38:26+00:00

New "Maintenance Buckets" section: create a bucket, add a pool item by title (creates the task and assigns it in one step), remove an item, delete a bucket (unbuckets its tasks rather than deleting them). New read-only Projects and Labels sections (name + color swatch) -- both are simple enough that read-only is the right call on web, per user direction, rather than duplicating the Android popup's editing UX. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL

Rework Tasks tab: Chains section, checklist modal, project visibility

2026-07-18T00:14:45+00:00

The flat Tasks-tab atom list was silently dumping every chain step (locked and unlocked) and dormant bucket-pool items in as ordinary undated cards, with no chain/project context and no protection against completing a locked step out of order. - CompleteNativeTask now rejects completing a locked chain task (ErrChainTaskLocked), mapped to 400 in both the widget and web complete-atom handlers. - Chain tasks and dormant bucket items are excluded from the flat atom list; a new "Chains" section shows one card per active/paused chain with the current step and N/M progress. - New chain checklist modal (GET /chains/{id}) lists every position in order with pause/resume/abandon -- the web view originally deferred as Android-only. - Fixed a real bug this surfaced: resuming a paused chain only flipped the status flag, never unlocking the deferred successor, so a chain paused right after a completion stayed stuck forever. SetChainStatus now catches up the deferred advancement on resume, idempotently. - Atom cards gained a project-name chip for general visibility. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL

Extend chain creation to accept per-task description and priority

2026-07-17T22:46:18+00:00

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 Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL

Document deferred UI screens for chains and buckets

2026-07-17T22:28:08+00:00

Fleshes out the "not built" notes in both specs into actionable follow-up scope: what data/API layer already exists, what the screen needs to do, and precedent to follow. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL

Implement linear task chains and recurring maintenance buckets

2026-07-17T22:22:37+00:00

Backend, web timeline, and Android widget wiring for the last two unimplemented items from doot-future-task-scheduling-ideas. Chains: task_chains table + chain_id/chain_position/chain_unlocked on native_tasks (migration 026), WIP-limit-1 advancement hooked into CompleteNativeTask, locked tasks excluded from all date-based queries, 5 new /api/widget/chains* endpoints, an N/M position badge on web and Android widget rows. Buckets: maintenance_buckets table + bucket_id/bucket_state/ bucket_last_active_at on native_tasks (migration 027), staleness-then-priority selection scoring, a new RunBucketCycleCheck scheduler loop, 5 new endpoints including the distinct Defer action, a Defer button on web and Android widget rows. Also corrected stale "not yet approved" status headers on the two already-shipped specs this work depended on (labels/projects, budgets/ availability) -- their headers were never updated after implementation. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL