UniPi 3.0.3

Fixed

• Pi stops warning about — and installing — a second copy of its own runtime (#43). @pi-unipi/compactor and @pi-unipi/subagents declared @earendil-works/pi-agent-core, and @pi-unipi/background-tasks declared @earendil-works/pi-ai, under dependencies. Pi supplies those five packages itself, so a published dependencies entry makes npm install them next to the host: on the reporter's PC that was 0.87.1's pi-agent-core, pi-ai, chord and pi-telemetry (≈15 MB, 8 lock entries) while Pi 1.5.0 was already running, and every start printed Host-provided extension packages must be declared in peerDependencies with a "*" range, not dependencies. Every one of those imports is import type only (subagents never imports the package at all), so no copy is needed at runtime: the entries moved to peerDependencies, keeping the usual ^0.87.1 gate. Each of the three now also declares every host package its source imports — @earendil-works/pi-ai was undeclared in subagents and background-tasks.
  Do this: update. Pi stops installing those copies; anything already on disk under ~/.pi/agent/npm/node_modules/@earendil-works/ is dead weight and can be deleted, because Pi maps those specifiers to its own modules.
• /unipi:fusion-stats shows the active pair before the first handoff. The command answered "Fusion is not active — pick a Fusion pair with /unipi:model" in every session that had not delegated yet. It read the sidekick runtime — a process that starts on the first handoff — as the sign of Fusion being on. A picked pair now reports its lead and sidekick, zero tokens, and a "not started yet" state.
  Do this: nothing.