PiClaw v2.10.0 — "Re-embody"

Runtime, model and credential handling have been put back into one body. The ghost was fine; the wiring needed less improv theatre.

Features

Upgraded the Earendil runtime stack to 0.80.10, covering @earendil-works/pi-agent-core, @earendil-works/pi-ai and @earendil-works/pi-coding-agent.
Routed session and auxiliary model requests through the new runtime model layer, giving prompts, tools, delegates, compaction and restored sessions a single view of available models and credentials.
Moved GitHub Copilot discovery into the runtime model layer, so dynamically discovered Copilot models use the same catalogue path as the rest of model selection.
Adopted provider-owned credential and login flows where the 0.80.10 runtime now owns them, reducing compatibility seams around private and custom providers.
Kept pi-mcp-adapter pinned at 2.11.0, which remains the latest published version.

Fixed a production-path agent-directory split where one side could read PICLAW_PI_AGENT_DIR and another could read PI_CODING_AGENT_DIR, producing separate credential and catalogue views. The directory resolution is now unified and the upstream environment is synchronised before runtime startup.
Cache-first and offline startup paths were revalidated against the corrected runtime, reducing surprises when model catalogues or credentials are loaded without a fresh network path.
Model-picker latency and Copilot catalogue consistency were verified after the runtime migration.
Local standalone verification covered prompt execution, tool use, delegate calls, session restore, compaction and model discovery after the migration.
Azure managed-identity token caching was tightened so cached credentials are treated as sensitive runtime material rather than casual desk clutter.

Preserved Copilot request headers for dynamically discovered models, fixing a path where dynamic catalogue entries could lose provider-specific request metadata.
Hardened payload hooks so missing selected-model data is tolerated instead of turning a recoverable provider payload into a small administrative incident.
Aligned private and custom provider handling with the 0.80.10 runtime model layer.
Verified Kimi deferred activation under the new provider/runtime path.
Cleared baseline lint errors before the migration line, making later failures easier to read and less like a crime scene with old footprints.

Rewrote and tightened shipping documentation in plain English, with outdated operational claims removed or corrected.
Updated Earendil references to 0.80.10 across the README, runtime docs, shipped skill docs and operational notes.
Reviewed the README against the technical-docs writing rules and trimmed weaker wording.
Updated cross-instance IPC documentation and related runtime/operator guidance.
Archived the old file-based kanban skill guidance in favour of the current GitHub Issues workflow.
Refreshed shipped skill documentation, including the technical-docs skill and timeline PDF export workflow.

This release is mostly a runtime/model/auth migration plus documentation cleanup. It is not a new UX feature release.
Existing provider credentials still have to exist in the expected profile/keychain locations; this release makes the lookup path consistent, not magical.
The Copilot catalogue is still provider-owned and can change upstream without a Piclaw release. The runtime path is now less likely to drop the relevant headers while finding out.
pi-mcp-adapter remains at 2.11.0 because there is no newer published version to adopt.