chore(ai): archive session record and task-review todo cleanup

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.

1 files changed, 94 insertions, 96 deletions

diff --git a/todo.org b/todo.org
index f6529c2..802f94b 100644
--- a/todo.org
+++ b/todo.org
@@ -7,25 +7,6 @@ Project-scoped (not the global =~/sync/org/roam/inbox.org= list).
 
 * Rulesets Open Work
 
-** DONE [#A] Implement task-review daily-habit per spec
-CLOSED: [2026-05-20 Wed]
-:PROPERTIES:
-:LAST_REVIEWED: 2026-05-20
-:END:
-Spec: [[file:docs/design/task-review.org]]
-
-Retires =wrap-it-up.org='s date-coverage scan and replaces it with a daily list-hygiene review (N=7 oldest-unreviewed top-level =[#A]= / =[#B]= / =[#C]= tasks per session, ~12-day rotation). Built as a pure Claude workflow — Shape B, no elisp; see the spec's Revision section for why the elisp approach was dropped.
-
-Status:
-1. [X] =task-review-staleness.sh= + bats (count + =--list= modes).
-2. [X] =wrap-it-up.org= health check (threshold 30).
-3. [-] =task-review.el= — dropped (Shape B is a pure workflow, not an Emacs mode).
-4. [X] New =task-review.org= workflow + INDEX entry (the existing listing workflow was renamed to =open-tasks.org= to free the name).
-5. [X] Startup nudge in template =startup.org= (threshold 7), not the project-only startup-extras layer.
-6. [X] Smoke test against live =todo.org= — first cycle run 2026-05-20 (7 tasks reviewed: 3 re-grades, 1 cancellation, 1 bump-and-tag).
-
-Triggered by: 2026-05-16 brainstorm on retiring the date-coverage scan.
-
 ** TODO [#A] wrap-it-up Step 3.5 assumes GitHub-family remote :chore:quick:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-20
@@ -1235,83 +1216,6 @@ or compound commands, and can misidentify targets. Use =shlex= for simple
 commands, document unsupported shell constructs, and fail toward asking when a
 destructive pattern is ambiguous.
 
-** CANCELLED [#B] Build =ov-1= skill for DoDAF OV-1 (High-Level Operational Concept Graphic)
-CLOSED: [2026-05-20 Wed]
-
-Cancelled during the 2026-05-20 task review.
-
-Triggered by SOFWeek (May 2026, Tampa) — DeepSat attending; DoD attendees
-may ask for architecture diagrams. OV-1 is the universal informal
-currency in DoD briefings ("show me the architecture" → OV-1 by default).
-
-Priority upgrades to =[#A]= if Craig confirms scenario 2 below (personal
-load-bearing need at the event); stays =[#B]= or drops to =[#C]= if
-scenario 1 (team already covers it, future asset only).
-
-*** Prior art (searched 2026-04-19)
-
-No existing Claude Code skill exists for DoDAF / OV-1 / SV-1 / SysML.
-
-- =anthropics/skills= — 17 skills, zero DoDAF/SysML/defense coverage.
-- =awesome-claude-code= list — zero hits for DoDAF/OV-1/SysML/UAF.
-- =mfsgr/sysml2dodaf= — empty repo (0 stars, no code). Vapor.
-- =HowardKao-1130/mini-NEXEN= — broad SE methodology skill that
-  name-drops DoDAF as a trigger keyword; no artifact generation. 0 stars.
-- =gaphor/gaphor= (Apache-2.0, 2.2k stars) — mature UML/SysML GUI
-  modeler. Not a skill; not a pipeline. Useful reference only.
-
-Nearest prior art to lean on when building:
-- DoDAF 2.02 Viewpoints & Models reference (dodcio.defense.gov) —
-  canonical OV-1 exemplars. Embed 3-5 layouts as skill =references/=.
-- Pattern from existing =c4-diagram= skill — same shape (prose → diagram
-  spec), swap the viewpoint vocabulary to DoDAF.
-- PlantUML for SV-1 (when that skill comes later); Mermaid or draw.io
-  XML for OV-1 lightweight visuals.
-
-*** Build scope (when triggered)
-
-*In scope:*
-- Input: prose description of a system + its operational context.
-- Output: structured OV-1 *spec* — performers, external actors (other
-  systems, forces, adversaries), relationships (data/control flows),
-  narrative captions, classification marking, legend requirements.
-- DoDAF 2.02 completeness checklist as a quality gate — verify the
-  produced spec contains every element a correct OV-1 requires.
-- Optional lightweight visual: draw.io XML or Mermaid approximation for
-  quick review; NOT a finished rendering.
-
-*Out of scope:*
-- Icon libraries, pictorial assets, finished PowerPoint export. OV-1
-  final art belongs to a designer or Craig in Visio/PowerPoint; the
-  skill's job is the spec and the check, not the slide.
-- SV-1, SV-2, UAF, IDEF1X, other viewpoints. Build only when a
-  concrete need triggers each.
-
-Estimate: 4-6 hours.
-
-*** Craig's investigation before kickoff
-
-1. Does DeepSat's systems-engineering or marketing team already have an
-   OV-1 (or the equivalent briefing artifact) for SOFWeek?
-2. If yes (scenario 1) — skill is a future asset, not event-load-bearing.
-   Ship after SOFWeek. Priority drops to =[#C]=.
-3. If no, or if the scenario is "Craig may need to produce/iterate an
-   OV-1 on the fly during the event" (scenario 2) — skill is load-bearing
-   for the event. Priority upgrades to =[#A]=; build before SOFWeek.
-4. Confirm the classification level the skill needs to handle
-   (unclassified-only? or FOUO markings? affects the classification
-   block in the spec).
-5. Confirm the target rendering format DeepSat uses for OV-1
-   deliverables (PowerPoint slide? Cameo? Visio? affects whether the
-   skill emits draw.io XML vs Mermaid vs pure structured spec).
-
-*** Related
-
-See also the DoD-specific notations section under the later TODO
-(=c4-*= rename revisit) — OV-1 is flagged there as the highest-value
-starting point across the DoD notation landscape (SysML, DoDAF/UAF,
-IDEF1X). This entry is the execution plan for that starting point.
-
 ** TODO [#C] Build =/update-skills= skill for keeping forks in sync with upstream
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-20
@@ -2217,3 +2121,97 @@ Fix: extend Phase A's discovery to also scan =claude-templates/inbox/= when the
 Adjacent question worth answering at the same time: should cross-project handoffs file into =./inbox/= at the project root (matching what Phase A already scans), or stay in =claude-templates/inbox/= and rely on the discovery fix? The =inbox-send= script's target-project logic is the place to settle that.
 
 Triggered by: 2026-05-15 evening session, surfaced when committing the test-harness work.
+** DONE [#A] Implement task-review daily-habit per spec
+CLOSED: [2026-05-20 Wed]
+:PROPERTIES:
+:LAST_REVIEWED: 2026-05-20
+:END:
+Spec: [[file:docs/design/task-review.org]]
+
+Retires =wrap-it-up.org='s date-coverage scan and replaces it with a daily list-hygiene review (N=7 oldest-unreviewed top-level =[#A]= / =[#B]= / =[#C]= tasks per session, ~12-day rotation). Built as a pure Claude workflow — Shape B, no elisp; see the spec's Revision section for why the elisp approach was dropped.
+
+Status:
+1. [X] =task-review-staleness.sh= + bats (count + =--list= modes).
+2. [X] =wrap-it-up.org= health check (threshold 30).
+3. [-] =task-review.el= — dropped (Shape B is a pure workflow, not an Emacs mode).
+4. [X] New =task-review.org= workflow + INDEX entry (the existing listing workflow was renamed to =open-tasks.org= to free the name).
+5. [X] Startup nudge in template =startup.org= (threshold 7), not the project-only startup-extras layer.
+6. [X] Smoke test against live =todo.org= — first cycle run 2026-05-20 (7 tasks reviewed: 3 re-grades, 1 cancellation, 1 bump-and-tag).
+
+Triggered by: 2026-05-16 brainstorm on retiring the date-coverage scan.
+** CANCELLED [#B] Build =ov-1= skill for DoDAF OV-1 (High-Level Operational Concept Graphic)
+CLOSED: [2026-05-20 Wed]
+
+Cancelled during the 2026-05-20 task review.
+
+Triggered by SOFWeek (May 2026, Tampa) — DeepSat attending; DoD attendees
+may ask for architecture diagrams. OV-1 is the universal informal
+currency in DoD briefings ("show me the architecture" → OV-1 by default).
+
+Priority upgrades to =[#A]= if Craig confirms scenario 2 below (personal
+load-bearing need at the event); stays =[#B]= or drops to =[#C]= if
+scenario 1 (team already covers it, future asset only).
+
+*** Prior art (searched 2026-04-19)
+
+No existing Claude Code skill exists for DoDAF / OV-1 / SV-1 / SysML.
+
+- =anthropics/skills= — 17 skills, zero DoDAF/SysML/defense coverage.
+- =awesome-claude-code= list — zero hits for DoDAF/OV-1/SysML/UAF.
+- =mfsgr/sysml2dodaf= — empty repo (0 stars, no code). Vapor.
+- =HowardKao-1130/mini-NEXEN= — broad SE methodology skill that
+  name-drops DoDAF as a trigger keyword; no artifact generation. 0 stars.
+- =gaphor/gaphor= (Apache-2.0, 2.2k stars) — mature UML/SysML GUI
+  modeler. Not a skill; not a pipeline. Useful reference only.
+
+Nearest prior art to lean on when building:
+- DoDAF 2.02 Viewpoints & Models reference (dodcio.defense.gov) —
+  canonical OV-1 exemplars. Embed 3-5 layouts as skill =references/=.
+- Pattern from existing =c4-diagram= skill — same shape (prose → diagram
+  spec), swap the viewpoint vocabulary to DoDAF.
+- PlantUML for SV-1 (when that skill comes later); Mermaid or draw.io
+  XML for OV-1 lightweight visuals.
+
+*** Build scope (when triggered)
+
+*In scope:*
+- Input: prose description of a system + its operational context.
+- Output: structured OV-1 *spec* — performers, external actors (other
+  systems, forces, adversaries), relationships (data/control flows),
+  narrative captions, classification marking, legend requirements.
+- DoDAF 2.02 completeness checklist as a quality gate — verify the
+  produced spec contains every element a correct OV-1 requires.
+- Optional lightweight visual: draw.io XML or Mermaid approximation for
+  quick review; NOT a finished rendering.
+
+*Out of scope:*
+- Icon libraries, pictorial assets, finished PowerPoint export. OV-1
+  final art belongs to a designer or Craig in Visio/PowerPoint; the
+  skill's job is the spec and the check, not the slide.
+- SV-1, SV-2, UAF, IDEF1X, other viewpoints. Build only when a
+  concrete need triggers each.
+
+Estimate: 4-6 hours.
+
+*** Craig's investigation before kickoff
+
+1. Does DeepSat's systems-engineering or marketing team already have an
+   OV-1 (or the equivalent briefing artifact) for SOFWeek?
+2. If yes (scenario 1) — skill is a future asset, not event-load-bearing.
+   Ship after SOFWeek. Priority drops to =[#C]=.
+3. If no, or if the scenario is "Craig may need to produce/iterate an
+   OV-1 on the fly during the event" (scenario 2) — skill is load-bearing
+   for the event. Priority upgrades to =[#A]=; build before SOFWeek.
+4. Confirm the classification level the skill needs to handle
+   (unclassified-only? or FOUO markings? affects the classification
+   block in the spec).
+5. Confirm the target rendering format DeepSat uses for OV-1
+   deliverables (PowerPoint slide? Cameo? Visio? affects whether the
+   skill emits draw.io XML vs Mermaid vs pure structured spec).
+
+*** Related
+
+See also the DoD-specific notations section under the later TODO
+(=c4-*= rename revisit) — OV-1 is flagged there as the highest-value
+starting point across the DoD notation landscape (SysML, DoDAF/UAF,
+IDEF1X). This entry is the execution plan for that starting point.