v1.6.0

1.6.0

Added

• Manage OmnyDrive mounts from inside a session with :drive. The new local
  command is the in-session counterpart of the top-level omnyshell drive CLI:
  because the session is already attached to one node, the node is implicit, so
  paths take no <node>: prefix and every operation is scoped to the connected
  node. Subcommands mirror the CLI — :drive ls, :drive mount <local-dir> <remote-path> (or --git <url> <remote-path>, with --rw,
  --no-initial-sync, --name, --branch, --depth), :drive status,
  :drive sync [--push|--pull], :drive resolve [--accept-local|--accept-origin| --reclone], :drive remount, and :drive unmount [--sync-first] [--no-keep-remote]. A mount-id belonging to a different node is refused, and
  mounts share the same on-disk registry as the CLI.
• Background :drive watch. :drive watch <mount-id> [--interval S] [--debounce MS] auto-syncs a mount in the background while the shell stays
  usable, logging each sync above the prompt; :drive unwatch [<mount-id>] stops
  one or all watchers (teardown also runs automatically when the session ends or
  the mount is unmounted). Background output repaints around the input line via a
  new LocalCommandContext.printAbove hook.
• Live drive sync progress. Every drive operation now reports progress as it
  runs instead of only a final count: sync, mount, resolve, remount and
  watch, for both the omnyshell drive CLI and the in-session :drive command.
  The top-level CLI renders an in-place bar
  ([##########----] 71% 5/7 files src/main.dart); in-session prints a
  throttled syncing N/M: path line above the prompt. Per-file granularity for
  directory mounts comes from omnydrive ≥ 1.1.0's per-file ProgressEvents; git
  push/clone show a coarse pushing… / cloning… phase. Threaded through a new
  DriveManager onProgress callback and a SyncProgressBar renderer.