Files
orca/src/main/ssh
OrcaWinandm4air dd87ae578d feat(ssh): remote orcad primitives on the pinned Node runtime (#16741 T6-1) (#24419)
- orcad-remote-runtime-control: the one launch-and-poll-readiness loop that
  deployOrcad and rollbackOrcad now share, plus exec and recovery helpers.
- orcad-remote-record-file: bounded, marker-delimited reads and atomic writes
  for host records. A read that returns no verifiable answer rejects instead
  of reading as "no record".
- The activation record store reads through it (a lost read no longer becomes
  an empty record) and writeOrcadActivationRecord refuses to replace a record
  this client cannot read, such as a newer schema; deploy and rollback use it.
- orcad-active-readiness: prove a recorded-active or relaunched slot against
  the activation gate, reporting exited / unverifiable / rejected.
- orcad-remote-build-hash and orcad-remote-context (host, home, server target
  via orcad-deployment-target, activation record; POSIX-only).
- Readiness reads are capped at 256 KiB, and a finished invalid JSON line is
  malformed rather than pending forever.

Inert: nothing in the app calls managed orcad deploy yet. Ported from #16741
(a68b6f3531) onto main's pinned-Node deploy core; the branch's Bun runtime,
slot eligibility, target detection and bundle installation are superseded by
main's orcad-remote-runtime, orcad-deployment-target and orcad-remote-install.

Co-authored-by: m4air <m4air@m4airs-Air.localdomain>
2026-10-01 11:09:04 -07:00
..