chore: task audit (reconcile open work, demote 2 skill designs)

I reconciled all 11 open tasks against session history and repo state and refreshed their review stamps. I corrected two stale preambles: helper-instance's shipped detection slices, and memories-sync's claim that work was pending when Phases 0-4 had already shipped. The create-documentation and research-writer skill designs drop to [#D]. Both are designed but unbuilt and wait on a real triggering task, so they shouldn't sit at [#C] against active work.

2 files changed, 13 insertions, 13 deletions

diff --git a/.ai/notes.org b/.ai/notes.org
index aae86aa..af1d3c5 100644
--- a/.ai/notes.org
+++ b/.ai/notes.org
@@ -78,7 +78,7 @@ Format:
 
 Markers maintained by workflows to record when they last ran. Read by other workflows that gate their behavior on freshness.
 
-:LAST_AUDIT: 2026-05-28
+:LAST_AUDIT: 2026-06-15
 :LAST_INBOX_PROCESS: 2026-06-15 (3 items: fix-speedrun proposal filed [#C], 2 pearl acks cleared)
 
 Format: one =:MARKER: YYYY-MM-DD= line per workflow. Workflows overwrite their own marker on completion.
diff --git a/todo.org b/todo.org
index 4f88e7a..6c359cc 100644
--- a/todo.org
+++ b/todo.org
@@ -37,7 +37,7 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 ** DOING [#B] Wrap-up inbox/transcript routing to destination projects :feature:spec:
 :PROPERTIES:
 :CREATED: [2026-06-13 Sat]
-:LAST_REVIEWED: 2026-06-13
+:LAST_REVIEWED: 2026-06-15
 :END:
 Optional wrap-up step that surfaces filed keepers belonging to another project, recommends a destination, and batch-moves them into that project's =todo.org= Open Work section (transcript filing deferred to vNext). All six decisions resolved (Reading B: the router acts on session-filed keepers, separate from the inbox gate and from defer-and-stage). Spec ready for review.
 
@@ -46,7 +46,7 @@ Spec: [[file:docs/design/wrapup-routing-spec.org]]. Source proposal: [[file:docs
 ** DOING [#B] Helper-instance support — concurrent same-project Claude :feature:spec:
 :PROPERTIES:
 :CREATED: [2026-06-11 Thu]
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
 SPEC REVIEWED 2026-06-12: [[file:docs/design/2026-05-28-generic-agent-runtime-spec-review.org][Codex review]] now rates Phase 1.5 =Ready with caveats=. Before any build, keep the Emacs integration as a cross-project handoff to =~/.emacs.d=, preserve the three-ring gate (bats → sandbox drills → pilot project), and do not let startup/helper changes reach synced template paths until the live drills pass.
 
@@ -86,9 +86,9 @@ OPEN QUESTION to answer first (Craig, 2026-06-15): doesn't helper-instance suppo
 
 ** DOING [#C] Check that memories are sync'd across machines via git :spec:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
-v1 implemented end-to-end 2026-06-10 (Phases 0-4 below, no-approvals batch). Remaining before DONE: the manual testing and validation child, plus the other personal machines' one-time clone + timer setup (archsetup handoff).
+v1 implemented end-to-end 2026-06-10 (Phases 0-4, all shipped + pushed). Implementation is complete. Remaining before DONE: the manual testing and validation child (below), plus the other personal machines' one-time =roam.git= clone + sync-timer setup (archsetup handoff).
 *** 2026-05-14 Thu @ 19:14:11 -0500 Investigate current memory storage
 
 Memory files live at
@@ -182,15 +182,15 @@ Expected: all four behave per the spec; any miss promotes to a bug task. (Agent-
 ** TODO [#C] Morning ops orchestrator pilot — read-only :feature:
 :PROPERTIES:
 :CREATED: [2026-06-11 Thu]
-:LAST_REVIEWED: 2026-06-11
+:LAST_REVIEWED: 2026-06-15
 :END:
 A scheduled headless morning run chaining the existing pieces: startup checks, the triage-intake scan, a system health check — producing the prep doc plus a report and a notify ping, with all remediation propose-only. Staged adoption from the 2026-06-11 insights report's "Self-Healing Daily Ops Orchestrator": read-only first; promote individual routine remediations to auto only after each has a track record. Known blockers to design around: headless MCP auth (interactively-authenticated servers are absent in cron runs) and the consent boundary (triage Phase D, anything destructive).
 
 The triage limb can reuse triage-intake's *auto mode* (added 2026-06-15, see [[file:.ai/workflows/triage-intake.org]]) — its accumulate-don't-mutate sweep is the propose-only behavior this orchestrator wants. Auto mode itself runs in-session (inherited MCP auth); the orchestrator is the durable headless schedule, so the headless-auth blocker above is the part still on this task to solve.
 
-** TODO [#C] Build =create-documentation= skill for high-quality project/product docs :feature:
+** TODO [#D] Build =create-documentation= skill for high-quality project/product docs :feature:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
 
 Create a Claude skill named =create-documentation= that can plan, write,
@@ -825,9 +825,9 @@ The skill should reject:
   public/library/API docs: =llms.txt= or markdown export is valuable, but normal
   human navigation remains primary.
 
-** TODO [#C] Build /research-writer — clean-room synthesis for research-backed long-form :feature:
+** TODO [#D] Build /research-writer — clean-room synthesis for research-backed long-form :feature:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
 
 Gap in current rulesets: between =brainstorm= (idea refinement → design doc)
@@ -884,7 +884,7 @@ Upstream reference (do not vendor): ComposioHQ/awesome-claude-skills
 
 ** TODO [#D] Revisit =c4-*= rename if a second notation skill ships :chore:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-10
+:LAST_REVIEWED: 2026-06-15
 :END:
 
 Current naming keeps =c4-analyze= and =c4-diagram= as-is (framework prefix
@@ -1030,7 +1030,7 @@ skill should be driven by a concrete contract need, not aspiration.
 
 ** TODO [#C] Token-rotation helper for =@a-bonus/google-docs-mcp= OAuth refresh :feature:quick:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
 
 When a Google refresh token gets revoked (re-grant scopes, removed Connected App, account password reset), recovery is currently manual: run =npx -y @a-bonus/google-docs-mcp= with the right env, follow the URL in a browser, kill the process, base64-encode the new =token.json=, decrypt =secrets.env.gpg=, replace the var, re-encrypt. A small =mcp/refresh-google-docs-token.sh <profile>= would chain that into one command.
@@ -1057,7 +1057,7 @@ Decision (Craig, 2026-05-31): *hold until a token rotation is imminent.* The OAu
 
 ** TODO [#C] Generic agent runtime support — Codex spec v0 :spec:design:
 :PROPERTIES:
-:LAST_REVIEWED: 2026-06-12
+:LAST_REVIEWED: 2026-06-15
 :END:
 Codex drafted a v0 design doc for making rulesets runtime-neutral rather than Claude-Code-specific. Motivating cases: offline operation with a local LLM, and two LLMs running in the same project at the same time without trampling each other's session-context.