v0.6.0

A repair release. Everything below came out of one user report — a folder tree that stayed
white under the Midnight palette — because chasing it exposed that of 59 regression
scenarios, not one had ever looked at a colour. The audit built to answer that found a
crash on ordinary use, and the same sweep of the test harness found seven keyboard checks
that had been measuring nothing at all.

Still unsigned and un-notarized. macOS blocks the first launch; README.md explains
how to allow it once.

Fixed

• The local-network prompt on first launch now says what it is for. macOS asks the moment
  anything enumerates network interfaces, which the title bar's throughput display does to read its
  byte counters — and with no explanation supplied, the prompt appeared before you had done anything
  and looked like an application asking to search your network. It now states the reason, and the
  reason is the whole of it: counters are read, nothing is searched for or connected to.
• Changing the colour scheme with the Notes or Disk Map panel open no longer quits the app. The
  two panels kept a reference to a table of host functions that is only valid while the host is
  handing it over; reading it later — which is what a theme change does — corrupted memory and
  killed the app outright. Found by the colour sweep below, not by the crash reports, because
  nothing had ever switched a theme with one of those panels open.
• The terminal's status line is readable under Norton Commander colours. It took its grey from a
  colour the palette defines for the path bar, which is black there and sat on a blue background
  here. Plugin panels now derive that grey from the surface they actually draw on, so it follows any
  palette instead of happening to suit some.
• The folder tree follows the colour scheme. Both of them — View ▸ Tree beside a panel and
  View ▸ Shared Tree — used to keep the light default whatever you had chosen, so under Midnight a
  white column of pale, barely readable text stood between two dark panels. The tree knew how to
  repaint itself and was never asked to.
• Piping a selection through a command that stops reading early no longer quits the app. head -1
  is an ordinary filter — it takes one line and leaves — and the rest of the text then had nowhere to
  go, which ends a program on macOS unless it says otherwise. Affected the editor's filter, the
  external formatters and anything else that pipes text through a tool.

Added

• Eject a removable volume without switching to Finder. Right-click a volume — or anything on it
  — and the menu offers Eject “name”; the same command is in Commands ▸ Eject Volume and can be
  given a key of your own in the keyboard settings. It works from inside the volume too, not only
  from the folder above it. The startup disk is never offered, a network share says so rather than
  failing silently, and when something still has the volume open, macOS's own explanation of what
  is holding it is passed straight through — that sentence is the only thing that tells you what to
  close. This was listed as done and was not built at all: the app read which volumes were ejectable
  and then had no way to eject one.

• Terminal tabs come back after a restart, in the folders they were in. The shells cannot come
  back — those processes ended with the app — but three terminals in three checkouts no longer become
  three prompts in your home folder. A tab the assistant opened for one command is deliberately not
  restored.

• The assistant can run a shell command — off unless you switch it on (Settings ▸ AI), visibly, and only after you agree to each one. It opens a terminal
  tab, so what was run is on screen afterwards next to everything else you ran, and a command that
  asks a question can be answered. The approval quotes the command in full, because that is the whole
  decision. The tab runs a non-interactive shell: aliases and functions from your ~/.zshrc do not
  apply, so the line you approved is the line that runs. A session set to read-only cannot use it at
  all, and it is not offered to external agents over MCP — those confirm their own plans, which is
  the right arrangement for file work they were connected to do and the wrong one for running a
  program of their choosing.

• Panels can be dragged between the side panel and the bottom area. Grab the mode switcher and
  drop it on the other one; the target lights up, and a panel dropped where it already is does
  nothing rather than pretending. The menu route (right-click the switcher) does the same thing and
  remains the one that works from the keyboard.