fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972

Activity

1. dezren39

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1638
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-j
   • Session / ID: task 10341
   • Found via: queue claim
   • Task: task 10341 (triage for issue fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972, direct execution lane) — verifying the issue at current main and recording the scoped path or blockers on the issue.
   • Expectation: triage findings posted on issue fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972 this shift.
   • Links: issue fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972
5. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
6. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage complete

   • Agent: queue worker (repo-worker-code), lane code-j
   • Session / ID: task 10341
   • Found via: queue claim (coverage-audit requeue)

   Triage of issue #5972 at current main (verified fresh 2026-11-05):

   • Issue fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972 is OPEN (label documentation), the docs-migration stay-until-replaced register item R1. No hard-stop labels. Its exit condition is explicit: the built-in fallback mode ships and is verified in a proxy-down drill, after which the 8 named hatch files become historical copies only.
   • This is not a duplicate of design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697, but its SSH core is owned there. design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697 (OPEN, status/parked under another queue task) is the design for baking the SSH recovery path into the fleet binary — its recorded route is "orchestrate system ssh now, native russh deferred", and its findings establish that the ProxyCommand half already exists as Rust (fleet proxy connect --stdio replaces laptop-proxy-connect.py today). fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972's three SSH files (laptop-ssh.sh, laptop-ssh-real.sh, laptop-proxy-connect.py) are exactly design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697's scope. Implementing a second fallback design from fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972 would fork that work — the implementation path for the SSH portion is design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697's, full stop.
   • The other five files are not SSH: laptop-agent.py / laptop-agent-daemon.py / laptop-agent-broker.py retire via the Rust daemon/client work under design: laptop-agent — resident execution agent on the laptop (replace per-command SSH spawns) #5343 (phase 3, fleet serve laptop-agent / the laptop-agent client domain design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697 names as its sibling), and board-agent.service + its installer are a separate service decision not covered by either design.
   • Interaction with Design: fleet proxy get/put — file transfer over the agent channel #5759 (fleet proxy get/put, triaged earlier today in task 10168): fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972 requires the fallback to cover stdin-pipe transfers because the daemon has no stdin/file channel — that is one of the fallback classes design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697 also lists. Once Design: fleet proxy get/put — file transfer over the agent channel #5759's file RPC ships, the two production scripts driving that requirement (fetch-charge-inputs.py, atlas-backup.py) can re-point to get/put, and the fallback's stdin class shrinks to sudo feeding and ad-hoc pushes. The fallback still needs the class (sudo -S feeding for switch runs has no get/put analogue), so Design: fleet proxy get/put — file transfer over the agent channel #5759 narrows but does not remove the requirement.

   Scoped path / ordering recorded:

   1. SSH fallback mode: implement per design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697's design (system-ssh orchestration in the binary, multiplexing/burst-safe options carried over from laptop-ssh-real.sh) — owned by design: bake the SSH recovery path into the fleet binary — orchestrate system ssh now, native russh deferred #5697's line of work, tracked here for the exit condition.
   2. Agent-trio retirement: per design: laptop-agent — resident execution agent on the laptop (replace per-command SSH spawns) #5343 phase 3.
   3. Board-agent files: separate decision in the docs migration; not silently swept into either implementation.
   4. Proxy-down drill against the shipped fallback (multiplexed exec, a stdin push, a sudo-fed switch) — the drill passing is what closes fleet: built-in fallback connection mode (direct/SSH) when the proxy path is unavailable — replaces laptop-ssh.sh family (docs migration stay-item R1) #5972, not the code landing alone.

   Blockers recorded: sequencing only — #5972 closes last, after #5697's implementation and the drill. No Drew decision is needed at triage. Issue #5972 stays open as the register/exit-condition tracker.
7. dezren39

   added

   status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
8. github-actions

   assigned

   dezren39

   on Nov 5, 2026