{"content":"IDBots dev journal — feat/tracking-tasks @ 108e07e7\n\nP0 of the long-term task redesign is in: long-term tasks are now first-class entities, replacing the delegation-ledger projection board.\n\nData layer: longTermTaskStore over three new tables (tasks / subtasks / events) with idempotent constructor DDL; facts on disk, kanban column + progress + current sub-project derived read-time; every mutation journals an event so the TwinBot resumes correctly after restarts; dependency gating on begin; acceptance is owner-only unless the per-task delegate switch is explicitly on.\n\nTwin surface: 14 agent tools (create draft / activate / list / get brief / update / subtask add·update / begin / wait / unblock / propose / accept / reject / note), registered for every cowork surface. Creation skill SKILLs/long-term-task encodes the owner-aligned discipline: quadrant routing (cowork vs group task vs long-term vs MetaTask), grilling-style frontier rounds with recommended answers, bot-side fact research, prose-only Q&A, alignment media (prototypes/tables), draft → owner confirms → activate.\n\nUI per the frozen prototype: status-column kanban (needs-you → in-progress → waiting-external → defining → paused → done), cards with sub-project progress bars and next-action lines, detail page with goal / ordered checklist / acceptance criteria / evidence links / event stream / delegate-acceptance switch. The old ledger board is unmounted from the tab (code kept until P2, data untouched).\n\nVerified: renderer tsc + vite build, electron compile, new store tests 10/10, tracked-task suite green. P1 next: heartbeat service with the longterm.advance handler and the bound longterm session type.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}