fix(release): finalize v1.23.0 — Tauri blank-screen fix + changelog + CF Pages rename

[qnbs]

User description

Finalizes the v1.23.0 release notes and a small rebrand-config tail.

Changes

• CHANGELOG: promote [Unreleased] → ## [1.23.0] — 2026-06-16; add this release's remaining entries: Local-First foundation (feat(local-first): A0.1 perf harness → B0.1 PoC → ADR-0008 → B1.1 shadow sync #140, behind enableLocalFirstSync), OpenRouter reactive policy + render-loop fix (fix(settings): make OpenRouter cloud-policy block reactive to live state #163), Local AI settings i18n (fix(i18n): localize Local AI settings section (40 keys × 8 locales) #164), WorldScript icons + 8-bit Tauri fix + URL cleanup (fix(branding): WorldScript W monogram icons (8-bit, fixes desktop build) #165), and Dependabot maintenance. A fresh empty [Unreleased] shell remains on top.
• wrangler.toml: rename the Cloudflare Pages project storycraft-studio → worldscript-studio. CF is not actively/prominently deployed, so this is a safe forward rename; the CF-side project rename is a later step.

Notes

• Version fields are already 1.23.0 everywhere (synced); this PR only finalizes notes + the CF name.
• Desktop build already verified green on all 3 platforms via fix(branding): WorldScript W monogram icons (8-bit, fixes desktop build) #165's tauri-build run.

🤖 Generated with Claude Code

---

CodeAnt-AI Description

Fix desktop blank-window loading and finalize v1.23.0 release notes

What Changed

• Desktop builds now load the app with the correct relative base, so the Tauri window opens with content instead of a blank screen on Windows and macOS
• The base-setting logic is now covered by tests, including Tauri desktop, edge deployments, explicit custom bases, and the default GitHub Pages path
• The v1.23.0 changelog is finalized with the remaining release entries, and the Cloudflare Pages project name is updated to match WorldScript Studio

Impact

✅ Fewer blank desktop windows
✅ Reliable asset loading in Tauri builds
✅ Clearer v1.23.0 release history

💡 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.

[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:19pm

[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

[qnbs]

Added a release blocker fix: desktop (Windows/macOS) launched to a blank webview because the Tauri build read TAURI_PLATFORM (Tauri 1.x) instead of TAURI_ENV_PLATFORM (Tauri 2.x), so base fell through to the GitHub Pages path and 404'd all hashed assets under tauri://localhost/. Fixed in config/resolveViteBase.ts (+6 unit tests). Triggering tauri-build.yml on this branch to produce a fresh Windows binary for manual re-test.

@CodeAnt-AI review

[qnbs]

@CodeAnt-AI review

[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

[codeant-ai]

Sequence Diagram

This PR centralizes Vite base resolution so Tauri desktop builds detect the correct platform env vars, use a relative base, and successfully load bundled assets instead of showing a blank window.

sequenceDiagram
    participant Developer
    participant TauriBuild as Tauri build
    participant ViteConfig as Vite config
    participant ResolveBase as resolveViteBase
    participant DesktopApp as Desktop app

    Developer->>TauriBuild: Run desktop build
    TauriBuild->>ViteConfig: Start Vite bundling with env vars
    ViteConfig->>ResolveBase: Resolve base from environment
    ResolveBase-->>ViteConfig: Return './' for Tauri desktop
    ViteConfig->>TauriBuild: Bundle app with relative asset paths
    DesktopApp->>DesktopApp: Load assets using relative base and render UI

Loading

---

Generated by CodeAnt AI