deploy(hailo): cross-build script — mention iter-215 ruvllm-bridge installer (iter 225)

iter-215 added `install-ruvllm-bridge.sh` (closing ADR-178 Gap A's
deploy-artifact gap for the third bridge). cross-build-bridges.sh
already cross-compiles `ruvllm-bridge` (line 36's BINS array, since
iter 122/128), but its trailing operator-hint at lines 141-145 only
named the two daemon bridges' installers — operators copying the
hint missed that ruvllm-bridge has its own installer too.

Updated the hint to:
  - List all three installers
  - Note ruvllm-bridge ships no systemd unit (subprocess lifecycle,
    iter-215 design rationale)
  - Use the conventional "pick the bridges you need" phrasing,
    since most deploys won't use all three

Validated:
  - bash -n on the script: parses clean
  - All three install-*.sh referenced exist (iter-216 verified the
    rename + file presence)

Pure deploy-script docs hygiene; no code or unit-file change.

Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
ruvnet 2026-05-03 22:44:50 -04:00
parent f6cae8114c
commit 91c4e79879

View file

@ -138,8 +138,10 @@ echo
echo "Verify on the target:"
echo " ssh root@${DEPLOY_HOST} 'for b in ${BINS[*]}; do /usr/local/bin/\$b --version; done'"
echo
echo "Then install the systemd service (if not already done):"
echo "Then run the matching installer for whichever bridge(s) you ship"
echo "(each is idempotent; pick the bridges you actually need):"
echo " ssh root@${DEPLOY_HOST}"
echo " cd /path/to/ruvector/crates/ruvector-hailo-cluster/deploy"
echo " sudo bash install-mmwave-bridge.sh /usr/local/bin/ruvector-mmwave-bridge # mmwave"
echo " sudo bash install-mmwave-bridge.sh /usr/local/bin/ruvector-mmwave-bridge"
echo " sudo bash install-ruview-csi-bridge.sh /usr/local/bin/ruview-csi-bridge"
echo " sudo bash install-ruvllm-bridge.sh /usr/local/bin/ruvllm-bridge # iter 215 — no systemd unit, parent-spawned"