[M8] Compatibility, optimization, and standalone v1 release

[Teakowa]

Goal

Harden Wright into a standalone production-ready native toolchain and define the actual v1 release gate.

By M8, Wright should natively accept both supported .opy source and localized vanilla Workshop text, expose a first-class CLI, and no longer require OverPy/Node in the default supported runtime path.

Scope

• Finalize the v1 compatibility matrix and supported input/target versions.
• Enforce S/D/N/E compatibility gates over the declared corpus and scenario set.
• Build repeatable semantic/runtime-sensitive compatibility scenarios for high-risk Workshop behavior.
• Introduce a transformation/pass pipeline separate from read-only analysis.
• Provide conservative optimization profiles such as off, compat, and experimental aggressive.
• Measure parse/compile/analysis latency, memory, generated size, element/action/rule/variable usage, and optimization effects.
• Eliminate known semantic regressions in the declared supported surface.
• Harden deterministic diagnostics/output, crash behavior, packaging, release automation, and cross-platform distribution.
• Define public stability expectations for v1 CLI and machine-readable interfaces.

M8 sub-issues

• [M8] Finalize v1 compatibility matrix and S/D/N/E release gates #49
• [M8] Build runtime-sensitive semantic scenario framework #50
• [M8] Introduce WIR transformation pipeline and optimization profiles #51
• [M8] Implement evidence-backed compatibility-safe optimizations #52
• [M8] Define Workshop cost model and performance/resource benchmarking #53
• [M8] Harden standalone packaging, release automation, and public stability contracts #54
• [M8] Validate standalone v1 and rebaseline M9 #55 — v1 acceptance/re-evaluation gate before M9

v1 definition

Wright v1 is a standalone native Overwatch Workshop toolchain with:

• native localized Workshop input/output;
• native .opy compilation for the declared support matrix;
• a first-class CLI and compiler/session driver;
• semantic analysis and structured diagnostics;
• stable machine-readable interfaces suitable for automation.

Browser/editor extensions are explicitly not part of the v1 product boundary.

Exit criteria

• S/D/N compatibility gates pass for the declared v1 corpus.
• Representative high-risk E-level semantic scenarios pass with no known supported-surface regressions.
• compat optimization mode is evidence-backed and safe; aggressive is not required for v1.
• Default supported workflows are standalone and native.
• Release artifacts and stability policy are documented and reproducible.
• [M8] Validate standalone v1 and rebaseline M9 #55 validates the actual release evidence and rebaselines M9.

Planning note

M8 issues are provisional until #48 completes. #55 is a hard re-evaluation gate; M9 planning should be revised if v1 implementation produces different public boundaries than currently expected.

[Teakowa]

Milestone complete: sub-issues #49–#54 and gate #55 are closed with v1-gate/scenario/benchmark/release evidence (commits 2537396, 1611004); see the gate writeup.