aboutsummaryrefslogtreecommitdiff
path: root/todo.org
Commit message (Collapse)AuthorAgeFilesLines
* docs(todo): add priority and tag schemeCraig Jennings2026-05-281-0/+27
| | | | | | | | | | | | | | | | Adds an explicit [#A]-[#D] legend at the top of todo.org defining what each priority level means in practice. Type and effort tag conventions live alongside, since task-audit enforces both. [#A] now requires a SCHEDULED or DEADLINE date. A task that can't be dated isn't really [#A]. It belongs at [#B]. Tags split two ways. Type tags (:feature:, :chore:, :spec:, :bug:) are mandatory. Effort and autonomy tags (:quick:, :solo:) are optional and orthogonal. Both can apply to the same task. Seeds a Workflow State section in notes.org for the :LAST_AUDIT: marker that open-tasks.org Next Mode reads to decide whether to offer a task-audit run. The marker starts unset. The first task-audit run populates it.
* feat(workflows): backfill iteration history in spec workflowsCraig Jennings2026-05-281-1/+2
| | | | | | Closes the org-drill backfill TODO. Both workflow files now carry a bottom "Review and iteration history" section with four entries: Draft 1 (linear-emacs origin, 2026-05-23, placeholder timestamp), Review-and-Fold (commit 7f2aea1, 2026-05-23), Requirement addition (commit 55adf6e, 2026-05-28), and this backfill commit. Canonical and mirror updated together. Working directory working/spec-workflows-iteration-history-backfill/ removed on this commit. The spec-response cycle on the working draft (two Codex reviews, three rulesets responses) validated the entry-shape and the content before splice. Codex caught file-history conflation that would have made per-file provenance inaccurate. Craig's direct rationale on the Iteration 1 and Iteration 3 Why lines replaced the original INFERRED markers.
* docs(todo): clarify what blocks the iteration-history backfill TODOCraig Jennings2026-05-281-1/+1
| | | | The earlier body listed two reasons to wait: a file-conflict block (correct, since spec-review.org and spec-response.org have uncommitted edits) and a guess that the entry-shape spec might still change (inference without evidence). The revised dependency drops the guess. The read-only research portion can run in parallel without touching the files.
* chore(intake): file org-drill iteration-history backfill as TODOCraig Jennings2026-05-281-0/+17
| | | | The org-drill inbox asks rulesets to backfill =Review and iteration history= sections on spec-review.org and spec-response.org. It lands as a follow-up TODO because the requirement itself is still being established in uncommitted WIP.
* chore(intake): file pearl pattern-catalog and codex runtime spec as TODOsCraig Jennings2026-05-281-0/+33
| | | | Moved three inbox notes into docs/design/ so the task body links survive: pearl's two pattern-catalog handoffs and codex's v0 generic-agent-runtime spec. Added two corresponding TODOs under Rulesets Open Work, both [#C].
* chore(todo): full review pass — re-stamp, drop stale schedules, refresh ↵Craig Jennings2026-05-261-20/+19
| | | | | | daily-prep task Walked all 14 open tasks. Re-stamped LAST_REVIEWED to 2026-05-26, dropped the past SCHEDULED dates from the research-writer and Skill-Seekers wait-for-trigger tasks, tagged the Makefile consolidation :quick:solo:, and refreshed the daily-prep delegation task to reflect the triage-intake engine/plugin split.
* chore(todo): add coverage-summary language-bundle taskCraig Jennings2026-05-251-0/+29
|
* chore(todo): review and stamp ten stale tasksCraig Jennings2026-05-251-3/+33
| | | | Re-grade /research-writer to [#C] (deferred until a real research-writing task triggers it) and tag the two MCP tasks :solo:quick:. The rest confirmed as-is.
* chore(ai): archive session record, regen lint follow-ups, fix dangling todo linkCraig Jennings2026-05-241-1/+1
| | | | The claude-memory clone was removed this session, so the todo entry's file: link to it would dangle — switched to plain text.
* chore(todo): reopen memory-sync task after reversing the migrationCraig Jennings2026-05-241-2/+4
|
* chore(todo): close cross-machine memory sync via dedicated repoCraig Jennings2026-05-231-3/+7
| | | | I closed the memory-sync task. Memory now lives in a dedicated private claude-memory.git on cjennings.net, with each project's memory dir symlinked into a local clone so new memory lands in the working tree and a push syncs it. I settled on that over stow/dotfiles and over keeping it in rulesets, since rulesets sits on every session's startup-pull path and memory churn would dirty it. The task's dated entries carry the decision and the shipped details.
* chore(ai): archive session record, sweep completed tasks, queue follow-upsCraig Jennings2026-05-221-460/+455
| | | | Archived the session record. Moved six completed tasks from Open Work to Resolved: the 2026-05-04 audit-pass parent, the two commits.md overlay tasks, the make-remove feature, the mcp/ install-pipeline doc, and the wrap-it-up GitHub-host quick fix. Queued the one lint judgment and the task-review staleness note in the inbox for next-session processing.
* chore(todo): close the mcp/ install-pipeline doc itemCraig Jennings2026-05-221-1/+3
|
* chore(todo): close make-remove and audit-parent itemsCraig Jennings2026-05-221-3/+8
|
* chore(todo): close the two commits.md overlay tasksCraig Jennings2026-05-221-7/+7
|
* chore(todo): promote the two deferred commits.md audit items to top-level tasksCraig Jennings2026-05-221-15/+12
|
* chore(todo): close brainstorm audit itemCraig Jennings2026-05-221-6/+3
|
* chore(todo): close playwright networkidle + emoji audit itemsCraig Jennings2026-05-221-13/+6
|
* chore(todo): close hooks code audit itemsCraig Jennings2026-05-221-13/+6
|
* chore(todo): close hooks README audit itemCraig Jennings2026-05-221-5/+3
|
* chore(todo): close verification/testing/subagents audit itemsCraig Jennings2026-05-221-21/+12
|
* chore(todo): close language-ruleset audit itemsCraig Jennings2026-05-221-24/+12
|
* chore(todo): close architecture audit itemsCraig Jennings2026-05-221-45/+24
|
* chore(todo): close branch-workflow and c4 audit itemsCraig Jennings2026-05-221-36/+18
|
* chore(todo): close v2mom, prompt-engineering, and codify audit itemsCraig Jennings2026-05-221-36/+18
|
* chore(todo): close frontend, security, and pairwise audit itemsCraig Jennings2026-05-221-44/+18
|
* chore(todo): close add-tests audit items (1 fixed, 1 moot)Craig Jennings2026-05-221-12/+6
|
* chore(todo): close debugging-skills audit itemsCraig Jennings2026-05-221-17/+9
|
* chore(todo): close playwright headed/headless itemCraig Jennings2026-05-221-6/+3
|
* chore(todo): close PR-response audit items (2 fixed, 2 moot)Craig Jennings2026-05-221-24/+12
|
* chore(todo): close review-code CI-trust and CLAUDE.md-citation itemsCraig Jennings2026-05-221-15/+7
|
* chore(todo): close GH-assumption and review-code strengths tasksCraig Jennings2026-05-221-5/+5
|
* chore(ai): archive session record and task-review todo cleanupCraig Jennings2026-05-201-96/+94
| | | | Archive the DONE task-review implementation and the cancelled OV-1 skill from Open Work to Resolved. The follow-ups file picks up one lint judgment and the review-habit staleness line for the next daily-prep.
* chore(todo): close the task-review implementation as doneCraig Jennings2026-05-201-2/+3
| | | | The habit is built and smoke-tested — the staleness script with count and --list modes, the wrap-up health check, the task-review workflow, and the startup nudge all shipped, and the first review cycle ran clean against the live list. The elisp component was dropped under Shape B. The daily habit carries on through the startup nudge and the wrap-up watchdog.
* chore(todo): re-grade and prune tasks in a review passCraig Jennings2026-05-201-5/+26
| | | | This is the first task-review cycle. I re-graded create-documentation, the 2026-05-04 audit review pass, and /update-skills from [#A] to [#C]; bumped the wrap-it-up GitHub-remote chore to [#A] and tagged it :quick:; and cancelled the OV-1 DoDAF skill. The kept and re-graded tasks get a :LAST_REVIEWED: stamp so the staleness watchdog and the rotation know they've been looked at.
* docs(design): record task-review Shape B revisionCraig Jennings2026-05-201-8/+9
| | | | | | The spec recommended an Emacs keystroke mode (task-review.el). Implementation went the other way — a pure Claude workflow, no elisp — because the interactive mode would couple a rulesets-owned file to archsetup's init.el, and the daily Claude touchpoint already exists in daily-prep. I added a Revision section at the top recording the change: pure workflow, rulesets-owned, the task-review.org / open-tasks.org name swap, the staleness --list selection, and the startup nudge promoted to template-level. The elisp architecture and ERT sections stay as a record of the abandoned approach, flagged superseded. The todo task moves to DOING with per-component status: everything but the smoke test is done, and component 3 (the elisp) is dropped.
* chore(ai): archive session record and wrap-up lint followupsCraig Jennings2026-05-191-13/+12
| | | | Records this session's process-rule additions (Discovery check in commits.md Step 1; mechanical primary trigger for session-context writes), ai launcher polish (per-project opening line + explicit end-of-session window placement), and the new triggers.md for cross-project launch phrases. Lint-followups carries the recurring misplaced-heading judgment at line 2143 (false positive: `**` inside `=...=` verbatim, leave alone) plus a date-coverage list, both deferred per the task-review spec.
* chore(todo): close Phase A inbox-blind-spot task as mootCraig Jennings2026-05-191-1/+4
| | | | | | The bug was real on 2026-05-15 but is moot in current state. inbox-send.py's discovery scans ~/code/* and ~/projects/* single-level, so claude-templates/ (two levels under ~/code/) is never routable as a target. The 2026-05-15 incident was a one-time manual workaround because rulesets/inbox/ didn't exist yet; 470085f added that root inbox and the same session removed claude-templates/inbox/. Nothing routes to the subtree inbox now, and the subtree inbox doesn't exist. Phase A scanning only ./inbox/ is correct given current state. No code change needed; this is just a depth-based completion flip per the todo-format convention.
* docs(design): task-review spec + filed [#A] taskCraig Jennings2026-05-161-0/+14
| | | | | | docs/design/task-review.org captures the brainstorm output for a daily 5-min keystroke-driven review habit that walks 7 oldest-unreviewed top-level [#A]/[#B]/[#C] tasks per session, rotating through the list over ~12 days. Replaces wrap-it-up.org's date-coverage scan once implemented; the watchdog flips from "do all priorities have dates?" to "is the review habit happening?" with a 30-day threshold. todo.org gets a [#A] entry at the top of Rulesets Open Work pointing at the spec, so the implementation work isn't lost. Six components in the spec's Next Steps: extract task-review-staleness.sh, replace the wrap-up section, author task-review.el in archsetup, author the workflow file plus INDEX entry, add the startup nudge, smoke test.
* docs(todo): archive wrap-it-up github task; file Step 3.5 follow-upCraig Jennings2026-05-161-5/+24
| | | | | | | | | | todo.org bookkeeping for the night: - Wrap-it-up github task moved to Rulesets Resolved by archive-done (CLOSED 2026-05-16 Sat). The fix shipped in 7121a88. - New [#C] filed: wrap-it-up Step 3.5 assumes GitHub-family remote. Triggered by the same-file audit during tonight's start-work. Step 3.5 says "the project's GitHub remote — use gh pr list ..." which is generic GitHub (not github.com literal) but still bakes in a host-family assumption that would break on a future non-GitHub Linear project. Currently fine for DeepSat-on-GHE. - Spec stubs added under DOING memory-sync and TODO /update-skills: placeholders for cj: comment blocks to fill in during the next session on each. Date-coverage scan flagged 8 [#A] / [#B] tasks lacking DEADLINE or SCHEDULED; appended to lint-followups for morning review.
* chore(ai): wrap stale-cleanup + bats harness for audit/install-aiCraig Jennings2026-05-151-47/+44
| | | | Two arcs this session: closed two stale todo entries (/lint-org retroactively, pull-ordering doc proactively after writing the missing protocols.org paragraph), then built scripts/tests/audit.bats and scripts/tests/install-ai.bats covering the three deferred destructive edges from yesterday's fold-epic test plan. A dotemacs cross-project handoff for a cj-scan nested-fence bug landed during commit staging and shipped as its own commit, separate from the test-harness work. archive-done moved three DONE level-2 entries to Rulesets Resolved.
* docs(todo): close test harness; file Phase A inbox-scan bugCraig Jennings2026-05-151-1/+12
| | | | Flipped the test harness task at line 1766 to DONE (work landed in 7ef200a). Filed a new [#B] for a fold side-effect surfaced during the publish flow: Phase A's inbox check at startup.org:107 only looks at the project root, so it never scans claude-templates/inbox/ (the canonical's inbox, now in-repo after the subtree merge). This session received a cross-project handoff there at startup and missed it entirely; the drift surfaced only during commit staging.
* fix(cj-scan): suppress detection inside nested non-cj begin_* blocksCraig Jennings2026-05-151-0/+27
| | | | | | cj-scan.py matched =#+begin_src cj:= / =#+end_src= line-by-line without awareness of enclosing block scopes. A cj fence embedded inside =#+begin_example= (typical when documenting what the <cj yasnippet emits) or =#+begin_src snippet= (the yasnippet definition itself) was misclassified as a live cj annotation. Two false positives surfaced from a /respond-to-cj-comments run against an org file with yasnippet docs. Track an active wrapper_type. When the scanner sees =#+begin_<type>= for any type other than cj: (the cj-open regex is checked first), enter a wrapper state where every line is content until the matching =#+end_<type>= closer fires. Inside a wrapper, both fence patterns and legacy inline cj: lines stay suppressed. Added the TestCjScanNestedFencesIgnored class with 6 tests: nesting inside example, src <other-lang>, and quote; regression guards for clean wrapper close and unclosed-wrapper non-swallow. Canonical pytest: 302 passed, 1 skipped.
* docs(todo): close /lint-org and pull-ordering doc tasksCraig Jennings2026-05-151-18/+10
| | | | /lint-org at line 1292 shipped on 2026-05-14 but never got flipped. The pull-ordering doc task at line 36 shipped partially earlier (Phase A.0 wired in the 2026-05-15 fold) and just got its protocols.org paragraph in the previous commit. This commit rewrites the body to reflect what actually landed and flips it to DONE.
* chore(ai): wrap fold-claude-templates + audit/install-ai + ratio migrationCraig Jennings2026-05-151-175/+173
|
* docs(todo): close consolidate .ai/ template infra epic; ratio migratedCraig Jennings2026-05-151-2/+4
|
* docs(start-work): encode follow-up filing placement rulesCraig Jennings2026-05-151-1/+2
| | | | | | Phase 4 step 5's "Disposition for each candidate" now spells out where to file a "file a ticket" follow-up in todo.org: siblings for epic-style parents (level-2 with level-3 children), new level-2 entries for standalone tasks. Both cases require a "Triggered by:" line so a future reader sees the origin. The placement rule lived in project memory but didn't propagate across projects. Encoding in start-work makes it cross-project default behavior.
* docs(todo): mark fold-epic children 1-3 done (audit, install-ai, fold), ↵Craig Jennings2026-05-151-3/+6
| | | | child 5 awaits ratio
* feat(make): add catchup-machine target for cross-machine .ai/ syncCraig Jennings2026-05-151-1/+1
| | | | | | | | scripts/catchup-machine.sh runs the four steps that bring a machine in sync with rulesets canonical: git pull, make install (symlink refresh), make audit APPLY=1 (rsync .ai/ across all projects), and make doctor (verify). Idempotent, safe to re-run any time. Built for the post-fold ratio migration but applies generally: after a fresh rulesets clone on a new machine, or whenever the canonical source has advanced since last sync. Handles dirty working trees by skipping the pull and surfacing a warning; user commits or stashes before re-running.
* docs(todo): close fold-epic test plan, file edge-case follow-upCraig Jennings2026-05-151-1/+16
| | | | Audit and install-ai both pass their core test paths (report-only, --apply convergence, idempotency, fresh install, refusal-on-existing, GITIGNORE mode, doctor 36/0/0, pytest 296+1 skipped). Three destructive edge cases (--force on dirty, missing .ai/ FAIL, install-ai fzf-pick form) were deferred to a [#C] sibling task that proposes a self-contained test harness rather than running them against real projects.