chore(release): v1.23.0 smoke-test sign-off + worldscript-localfirst DB prefix

[qnbs]

User description

Final pre-tag step for v1.23.0.

Smoke-test sign-off (docs/V1.23-REBRAND-SMOKE-TEST.md)

• ✅ Desktop blank-screen blocker fixed (TAURI_ENV_PLATFORM base-path, fix(release): finalize v1.23.0 — Tauri blank-screen fix + changelog + CF Pages rename #166) — maintainer confirmed the Windows installer now launches the full UI (row 7.1).
• ✅ Tauri build green on all 3 OS (row R.12); full CI green on main (row R.11).
• ✅ Rebrand static checks (R.4/R.9/R.10) + version consistency (1.23.0 across package.json / tauri.conf.json / Cargo.toml / sw.js).
• macOS GUI N/A (no hardware); Linux GUI N/A on Ubuntu 20.04 (Tauri 2 needs webkit2gtk-4.1 / 22.04+) — covered by green CI builds, non-blocking post-release pass.

Brand fix

• Renamed the off-by-default local-first shadow-store IndexedDB prefix storycraft-localfirst- → worldscript-localfirst- (+test) so the rebrand's "all IndexedDB names → worldscript-*" claim holds. Pre-release store behind enableLocalFirstSync (off) → safe outright rename, no migration.

After merge: tag v1.23.0 (signed release binaries + latest.json).

🤖 Generated with Claude Code

---

CodeAnt-AI Description

Rename the local-first data store prefix and record v1.23.0 release sign-off

What Changed

• The experimental local-first project data store now uses the worldscript-localfirst- name instead of storycraft-localfirst-, matching the rebrand.
• The unit test was updated to expect the new database name.
• The smoke-test guide was expanded with the v1.23.0 sign-off, including the fixed desktop blank-screen issue, successful desktop builds, and completed rebrand checks.

Impact

✅ Rebranded IndexedDB names
✅ Clearer release sign-off
✅ Fewer stale StoryCraft references

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
worldscript-studio	Ready	Preview, Comment	Jun 16, 2026 4:57pm