I m building ShipGuard as an open-source, local-first assurance layer for using Codex on real iOS work.

The current public release is now green on main with release-candidate readiness proof: install, upgrade, uninstall, release-proof consumption, schema docs, plugin refresh proof, package proof, and blocked stable-release claims. In plain English: ShipGuard is getting closer to being a product, not just a bundle of useful scripts.

The v4 direction is narrower than it might look:

inspect -> prepare -> verify

I am building ShipGuard around one rule: agent speed is great, but risky iOS work needs a proof lane.

For me the line changes by surface:

- build/run for compile and obvious integration

- logs/debugger for runtime behavior