Claude-built tools become deployed full-stack apps through two composable skills — and a repo stays the record for every app that has one.
A fleet of supply-chain consoles was built as Claude React artifacts and deployed through a two-skill pipeline. abacus-mirror ports an artifact at high fidelity to a managed Next.js web app — it encodes the platform's deploy contract (component slot, managed providers, dependency age gate, design tokens) so the port survives contact with the platform. abacus-bridge then augments the deployed mirror server-side: database persistence with an admin/use split, per-dataset merge, upload history, and a secure-by-default auth gate whose secret never enters the source.
The key property used to be that the Claude artifact stayed canonical and a deployment could be re-derived in place. That round trip was retired on 20 Sep 2026 after an in-place upgrade stranded saved rows. An app holding saved data is now updated by export, tear down, rebuild and re-import. For the apps whose source lives in a repo, a change made on the platform comes home as a download, passes the PC's checks and the repo's own tests, and is committed, so the repo stays the record.
The portability is the point: nothing is locked in, and proven tools can move to a governed enterprise platform (managed Postgres behind an ORM layer that keeps the next hop portable too). Build fast on whatever's available; move to durable infrastructure when it matters.