chore(rebrand): phase 4c — remaining source strings, storage keys and identifiers

[qnbs]

User description

Summary

Part of the StoryCraft → WorldScript rebrand split. This PR sweeps the remaining source strings, test fixtures, worker scripts and type identifiers.

Changes

• Replaces remaining StoryCraft references in source code, comments and strings with WorldScript.
• Updates test files and fixtures to use the new identifiers.
• Updates worker entry files and service identifiers.
• Renames identifiers in types.ts and related type definitions.

Scope

• Does not include UI components (phase 4d), i18n values (phase 5-6) or docs/CI (phase 7-8).
• Legacy IndexedDB database names remain unchanged for migration compatibility.

Related

• Part of the rebrand split after rebrand: StoryCraft Studio → WorldScript Studio (v1.23.0) #141.
• Related PRs: phase 1-3, 4a, 4b, 4d, 5-6, 7-8.

---

CodeAnt-AI Description

Finish the WorldScript rebrand and make community templates create projects

What Changed

• Replaces remaining StoryCraft names, links, file names, storage keys, and startup labels with WorldScript across the app
• Updates accessibility, PWA, voice, AI, export, collaboration, and database markers so the new brand is used consistently in saved data and downloads
• Fixes community template application so selecting one now creates a new project and opens it instead of doing nothing
• Keeps the app’s existing data flow working after the rename, including theme, language, and view persistence

Impact

✅ Consistent WorldScript branding across the app
✅ Fewer broken saved settings after the rebrand
✅ Community templates now open as new projects

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

Skipping CodeAnt AI review — this PR changes more than 100 files, which usually means a migration, codemod, or vendored drop. Line-level review on diffs this large produces duplicate findings on the same rewrite pattern and drowns out anything that actually matters.

If you still want a review, comment @codeant-ai : review. For better signal, consider splitting the PR into smaller chunks.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
storycraft-studio	Ready	Preview, Comment	Jun 16, 2026 5:54am

[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 completes the rebrand by standardizing the adaptive AI engine gate on a WorldScript-specific window flag, showing how feature flag changes control local AI behavior through listener middleware and the local AI facade.

sequenceDiagram
    participant User
    participant App
    participant AdaptiveListener
    participant Window
    participant LocalAIEngine

    User->>App: Enable adaptive AI in settings
    App->>AdaptiveListener: Feature flag enableAdaptiveAiEngine updated
    AdaptiveListener->>Window: Set worldscript adaptive ai flag to true
    AdaptiveListener->>AdaptiveListener: Generate local device profile

    User->>App: Request local text generation
    App->>LocalAIEngine: generateLocalText(prompt)
    LocalAIEngine->>Window: Read worldscript adaptive ai flag

    alt Adaptive flag is true
        LocalAIEngine->>LocalAIEngine: Use adaptive task configuration
    else Adaptive flag is false
        LocalAIEngine->>LocalAIEngine: Use default local model configuration
    end

Loading

---

Generated by CodeAnt AI

[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 diagram shows how the app now uses WorldScript-specific storage identifiers and centralized brand constants when persisting user data and generating export files, replacing the previous StoryCraft naming while keeping the core flows the same.

sequenceDiagram
    participant User
    participant App
    participant BrandConstants
    participant BrowserStorage

    User->>App: Change settings and project data
    App->>BrowserStorage: Save state using worldscript-* keys and DB names
    User->>App: Request backup or dataset export
    App->>BrandConstants: Read APP_FILE_SLUG and APP_NAME
    App->>BrowserStorage: Build export files with worldscript-prefixed filenames
    App-->>User: Download WorldScript backup and settings files

Loading

---

Generated by CodeAnt AI

[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 fixes the Community templates Apply action so it now directly creates a project from the selected template via Redux and navigates to the manuscript view, instead of dispatching an unused window event.

sequenceDiagram
    participant User
    participant CommunityTab
    participant TemplateView
    participant Store
    participant AppView

    User->>CommunityTab: Click Apply on community template
    CommunityTab->>TemplateView: applyCommunityTemplate(template)
    TemplateView->>Store: setManuscript and setOutline from template
    TemplateView->>AppView: Navigate to manuscript view
    Store-->>AppView: Updated project state
    AppView-->>User: Show manuscript populated from template

Loading

---

Generated by CodeAnt AI

[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 diagram shows how applying a community template now directly creates a new project and navigates to it via the template view hook and Redux, replacing the previous no-op window event.

sequenceDiagram
    participant User
    participant CommunityTemplates
    participant TemplateView
    participant Store
    participant App

    User->>CommunityTemplates: Click Apply on community template
    CommunityTemplates->>TemplateView: applyCommunityTemplate(selectedTemplate)
    TemplateView->>Store: Set manuscript and outline from template sections
    Store-->>TemplateView: Project state updated
    TemplateView->>App: Request navigation to manuscript view
    App-->>User: Show new project in manuscript editor

Loading

---

Generated by CodeAnt AI