Complete editor automation, preview, recovery, and isolated playtesting

[zoeyrose]

Important

This preserved authoring issue now belongs to the fresh MIT Rust editor under the replacement program. Gameplay/content design and safe-authoring requirements remain unchanged. Legacy implementation paths below are historical evidence.

Replacement implementation contract

Editor owns preview state, recovery UI, automation adapters, and invocation of a versioned wrapper playtest contract. content-toolkit owns bulk/transaction CLI/MCP primitives; atrinik owns isolated server/client scenario orchestration. Preserve all safety, dry-run, recovery, observability, and preview requirements without reconstructing runtime paths.

Verified original past contributions by an approved MIT provenance grantor may be copied, migrated, translated, or relicensed under MIT only after complete Git provenance and third-party-material review is recorded. Other GPL implementation/tests must not be mechanically ported.

Required verification

• Preserve unknown fields, comments, ordering, and untouched bytes through lossless toolkit transactions.
• Use semantic commands with revision preconditions, dry-run/diff, undo/recovery, validation, and atomic writes.
• Use the exact shared renderer and toolkit APIs; no duplicate parser, renderer, or pixel-selection path.
• Test Linux/Windows, malformed/large projects, external edits, storage/device failures, and wrapper-isolated playtests as applicable.

Preserved product/design specification and historical implementation notes

Parent and roadmap

• Parent tracker: Replace Gridarta with the standalone MIT Rust editor #13
• Roadmap: Roadmap: replace classic Atrinik with a fresh MIT Go and Rust stack atrinik#168
• Roadmap milestone: M4
• Prerequisites: Ship the native Rust map-editing MVP #11, Define region projection manifests and image products renderer#21, Add a versioned local automation API and web control surface client#18

Outcome

Complete the high-value content workflow beyond the map MVP with safe bulk automation, exact previews, recovery, and disposable local playtests.

Scope

• Add tiled/exit graph assistance, backlink validation, advanced bulk tools, performance work, and focused panels for additional authored content based on actual maker needs.
• Expose exact deterministic preview rendering through the shared world-image executable/API.
• Add autosave/recovery outside source directories and an isolated collect/server/client playtest that touches only state it creates.
• Optionally add a thin stdio MCP facade only after CLI schemas stabilize; it must call the same core operations and safety checks.

Superseded path / cleanup target

Remove proof-only preview/playtest scripts and any direct writes to server/data, collected aggregates, generated region maps, or a running remote server.

Acceptance criteria

• A user can edit, validate, preview, and playtest a selected map without modifying source-tree runtime data.
• Bulk and machine-authored changes remain preconditioned, dry-runnable, atomic, and reviewable.
• Recovery restores editor-owned temporary state without corrupting authored files.
• Any MCP facade is a thin tested adapter, not a second parser/editor.

Validation baseline

Before: the MVP supports core editing but not a complete safe preview/playtest or advanced automation loop.

After: human and automated authors share one end-to-end edit/validate/preview/playtest workflow.

Run transaction/recovery fault injection, preview equivalence, isolated runtime setup/teardown tests, CLI/MCP schema tests if present, and package smoke tests.

This issue is a bounded child of #13. The parent remains open until every sibling child is complete.