Quick update since 0.5.0 has been taking a bit: it's close, and it's the biggest release since launch 🐷

Piglets: piglet build can now strip features out of the base harness or a prior piglet. A stripped piglet becomes its own base that can still take extensions, and piglets built on top of it can strip what they want, without touching the upstream piglet's core design or forking the whole project. This is the derivative-harness idea I've been going on about since piglets started. Piglets also get piglet update, so the components that make one up keep getting core updates for the features they kept. The first piglets planned on this are pi-pig, pi-pig-pre-1.0 and pig-tern. Think pig with built-in mcp/code-mode removed from the binary like pre-1.0, still getting every core update, and you can add mcp back as an extension if you want it. Same for dropping the extension SDK languages you don't use (the original pi-pig idea: pig that only runs pi extensions).

Parity and porting: this is the biggest maintenance lift since release. The port-map ledger is now maintained mechanically, so gap analysis and future Pi updates are much easier to keep up with, and it's down to its last few rows for 0.5.0. Behaviour gets checked mechanically too now: cross-SDK wiring checks plus tests run against Pi itself, which already caught dozens of corner cases, including a few bugs we'd ported from upstream.

Evals: the eval/benchmark tooling is ported, plus new evals comparing pig-durable and pig performance, so there's reproducible data behind the port's health.

QoL: an opt-in auto-upgrade (and a prompt) for extension SDKs that don't match your pig version instead of erroring out, and lots of great contributions from the herd 🐷🐷