- SPEC.md: retitled from 'v1 Draft' to a living-document status line;
added missing Schema Reference sections for gtd-kanban (2.3) and
gtd-matrix (2.4, both modes) — previously undocumented outside the
roadmap; added unscheduled-todos/unscheduled-notes to the calendar
table; rewrote Rendering (§4) and Architecture (§5) to reflect the
three-block pipeline, shared collectors, and tag-fetch machinery;
corrected v0.2.0 roadmap heading (recurrence shipped, strip horizon
was not built — previously overclaimed)
- New CHANGELOG.md: one entry per shipped version, 0.1.0 through 0.5.0
- README.md: fixed stale test count (47 -> 88), linked CHANGELOG, added
a 'Cutting a release' checklist including the npm whoami / E404
auth-expiry gotcha hit across several publishes
- No source changes; 88 tests still passing
- New default mode 'skeleton': rows = active (in-progress tag, shared
with the kanban); columns = due soon (due date within urgent-window
days, overdue included, or the urgent tag as manual override)
- Quadrants: Do Next / Scheduled / On Deck / Backlog — no 'Eliminate';
a committed vault needs when-and-what's-moving, not triage
- in-progress + urgent + dateless -> Do Next (urgent is the override)
- Dateless active work -> Scheduled; completed to-dos still excluded
- mode: eisenhower preserves the classic (urgent/important tags)
- MatrixBoard now positional (topLeft..bottomRight); per-mode labels
travel in the payload; rendering fully shared between modes
- New options: mode, in-progress-tag, urgent-window (default 3)
- Version 0.5.0; 8 new tests (88 total); README + SPEC updated
- New gtd-matrix block: 2x2 prioritisation grid with axis headers
(Urgent / Not urgent x Important / Not important)
- Quadrants from two configurable tags (urgent-tag default 'urgent',
important-tag default 'important'): both -> Do First; important ->
Schedule; urgent -> Delegate; neither -> Eliminate (default bucket)
- Completed to-dos excluded entirely (prioritisation view, not tracking;
kanban Done is where completions live); to-dos only; matrix note
excluded; warns when both axis tags are identical
- Same scope/todos/sort-type/sort/card-detail options as kanban; cards
reuse kanban rendering (compact, recurrence mark, drilldown)
- Quadrant colour accents: red Do First, blue Schedule, amber Delegate,
grey Eliminate
- SPEC roadmap restructured: matrix shipped as v0.4.0 (views axis);
drag-and-drop + create-from-view clustered as the v0.5.0+ authoring
epic with multi-board refresh and trigger/target questions recorded
- Version 0.4.0; 11 new tests (80 total); README documented
Sets expectations clearly: the plugin is desktop-only (custom code-block
rendering + webview messaging aren't reliably supported on mobile), but
the underlying to-dos sync and appear in Joplin's native mobile views.
- Detect recurrence via the 'recurring' tag maintained by the Repeating
To-Dos plugin (v2 stores recurrence in userData, not the note body, so
tag-presence is the correct signal — not body scanning)
- DataAdapter gains getNoteTagTitles; lookup runs for to-dos only (notes
can't recur), keeping extra API calls minimal
- GtdEvent.isRecurring threaded through collector and payload
- Webview shows ↻ to the right of any icon/glyph across all views:
strip tiles, hover-card rows, month-grid chips, unscheduled chips
- RECURRING_TAG constant leaves room for a future configurable tag name
- README documents the pairing; SPEC roadmap marks Option A shipped
- Version bumped to 0.2.0; 2 new tests (49 total)
- README rewritten for end users: quick start, full option reference for
both blocks, date-resolution rules, drilldown, limitations, credits
- Four screenshots added under docs/screenshots/
- SPEC.md remains the design/developer document, linked from README
