Prompt Optimizer v2.9.3

Summary

Established an English-first runtime and documentation baseline while keeping zh-CN and zh-TW fully localized through the updated locale packs.
Fixed localization regressions that surfaced English-only toasts in context editing, favorites, Prompt Garden imports, template loading, history saves, and model-management error paths.
Hardened repository guardrails, MCP packaging/startup behavior, and cross-platform script checks so the rollout is safer on both developer machines and CI.
Extracted evaluation prompt template assets into dedicated content/runtime modules to make template maintenance easier and keep guardrail coverage explicit.

The app now uses a more structured locale system: English is the baseline for shared runtime copy and docs, while Chinese users keep localized UI feedback instead of falling back to hardcoded English strings.

Split the UI locale packs into modular en-US, zh-CN, and zh-TW sections so runtime copy, template labels, favorites messaging, testing strings, and image workflow text can stay aligned across languages.
Restored localized feedback for context import/export, Prompt Garden partial-success warnings, template loading failures, history record errors, favorite save flows, tag/category management, and text model manager failure toasts.
Added bootstrap and runtime guard tests to catch hardcoded runtime strings and locale drift before merge.

Moved evaluation, rewrite, and structured-compare prompt assets into dedicated content/runtime modules instead of keeping large inline blobs in the service layer.
Added template guardrail tests so extracted prompt assets stay wired correctly as the evaluation stack evolves.

Hardened MCP packaging and startup integration, including the installable CLI entrypoint and language/config validation used by the English-first rollout.
Added repo-level locale parity and “no hardcoded Chinese runtime string” checks, then fixed the direct-execution path normalization so those checks behave correctly across Windows and Linux CI.

Fixed mixed-language error messages where zh-CN / zh-TW users could still see English fallback text such as Unknown error or raw English toast copy.
Fixed MCP startup/default-language integration gaps so locale bootstrap behavior and tests stay consistent.
Fixed cross-platform script execution detection for repo guardrails when CI compares Linux import.meta.url values against Windows-style script paths.

No breaking API or data-format changes.
This release does tighten locale and runtime-copy guardrails. If you maintain downstream customizations, expect stricter checks against untranslated runtime strings.

The locale rollout is intentionally test-heavy: UI runtime guards, locale parity checks, no-hardcoded-runtime scans, MCP environment coverage, and package script validation all landed together so the baseline is enforceable instead of convention-only.
The evaluation template refactor is primarily internal, but it substantially reduces the maintenance cost of large prompt assets and makes content reviews more targeted.