v0.7.0

The run gets a planner and the machine gets one panel. The planner skill authors the run's plan
with you in conversation without ever inventing an acceptance criterion; the machine panel comes
up with the first milestoner run and spans every run on the machine. The Claude Code plugin is
retired: it could not do anything without the npm-installed binary its commands and skills shell
out to, so milestoner skill install is now the one way the skills reach a machine.

Added

• The planner skill, milestoner-planner: plans a run together with the user - it interviews,
  proposes the milestone breakdown for approval, and only then writes the prompts, the protocol
  TODOs and the liveness config. It never writes before approval and never invents an acceptance
  criterion, so the boundary against generated specifications (D-031) stands; the argument is
  D-032. Shipped like the supervisor skill: one source in src/templates/, written by
  milestoner skill install.
• milestoner init now points at the planner skill for the authoring steps it cannot do itself.
• milestoner skill install -g as the short form of --global.
• The machine panel (D-033): milestoner serve --all serves every run the registry knows about,
  from any directory - a hub across runs plus the familiar per-run view with a switcher. The first
  milestoner run on the machine brings it up as a detached daemon that stays while any run is
  alive (plus a ten-minute linger) and then exits and cleans up after itself; every run prints its
  URL, discovery is ~/.milestoner/panel.json, and milestoner runs names the URL when a panel
  is live. --no-panel opts a run out.
• milestoner run --open opens the machine panel in the browser without writing the key into
  browser history: the CLI mints a single-use token and the panel exchanges it at /auth for an
  HttpOnly cookie, so the URL history keeps is already dead. By default the browser opens only on
  the run that started the daemon; --no-open stops even that. D-027's refusal of --open for
  the attached run --serve panel stands.

Changed

• milestoner skill install takes an optional skill name (supervisor, planner, or the full
  names). With no name it installs every bundled skill, where it previously installed only the
  supervisor; --print now requires a name.
• milestoner run now brings the machine panel up by default (read-write: kill, steer and unblock
  at 3am are why it exists; the guards are the same loopback bind, Host allowlist, key and Origin
  check as always). run --serve keeps its per-run attached panel unchanged and skips the machine
  panel.

Removed

• The Claude Code plugin and its in-repo marketplace (D-034). The plugin could not do anything
  without the npm-installed binary its commands and skills shell out to, so it was a second copy
  of the npm channel, not a second channel. milestoner skill install is now the one way to get
  the skills, and with them gone go commands/, the generated skills/ mirror, the manifest
  sync/check scripts, and the manifests CI job.