docs(todo): archive wrap-it-up github task; file Step 3.5 follow-up

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.

1 files changed, 24 insertions, 5 deletions

diff --git a/todo.org b/todo.org
index 343176f..7c4d713 100644
--- a/todo.org
+++ b/todo.org
@@ -7,7 +7,15 @@ Project-scoped (not the global =~/sync/org/roam/inbox.org= list).
 
 * Rulesets Open Work
 
+** TODO [#C] wrap-it-up Step 3.5 assumes GitHub-family remote :chore:
+Triggered by: 2026-05-16 wrap-it-up github.com cleanup (audit of the same file).
+
+Step 3.5 (Linear ticket-state hygiene) at =wrap-it-up.org:207= says "the project's GitHub remote — use =gh pr list ...=". Currently fine in practice: the step is Linear-gated, and the only Linear-using project is DeepSat (on =deepsat.ghe.com=, a GitHub-family host where =gh= works). Would break if a future Linear-using project lived on a non-GitHub host (gitlab, gitea, bitbucket). Either drop the GitHub-family assumption (provider-agnostic lookup, harder) or document the assumption explicitly so future projects know the step needs an update if they don't fit.
 ** DOING [#A] Check that memories are sync'd across machines via git.m
+*** 2026-05-16 Sat @ 01:12:52 -0500 Spec
+#+begin_src cj: comment
+write the spec here. 
+#+end_src
 
 *** 2026-05-14 Thu @ 19:14:11 -0500 Investigate current memory storage
 
@@ -1279,7 +1287,13 @@ new templates, or scope expansions that we'd want to pull in without losing
 our local modifications. A skill should handle this deliberately rather than
 by manual re-cloning.
 
-*** Design decisions (agreed)
+*** 2026-05-16 Sat @ 01:14:40 -0500 Specification
+#+begin_src cj: comment
+write the specification here. 
+#+end_src
+
+*** 2026-05-16 Sat @ 01:14:20 -0500 original goals and decisions
+**** Design decisions (agreed)
 
 - *Upstream tracking:* per-fork manifest =.skill-upstream= (YAML or JSON):
   - =url= (GitHub URL)
@@ -1297,7 +1311,7 @@ by manual re-cloning.
   or corrupt (can't run 3-way merge): write =.local=, =.upstream=,
   =.baseline= files side-by-side and surface as manual review.
 
-*** V1 Scope
+**** V1 Scope
 
 - [ ] Skill at =~/code/rulesets/update-skills/=
 - [ ] Discovery: scan sibling skill dirs for =.skill-upstream= manifests
@@ -1317,7 +1331,7 @@ by manual re-cloning.
 - [ ] On successful sync: update =last_synced_commit= in the manifest
 - [ ] =--dry-run= to preview without writing
 
-*** V2+ (deferred)
+**** V2+ (deferred)
 
 - [ ] Track upstream *releases* (tags) not just branches, so skill can propose
   "upgrade from v1.2 to v1.3" with release notes pulled in
@@ -1332,13 +1346,13 @@ by manual re-cloning.
   =M-x smerge-ediff= as an alternate path for users who prefer ediff over
   per-hunk prompts
 
-*** Initial forks to enumerate (for manifest bootstrap)
+**** Initial forks to enumerate (for manifest bootstrap)
 
 - [ ] =arch-decide= → =wshobson/agents= :: =plugins/documentation-generation/skills/architecture-decision-records= :: MIT
 - [ ] =playwright-js= → =lackeyjb/playwright-skill= :: =skills/playwright-skill= :: MIT
 - [ ] =playwright-py= → =anthropics/skills= :: =skills/webapp-testing= :: Apache-2.0
 
-*** Open questions
+**** Open questions
 
 - [ ] What happens when upstream *renames* a file we fork? Skill would see
   "file gone from upstream, still present locally" — drop, keep, or prompt?
@@ -2159,3 +2173,8 @@ Build a self-contained test harness under =.ai/scripts/tests/= that spins up =/t
 Pattern reference: bats or shell-based assertions (similar to the elisp ERT suites for =todo-cleanup= and =lint-org=, but for shell scripts).
 
 Triggered by: 2026-05-15 fold-epic, child 4 test plan; commits =94782ee= (audit) + =d364cf2= (install-ai).
+** DONE [#A] wrap it up mentions github, which isn't the remote for many projects. :chore:
+CLOSED: [2026-05-16 Sat]
+For many of them, git.cjennings.net mirrors to github.com, and github.com isn't the remote.
+For many others, git.cjennings.net is the remote with no mirror.
+Remove or replace the reference to github.com