Outcome
Publish a standalone native editor that runs from released artifacts and safely opens explicit projects without Java, classic binaries, or source-layout assumptions.
Scope and invariants
- Package editor binary, approved SDL3/UI/renderer/toolkit runtime dependencies, shaders/fonts/bootstrap assets, licenses/notices, SBOM, provenance, checksums, and crash-symbol policy.
- Define install/user config/cache/recovery paths, project selection, upgrade/downgrade/reinstall behavior, file associations if approved, and compatibility ranges.
- Exercise Vulkan/Linux and D3D12/Windows, high DPI, multiple displays, clean machines, restricted permissions, and paths with Unicode/spaces.
- Exclude client credentials/cache and server mutable state; playtest integration invokes installed wrapper contracts explicitly.
- Document backup/recovery and safe uninstall behavior for user-authored/recovery data.
Acceptance criteria
- Clean-machine packages open/edit/validate/preview/save a fixture without source checkouts, Java, Python runtime, classic binaries, or connected server.
- License audit covers every bundled code/asset/font/shader.
- Upgrade preserves settings/recent projects/recovery compatibly and never mutates project source automatically.
- Release artifacts are reproducible or variance documented and include complete provenance.
- Website/wrapper use immutable release coordinates.
Dependencies and parallelization
Depends on M4 workflow parity, released renderer/toolkit crates, and provenance closure. Packaging automation can start with M4 snapshots.
Licensing
Editor code/tests are MIT. Verified original past work by an approved MIT provenance grantor may be copied, migrated, or translated under the audited file/component grant; other legacy implementation remains behavior/specification input only. Authored content/assets retain exact licenses.
Outcome
Publish a standalone native editor that runs from released artifacts and safely opens explicit projects without Java, classic binaries, or source-layout assumptions.
Scope and invariants
Acceptance criteria
Dependencies and parallelization
Depends on M4 workflow parity, released renderer/toolkit crates, and provenance closure. Packaging automation can start with M4 snapshots.
Licensing
Editor code/tests are MIT. Verified original past work by an approved MIT provenance grantor may be copied, migrated, or translated under the audited file/component grant; other legacy implementation remains behavior/specification input only. Authored content/assets retain exact licenses.