0.1.10-beta4

The remote Copilot goal-delivery fix.

A fresh Copilot loop in an SSH remote repository booted to an idle screen with its goal never delivered. Root cause, measured against a live TUI: an unattended Copilot queues its --interactive goal behind a per-session folder-trust dialog nobody is present to answer — and --yolo does not cover folder trust. The queued goal fires the instant trust is granted.

The remote launch now pre-trusts the one repository the loop was pointed at, on the host it runs on — an additive, idempotent write to Copilot's own trustedFolders (schema read off a real "remember this folder" answer). Creating a loop in that repo is the consent; the seed just delivers it to the right machine.

Scoped hard, pinned by tests: only Copilot nodes get the seed, a Claude node's remote script is asserted untouched, every local launch path is untouched by construction, and a host without python3 falls back to today's dialog rather than blocking the launch.

Note for loops created before this fix: an existing goal-less session is deliberately never re-prompted — rescue it with graphcode node send <project> <id> <goal> (delivery to remote sessions works as of beta3), or delete and recreate the loop.

Everything from beta3 (remote message/kill delivery over ssh, sidebar section air) is unchanged.