sessionpipe-gui v0.4.0

Added

• sessionpipe 0.10.0. A machine in inherit mode (no permission flag: its agents run
  as your own sessions there do, whatever their settings allow) shows as that, with one
  line saying what it means, on Machines, the pairing page and the New session picker,
  never as safe or auto; the well-known says control.inherit: true, so a 0.10.0 machine
  may pair or switch to inherit with this receiver. New session there defaults to "As your
  own sessions on this machine", which is sent as no level at all, and offers Read only
  and Safe; nothing wider is offered or queued there, and inherit is never signed. An
  ack's applied: inherit reads "As your own sessions".
• A session waiting on its own background work (turn.ended.background) stays
  working, "waiting on 2 background tasks", until it wakes, instead of going idle.
• Unattended runs (session.attended: false): a short one is drawn quiet on the board
  ("unattended"), and no unattended run raises a banner or a notification; absent is
  unknown and changes nothing.
• Who submitted a turn (turn.started.submitted_by): a scheduled, loop or system turn
  says so under its prompt and on its row while it runs; an injected turn (a task
  notification) never becomes the row's last ask.
• Accounts named by host (an API home, api.z.ai): kept from the hello's accounts
  without an email and listed on Machines.
• ACP agents: labels and monograms for the ACP registry's harness names, Machines lists
  what a daemon can start, New session offers them with no permission or model pickers,
  and a start delivered over api says "Ran on …" with its reply.
• Demo mode pairs two machines: studio-mac on 0.10.0 in inherit mode (goose among its
  agents, an api.z.ai account, a start it ran over ACP) and build-box on 0.9.0, and plays
  background work, a scheduled turn and a short unattended run.

Changed

• The hello's home is gone (0.10.0 sends none). A start's folder may be ~/… where the
  machine's hello has start and this receiver's sessionpipe-core takes one (feature
  detected, server/control/tilde.ts); otherwise folders stay absolute, from the
  machine's folders.

• The receiver's second look at a command follows 0.10.0: the closed field set per kind,
  files on a prompt only for a machine that says prompt_files, and a level at most Safe
  on an inherit machine. A hello keeps up to 64 harnesses.

• The Mac app sends. The macOS release carries its Touch ID signer: a key in the
  Mac's Secure Enclave signs new sessions, prompts and permission answers, from the window
  and from a notification's Allow, Deny and Reply. Set it up once with Sign with Touch
  ID (on Machines, a session's composer or Settings › App › Signing): a browser or phone
  the machine already trusts approves the Mac with its passkey, and then one Touch ID a
  day unlocks sending. It needs a receiver whose sessionpipe-core verifies device keys and
  a machine that takes them (sessionpipe 0.10). The release needs no new entitlement.

• Where the app can't send, it says exactly why, with the next step: this build has no
  signer (Linux, Windows, a dev build), the receiver can't check the Mac's key yet (update
  sessionpipe-gui), the machine predates device keys (update sessionpipe there), or the
  Mac isn't set up for that machine yet (Sign with Touch ID). Notifications offer Allow,
  Deny and Reply only once the Mac holds a key for that receiver.