Wayfork 0.9.0 — wayforkctl for scripts and assistants

wayforkctl for scripts and coding assistants (F21) and the Windows fixes from the Discord
voice session (issues #1, #2). Pre-release like 0.8.0: covered by the test suites only;
the live check of the macOS control socket and the Windows PC run are still owed.

Added

• wayforkctl for scripts and coding assistants (F21). macOS: logs reads the app's
  log files with --source/--level/--grep/--since/--tail/--json filters and server
  addresses redacted, and works with the app quit. status, failed and rules read
  the running app. rules add|remove and log-level change it through its control
  socket (~/Library/Application Support/Wayfork/control.sock, owner only), and every
  change is undone unless wayforkctl confirm follows within --confirm-within seconds
  (default 60), also across an app crash. reconnect restarts one tunnel. Release
  builds ship the binary in Contents/Resources/bin. Windows: wayforkctl logs with the
  same filters.

• wayforkctl connections and explain (Windows). Read-only diagnostics on the
  service pipe: connections lists every connection sing-box's Clash API currently
  reports — exit, matched rule, upload/download, and a one-way-UDP flag per connection —
  with --process/--exit/--udp/--one-way filters; explain --process <path> | --host <h> | --ip <a> says which rule the applied plan would take, in route order.
  diagnostics gained --tail N to override its default 200-line log cap (capped at
  5000). Same pipe ACL as every other method; no secrets in the replies.

Fixed

• App rules survive an auto-update. A rule pointed at a Squirrel or MSIX versioned
  install folder (app-<ver>, WindowsApps\<Name>_<ver>_<arch>__<hash>) stopped matching
  the moment the app updated into a new one (Discord, Slack, …). The rule now matches any
  version of that install, its stored path follows the newest build, and adding the newer
  .exe again is recognized as the same rule (Windows).