| Age | Commit message (Collapse) | Author |
|
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
|
|
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
|
|
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
|
|
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
|