v0.3.0 — resumable production studio

Framewright 0.3.0 moves toward an agent-operated personal production studio: keep the project, decisions and reusable materials together, then prepare a local publication kit.

• Resume projects with explicit tasks/waits, file pins and revision-bound evidence. Technical QA, listening, creative acceptance and publication remain separate.
• Connect scenes, demonstrations, narration and missing inputs; reuse source/rights-bound materials across independent main/Short edits.
• Build local publication kits containing final files, hashes and open checks. Uploading remains a separate action.
• Search tools and proposed combinations; use shared repackaging/insight/hybrid intake and a private music catalogue. Discovery drift now fails offline validation.
• Retain scoped game creation, game/engine reviews and games as virtual sets, plus Shorts, converter/ASR and recording-preparation workflows.

Validation: 244 unit tests and the complete offline check pass, including historical-evidence integrity, local links, generated matrix and extracted standalone package smoke. No video render or new model qualification was performed for release. Current-source routing remains experimental and unevaluated.

Installation: framewright-router-0.3.0.zip contains the router skill only, including its project/journal/scene/kit helpers. Use the full source checkout/archive for both skills (video-production-router, game-engine-production) and case documentation. Verify the ZIP against SHA256SUMS. Core references stay local; optional case/provenance links are pinned to this release tag and checked during packaging. Schema-1 production projects require explicit backed-up migration before using schema-2 additions.

The PlayMCP service review continues with owner retakes; it is not a release prerequisite. Other engines, native audio/video understanding, strict resource enforcement and general autonomous production remain unqualified or deferred.