feat(dispatch): complete detached multi-device workflows - #1856
Merged
Conversation
bobleer
force-pushed
the
bob/dispatch-completion
branch
from
July 29, 2026 11:48
2f86339 to
fcd54d8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Type and Areas
Type: Feature / UI/UX / docs / test
Areas: Rust core, CLI, desktop/Tauri, server, SSH services, Relay device transport, web UI, i18n
Motivation / Impact
This finishes the work after #1850 so a task can be dispatched to either an SSH host or another signed-in BitFun device and continue after the controller disconnects. Users can choose an existing target directory or send an exact workspace snapshot, supervise permissions remotely, append instructions, and recover observation from another client.
Workspace snapshots are intentionally one-way and immutable: .git metadata is excluded, links and special files are rejected, the target copy becomes authoritative, and there is no implicit live sync or automatic sync-back.
Verification
Manual clean-VM SSH survival and two-device Relay acceptance were not run in this environment because they require external target hosts and accounts.
Reviewer Notes
The exact snapshot contract is bounded at 100,000 entries, 256 MiB per file, 2 GiB uncompressed, and 1 GiB compressed. SSH streams the archive over SFTP; account-device delivery uses bounded encrypted RPC chunks. Materialization is detached and target-side so controller or RPC timeout does not cancel publication.
The target job record is authoritative. Controller-side outbound records are observer projections only, carry independent cursors, and are retained separately.
Checklist