refactor(registry): unify package build/publish lifecycle in agentos-toolchain

[NathanFlurry]

• Grow @rivet-dev/agentos-toolchain into the full package lifecycle CLI: new stage (populates bin/ from a commands dir per declarative commands/aliases/stubs in agentos-package.json), build (assembles dist/package/), and publish (per-package version; dist-tag dev by default, latest only with explicit --latest), alongside the existing pack
• Add agentos-package.json staging manifests to every registry/software/* package and switch their builds to agentos-toolchain stage && tsc && agentos-toolchain build, fixing the unpopulated-bin/ gap
• Delete the legacy registry build/publish systems: registry/Makefile, publish-software.sh, assemble-dist-package.mjs, generate-readme.mjs, the stale software/*/wasm/ outputs and meta.json generation
• Stop shipping the staging bin/ in npm tarballs (packages shipped every binary twice)
• Add just registry-native [cmd], registry-build [pkg], registry-test, registry-publish <pkg> [tag], registry-publish-all, and registry-status recipes, plus a wasm-cmd target in registry/native/Makefile for single-command rebuilds
• Point agent packages at the agentos-toolchain bin instead of a relative dist path
• Rewrite registry/README.md around the new lifecycle and update CLAUDE.md

[railway-app]

🚅 Environment secure-exec-pr-222 in rivet-frontend has no services deployed.

---

🚅 Deployed to the secure-exec-pr-222 environment in secure-exec

Service	Status	Web	Updated (UTC)
secure-exec	😴 Sleeping (View Logs)	Web	Jul 3, 2026 at 1:35 am