chore(tasks): record the clone decision and move the ribbon deadline

The shallow-clone task now records why I settled the remote-URL half as I did, and the two options I turned down. Without that written down I'll relitigate it the next time I look at the https default and think detection would be tidier. The personal-ISO half is noted on the secrets task that will carry it.

The input-cover ribbon reseat moves to 2026-08-26. It needs the machine open on a bench and I'm away until then.

1 files changed, 43 insertions, 1 deletions

diff --git a/todo.org b/todo.org
index af8d75a..d43dc3b 100644
--- a/todo.org
+++ b/todo.org
@@ -179,7 +179,7 @@ sometimes (every failed lookup, which is occasional rather than constant) = P3 =
 [#C].
 
 ** TODO [#A] Reseat velox input-cover ribbon — phantom power button :bug:velox:hardware:
-DEADLINE: <2026-08-14 Fri>
+DEADLINE: <2026-08-26 Wed>
 :PROPERTIES:
 :CREATED: [2026-08-13 Thu]
 :LAST_REVIEWED: 2026-08-13
@@ -510,6 +510,18 @@ override already exists (=DOTFILES_REPO=, documented in
 lives: a config the personal ISO bakes in, a post-install step, or a detection
 that prefers ssh when a key is present. Craig's call.
 
+*Decided 2026-08-19: the ISO bakes the value, and a check nets the rest.*
+=archsetup:240= has the identical default for =archsetup_repo=, so this was
+always two repos rather than one. I ruled out detection — archsetup never
+restores =~/.ssh=, so key-presence at clone time depends on ordering it
+doesn't control, and "any key means ssh" would break a stranger who has an
+unrelated one. I ruled out a bare post-install step for the reason this whole
+class of bug exists: manual steps don't get run, which is why this sat four
+days. So the personal ISO carries =ARCHSETUP_REPO= / =DOTFILES_REPO= in the
+ssh form (noted on the secrets/ISO task), and =post-rebuild-check= check 8
+flags any working repo still on the read-only endpoint — covering curl|bash
+and stock-ISO installs, which the ISO value cannot reach.
+
 Repair on a machine already built: =git fetch --unshallow= in each repo, and
 =git remote set-url origin git@cjennings.net:<repo>.git= for dotfiles.
 
@@ -523,6 +535,16 @@ Not :solo:. The depth half is (two lines plus tests in the existing
 carries no =--depth= for these two repos). The remote-URL half needs the
 decision above, so the task as a whole waits on it. Split it in two if the
 depth fix is wanted sooner.
+*** 2026-08-19 Wed @ 23:05:00 -0700 Dropped --depth from both user-repo clones
+=archsetup:1462= and =:1475= now clone full history;
+=tests/installer-steps/test_clone_user_repos.py= covers it with 8 cases, and
+one of them asserts the AUR build clones still carry =--depth 1= so the fix
+can't be over-applied by a careless repo-wide sed. Both my repos on velox were
+already unshallowed by hand last session, so this is prevention rather than
+repair.
+*** 2026-08-19 Wed @ 23:05:00 -0700 Settled the remote-URL half and netted it
+See the decision recorded above. The ISO half is a note on the secrets/ISO
+task; the net is =post-rebuild-check= check 8, which ships now.
 ** TODO [#B] post-rebuild-check needs a reference-host mode :feature:velox:solo:
 :PROPERTIES:
 :CREATED: [2026-08-17 Mon]
@@ -758,6 +780,26 @@ archangel+archsetup ISO that's already ~80% built. Two ISO modes: generic
 don't start the migration until the credentials are rotated. Not started.
 Not :solo: — repo standup and history rewrite are Craig's calls; promote to a
 real spec (spec-create) when work resumes.
+
+*Also bake the push-capable repo URLs into the personal ISO* (decided
+2026-08-19). =archsetup:240= and =:245= default =archsetup_repo= and
+=dotfiles_repo= to =https://git.cjennings.net/...=, the anonymous read-only
+endpoint. That default is right for a stranger installing archsetup — no key on
+the server — and wrong for my machines, which have to push: velox came back
+from its rebuild unable to push either repo, and I only found out at a 403 four
+days later. I decided against detecting an ssh key in the installer, because
+archsetup never restores =~/.ssh= (I do that by hand), so key-presence at clone
+time depends on ordering the installer doesn't control, and a naive "any key
+means ssh" would break a stranger who happens to have one. The override already
+exists and is documented — =ARCHSETUP_REPO= / =DOTFILES_REPO= in
+=archsetup.conf.example= — so the personal ISO just needs to carry the ssh
+form of both, alongside the secrets bundle. The generic ISO keeps the https
+default untouched.
+
+The gap that leaves is a curl|bash or stock-ISO install, which takes the https
+default straight back. =post-rebuild-check= check 8 covers that path — it flags
+a working repo whose origin is the read-only endpoint — so the ISO value is the
+fix and the check is the net under it.
 ** TODO [#B] Settings toggles reset silently at session start :bug:dotfiles:
 :PROPERTIES:
 :CREATED: [2026-07-28 Tue]