[callumflack]

Summary

An app already owned on Moksha can become available on mainnet with one command, its existing key and Account owner, and no second claim.

vana app register --network mainnet --app-url http://localhost:3090 --app-name "Perplexity CLI demo"

The CLI verifies existing ownership, registers the same key on mainnet, and associates it with that Account. It opens Account only when sign-in is needed. Interrupted operations retain their identity; network profiles preserve Moksha metadata.

This release is independent of the funding changes in #106. It includes the existing transcript-isolation fix so release demos cannot open real browsers or contact providers.

Evidence

• Before: mainnet registration had no same-Account association path.
• After: focused tests cover same-key completion, repeat/interrupted runs, missing keys, wrong Account, unavailable ownership and browser-free automation.
• Full validation: 906 tests passed, TypeScript, ESLint and formatting passed before the transcript prerequisite. Its 23 focused isolation/runtime tests also passed.
• Build, npm package-content checks and isolated transcript capture passed. Live production proof remains pending Account deployment. Generated fixture output was inspected and discarded after validation.

Merge Danger

Door: two-way for CLI code; successful mainnet registration persists externally.

Blast Radius: builder registration, scoped app metadata and isolated release-demo capture.

Depends on Account schema/API deployment from vana-com/unity-surfaces#1981. Do not merge/release before that dependency is live and the production candidate flow is verified. Production database access is currently blocked. No fees, grants or data are migrated.

BUI-938. Created with Codex.