v0.26.3

Adds `peppy repo search` and `repo show` to find any indexed item by regex and report who implements, consumes, or observes it.

Released on August 31, 2026

A bare launcher name (no path separator, no .json5) passed to peppy stack launch or stack resolve now resolves through the repository cache only, never a same-named file in the current directory; write ./name.json5 to launch a local file.
Run peppy repo refresh after upgrading: peppy refuses a nodes cache written by an earlier release, and the commands that read it fail until it is rebuilt.

peppy repo search <name-regex>[:<tag-regex>][@<sha256>] finds any indexed node, launcher, contract, pairing, or MCP exposure by unanchored regex, listing each match's kind, repository, path, and fingerprint.
peppy repo show <query> reports every matched identity: where each document is published and, for a contract or pairing, the nodes that implement, consume, participate in, or observe it, with each pin's status.
Both repo search and repo show accept --json for machine-readable output and read the local caches, so they need no daemon.

peppy stack list --json prints the discovered core nodes and their stacks as one JSON document.
stack list panels and the repo search / repo show tables now fit the terminal, wrapping over-long cells inside the borders; piped output stays unwrapped.
On Linux, replacing the peppy binary while the daemon runs no longer strands built-in MCP nodes: the daemon serves them from its running image, warns in the add log, and adopts the new binary on restart.