codeSplitter: names the rename kept (live resources, sealing, identity, env vars) #805

The codesplitters → codesplitter rename kept these names on purpose, because renaming them loses data or breaks existing setups. Each one needs its own migration if we want it moved:

• Live resources: D1 codesplitters-db, the queues codesplitters-hooks, -jobs and -level-digs, R2 codesplitters-level-chunks, Vectorize codesplitters-vectors, and the Artifacts namespace codesplitters. Renaming any of them makes Alchemy create a new, empty resource and delete the old one. Moving them means copying the data first.
• Alchemy app name (name: "codesplitters" in rustybuns.config.ts): this sets the Alchemy state key and the desktop's ~/.codesplitters data dir.
• Deploy-key sealing context (codesplitters ${what} in src/deploy-keys.ts): changing it would make every stored deploy key impossible to decrypt. Moving it needs a re-seal pass that reads with the old context and writes with the new one.
• Git identity: the codesplitters author and the @codesplitters.local emails. Commits are rebuilt from these, so changing them changes commit hashes.
• git_truth value "codesplitters", which is stored in users.git_truth. The UI already shows it as codeSplitter.
• Commit statuses codesplitters/<check>: branch protection on GitHub may require these by name.
• CODESPLITTERS_* env vars: the release script and deploy flags use them. Moving them means reading both names for a while.
• 1Password vault codesplitters: the owner would rename it, then the op:// references.

🤖 Generated with Claude Code