Original campaigns and map editing

Master: https://github.com/stacksjs/the-settlers-iii-remake/issues/4

Decoded mission data drives a bounded declarative objective runtime. Save mission progress with the world. Editing and import/export use the same validated map representation.

Completion gate

All mandatory child acceptance criteria require verified implementation evidence. Research, compilation, prototype victory, and uploaded but unprocessed binaries are not equivalent to completion. HomeOS integration is independent of supported game platform delivery.

Implementation issues

• https://github.com/stacksjs/the-settlers-iii-remake/issues/77 - Implement a safe mission and objective runtime
• https://github.com/stacksjs/the-settlers-iii-remake/issues/78 - Complete tutorials and the Roman campaign
• https://github.com/stacksjs/the-settlers-iii-remake/issues/79 - Complete the Egyptian campaign
• https://github.com/stacksjs/the-settlers-iii-remake/issues/80 - Complete the Asian campaign
• https://github.com/stacksjs/the-settlers-iii-remake/issues/81 - Complete Mission CD campaign content
• https://github.com/stacksjs/the-settlers-iii-remake/issues/82 - Complete both Amazon campaign paths
• https://github.com/stacksjs/the-settlers-iii-remake/issues/83 - Build a native and browser map and scenario editor
• https://github.com/stacksjs/the-settlers-iii-remake/issues/84 - Verify all campaign progression and original media

Dependencies

Work the actual child blocking graph. Do not make this entire epic a blocker for independent work. Sources and exact acceptance criteria are recorded in each child.