Prompt Optimizer v2.9.0

Summary

Introduced the first end-to-end multi-image generation workflow, including ordered image inputs, a dedicated workspace, multimodal prompt optimization, and provider support updates.
Hardened local storage and favorites safety with startup integrity checks, favorite asset reference cleanup, quota protections, and a clearer storage overview in Data Manager.
Removed stale client-side blockers in the image pipeline and stabilized parallel runs, session recovery, replayable E2E suites, and bilingual release-note publishing.

Multi-image generation now spans optimize, generate, favorites, desktop bridge, and session restore flows instead of living as an isolated UI experiment.
Storage safety is much stricter: oversized or malformed startup state can now be repaired at boot, and unreferenced favorite image assets are cleaned up deliberately instead of accumulating silently.
Data Manager now explains storage areas and footprint more clearly, making it easier to spot abnormal growth before it turns into a startup or persistence failure.

Added startup storage safety checks before session restoration so broken settings, favorites, or session payloads are less likely to block app launch.
Extended the desktop image bridge to support persisted multi-image asset flows more reliably.

Added a redesigned multi-image workspace with ordered input management, route and session guards, token usage feedback, history restore, and Prompt Garden integration.
Refined the Data Manager storage overview so users can inspect storage regions and estimated footprint more directly.
Restored parallel variant execution outside automation-only flows.

Added multi-image request types, templates, provider routing, and provider coverage, including OpenRouter payload fixes and Seedream multi-image generation support.
Persisted multi-image session inputs as asset references instead of inline payloads, which keeps storage safer and restores more predictable.
Added favorite storage guards, favorite asset garbage collection, and repo-driven bilingual release-note plumbing.

Fixed OpenRouter multi-image requests so ordered input images are serialized into the provider payload instead of being dropped.
Fixed stale local capability checks that could block valid multi-image generation requests before they reached the provider.
Fixed multi-image session recovery so missing or invalid image assets fail explicitly instead of silently degrading into broken empty inputs.
Hardened favorite asset quota enforcement, import handling, and startup recovery paths to reduce orphaned data and silent storage growth.
Stabilized gated E2E replay workflows and refreshed image fixtures for more reliable regression coverage.

None for valid data and supported workflows.
Startup repair is now more proactive: malformed session entries, invalid favorites, or unreferenced favorite image assets may be cleaned up automatically to keep the app bootable and storage bounded.

Release notes are now repo-driven bilingual documents under releases/, and GitHub Release summaries consume the Summary and 概括 sections directly.
If you maintain provider integrations, multi-image support now needs provider-level payload assertions in tests, not just service-level routing coverage.
Storage architecture and budget assumptions are now documented in docs/architecture/storage-runtime-architecture.md.