chore(todo): tag solo-capable tasks and record their decisions

Reviewed the open-task list for solo-ness (whether I can complete a task end to end and verify it without input). Tagged seven :solo: — five that already qualified (workflow test harness, daily-prep delegation, rule-duplication audit, .aiignore, coverage-summary) and two unblocked by a decision today: the category-3 rule copies (leave team-tree copies alone, don't reach into team repos) and the token-tier pilot (approved the four-lane structure for both startup.org and triage-intake.org). The google-docs token-rotation helper stays unmarked, held until a real rotation lets me write and verify in one pass. Each decision is recorded in its task body.

1 files changed, 13 insertions, 7 deletions

diff --git a/todo.org b/todo.org
index b6cde8c..5f5597b 100644
--- a/todo.org
+++ b/todo.org
@@ -1072,7 +1072,9 @@ rm /tmp/secrets.env.tmp
 
 The flow tonight worked but took a handful of manual steps. One script collapses it.
 
-** TODO [#C] Decide on category-3 rule copies in the deepsat tree :chore:quick:
+Decision (Craig, 2026-05-31): *hold until a token rotation is imminent.* The OAuth re-grant is a browser step that can't be triggered without revoking a live token, so the script can't be verified in isolation. Not marked =:solo:= — when a token actually needs rotating, write and verify in one pass (solo at that point).
+
+** TODO [#C] Decide on category-3 rule copies in the deepsat tree :chore:quick:solo:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28
 :END:
@@ -1084,7 +1086,9 @@ While symlinking personal-project =.claude/rules/= mirrors to the rulesets canon
 
 For each: read the file, diff against the rulesets canonical, decide whether it's an intentional diverge (leave alone), stale (sync content), or should canonicalize (replace with symlink and accept the cross-repo dependency). The orchestration_dashboard_mvp pair is the project where Vrezh's PR review surfaced this whole thread, so any decision there has team-visibility implications.
 
-** TODO [#C] Audit language-specific rule files for cross-project duplication :chore:
+Decision (Craig, 2026-05-31): *leave team-tree copies alone.* Personal rulesets does not reach into team repos — canonicalizing would create a cross-repo dependency on the private rulesets, and the orchestration_dashboard_mvp copy is team-visible. This makes the task solo: diff each copy against canonical, record whether it's identical / drifted / overridden in the disposition, and close as "left alone (team-owned)" without modifying the team-tree files.
+
+** TODO [#C] Audit language-specific rule files for cross-project duplication :chore:solo:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28
 :END:
@@ -1097,7 +1101,7 @@ The four canonical rules (=commits=, =testing=, =verification=, =subagents=) are
 
 The Elisp pair is the most suspicious — three repos using essentially the same rules. Audit: diff these across the projects, check for drift, then decide whether to canonicalize them under =~/code/rulesets/claude-rules/languages/<lang>/= and symlink, or leave them as project-local.
 
-** TODO [#C] Refactor =daily-prep.org= to delegate to =triage-intake.org= for the triage section :chore:
+** TODO [#C] Refactor =daily-prep.org= to delegate to =triage-intake.org= for the triage section :chore:solo:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28
 :END:
@@ -1112,7 +1116,7 @@ Scope:
 
 Origin: came up while authoring =triage-intake.org= on 2026-05-11; body refreshed after the engine/plugin refactor on 2026-05-26.
 
-** TODO [#C] Templatize =make coverage-summary= into the language bundles :feature:
+** TODO [#C] Templatize =make coverage-summary= into the language bundles :feature:solo:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28
 :END:
@@ -1272,7 +1276,7 @@ Three wins: handoff is one paste not a re-read; forces specs to be implementable
 
 If the spec lacks an =Implementation phases= section, the step is the prompt to ask the author to add one before =Ready=.
 
-** TODO [#C] Add =.aiignore= for agent inventory exclusions :chore:
+** TODO [#C] Add =.aiignore= for agent inventory exclusions :chore:solo:
 :PROPERTIES:
 :CREATED: [2026-05-28 Thu]
 :LAST_REVIEWED: 2026-05-28
@@ -1284,7 +1288,7 @@ Scope: add a shared =.aiignore= file (or =rulesets-ignore.json= if a more struct
 
 Keep the lockfile policy explicit: ignored when a local skill dependency cache, tracked when reproducibility matters.
 
-** TODO [#C] Workflow test harness — drift + integrity tests :feature:
+** TODO [#C] Workflow test harness — drift + integrity tests :feature:solo:
 :PROPERTIES:
 :CREATED: [2026-05-28 Thu]
 :LAST_REVIEWED: 2026-05-28
@@ -1303,7 +1307,7 @@ Scope: add =scripts/tests/workflow-integrity.bats= (or pytest equivalent) verify
 
 Wire into =make test=. Run on the canonical =claude-templates/.ai/workflows/= as the source of truth.
 
-** TODO [#C] Token-tier pilot on largest workflows :feature:
+** TODO [#C] Token-tier pilot on largest workflows :feature:solo:
 :PROPERTIES:
 :CREATED: [2026-05-28 Thu]
 :LAST_REVIEWED: 2026-05-28
@@ -1318,6 +1322,8 @@ Apply a standardized section structure to the largest workflow files first — =
 - *Reference* — examples, edge cases, rationale, old decisions.
 - *History* / *Design Notes* — durable context not needed every run.
 
+Decision (Craig, 2026-05-31): *approved the four-lane structure (Summary/Execution/Reference/History) and the scope — restructure both =startup.org= and =triage-intake.org= now.* Makes the task solo: apply the lanes to both, preserving every existing instruction (reorganize, don't rewrite), verify the workflows still read coherently and the drift/integrity checks pass.
+
 Teach startup/routing to read =Summary= only at routing time, then =Execution= only for the selected workflow. Other sections become opt-in.
 
 After the pilot, evaluate: did the savings show up in real session token use? Did the structure constrain the workflow expressiveness too much? If yes to savings and no to constraint, expand to the next-largest workflows. If not, document why and stop. Don't templatize universally — shorter workflows don't need tiering.