[M13] Compile the accepted OSTW corpus slice to Workshop with reference differential validation

[Teakowa]

Parent: #90
Depends on: #118, #122

Goal

Complete the first Wright-owned OSTW -> Workshop pipeline for the semantic surface established by #118 and validate it against explicit-root pinned OSTW v3.4.0 reference evidence established by #122, without requiring output-text identity.

Context

#117/#118 establish Wright's native OSTW project/syntax/semantic frontend and frontend-neutral HIR boundary.

The original version of this issue assumed #115 proved the protect-ban entry project was accepted and produced a stable 79-element Workshop artifact. #118's pinned P1 probe disproved that interpretation: the upstream language server compiles the last-opened document plus its transitive import closure, and the historical 79-element result belongs to utils/ServerLoad.del, not the ds.toml.entry_point graph. The entry-root graph currently rejects on three missing ../OSTWUtils/... imports.

#122 therefore owns the corrected explicit-root oracle baseline and must establish the accepted differential target(s) used here. protect-ban remains valuable real-world syntax/semantic evidence, but its incomplete entry graph is not itself an accepted compile-success oracle until its licensed dependency closure exists.

Scope

• Implement lowering for the frontend-neutral HIR constructs introduced/required by [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 through the existing Wright HIR -> WIR -> Workshop path.
• Add wright compile support for the declared OSTW source/project boundary through the same driver/session contract as OPY and raw Workshop.
• Preserve observable semantics covered by [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 and its pinned probes, including variable allocation, user enums, functions/defaults, rule priority/order, control flow, expressions, named/default Workshop calls, and player-variable access where supported.
• Produce valid en-US Workshop through the existing Wright Workshop emitter; do not create an OSTW-specific Workshop backend.
• Consume canonical Wright Workshop catalog/signature metadata; do not reintroduce an OSTW-owned duplicate Workshop game-content table.
• Validate forward compilation against [M13 correctness] Rebaseline OSTW corpus oracle around explicit compile roots #122's explicit-root accepted reference targets using semantic/normalized evidence, not byte identity or optimizer/temp-variable identity.
• Require Wright-emitted Workshop to parse and reach the declared semantic round-trip/fixed-point contract for the supported target surface.
• Add deterministic forward-compilation/differential gates to CI using explicit-root evidence.
• Document the first declared OSTW compile support matrix and known limitations based on what actually passes.

Non-goals

• Claiming the incomplete protect-ban entry graph compiles when the pinned reference rejects it on missing dependencies.
• Copying or synthesizing unlicensed OSTWUtils code to manufacture a passing corpus.
• Optimizer parity, identical variable allocation names, formatting parity, or byte-identical Workshop output.
• Classes/generics/lambdas/pattern matching outside the [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 boundary.
• Workshop -> OSTW reconstruction.
• Multi-locale output.
• Upstream .NET/OSTW runtime dependency in supported production compilation.

Acceptance criteria

• wright compile compiles the explicit-root accepted OSTW target(s) established by [M13 correctness] Rebaseline OSTW corpus oracle around explicit compile roots #122 using only Wright production binaries/libraries.
• The resulting Workshop is semantically equivalent under Wright's declared compatibility contract to the corresponding pinned v3.4.0 explicit-root reference result.
• All [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 HIR constructs included in the declared target surface lower through shared HIR/WIR/Workshop semantics without an OSTW-specific backend.
• Normalized/differential evidence is deterministic and CI-protected; formatting/temp/optimizer differences are not correctness failures by themselves.
• Wright-emitted Workshop reparses and reaches a semantic fixed point under the declared Workshop round-trip contract.
• Documentation distinguishes accepted compile targets, real-world reference-rejected/incomplete corpus boundaries, and syntax/semantic-only evidence.
• Existing OPY/Workshop behavior and compatibility gates remain green.

Relationships

• First end-to-end forward-compilation child of [M13] Source-language interoperability and OSTW compatibility #90.
• Depends on [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 semantic HIR and [M13 correctness] Rebaseline OSTW corpus oracle around explicit compile roots #122 corrected oracle semantics.
• Must be accepted before PM decomposes Workshop -> OSTW reconstruction or claims broader OSTW interoperability.
• [M13] Integrate the accepted OSTW semantic surface with Wright tooling services #120 tooling integration may proceed independently once [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 is accepted.

[Teakowa]

Evidence: first declared OSTW → Workshop compile surface (commits 36884ee, 0d17281, 42d1ea7, 1377db9, 8964657 on main)

Acceptance criteria → evidence

• Native wright compile for the [M13 correctness] Rebaseline OSTW corpus oracle around explicit compile roots #122 accepted targets: wright compile --root compatibility/ostw/probes/<target> <target>/main.ostw compiles p4-types-expressions, p5-functions-control, and p6-catalog-signatures using only Wright production binaries — OSTW frontend → shared wright-ir lowering → shared wright-workshop emitter (no OSTW-specific backend).
• Semantic equivalence vs pinned v3.4.0 explicit-root evidence: crates/wright-ostw/tests/differential.rs compiles each target, parses the committed reference emission (workshop.entry-only.txt) through the shared Workshop parser, applies the declared normalization to both sides, and requires structural equality of rule bodies. Report: target/wright-ostw-differential-report.json (all three status: parity, roundTrip: fixed-point). The declared normalization is documented in docs/ostw/support-matrix.md (constant folding incl. x || true domination, write-once per-call player-variable inlining, foreach-counter globalizing, null/unit vector idioms, <0>≡{0} placeholders, Team≡Team-color, init-rule names).
• Shared HIR → WIR → Workshop, no OSTW-specific backend: all [M13] Resolve and lower the accepted protect-ban OSTW semantic slice into HIR #118 constructs lower through wright-ir/wright-workshop — value/void function inlining with the reference-shaped per-call player-variable argument materialization and call-site defaults, statement-bodied value-function side-effect hoisting, C-for/foreach → For Global Variable, switch → the reference Skip-array dispatch (jump table computed over emitted action counts, fallthrough, break = Skip, default = last body), rule return → Abort, rule-priority ordering, user enums → 0-based integers, ternary → If-Then-Else, casts → pass-through, named/default catalog argument binding via new probe-evidenced paramDefaults metadata.
• Deterministic, CI-protected differential + round-trip: new CI job ostw-compile-differential runs the suite and uploads the report; each target also asserts the declared round-trip fixed point (Wright-emitted Workshop reparses and re-emits byte-identically).
• Documentation: docs/ostw/support-matrix.md declares the accepted surface, lowering decisions, normalization contract, and deterministic rejection boundaries; docs/cli.md, docs/ostw/compatibility-baseline.md (phase C marked implemented), docs/workshop/catalog-pipeline.md (paramDefaults), compatibility/ostw/probes/README.md updated.
• Existing gates remain green: full CI green on main (Rust quality stable + 1.85.0, v1 gates, OverPy oracle, adapter, native-vs-reference differential, OSTW reference baseline, distributions).
• Non-goals respected: no protect-ban entry-project compilation claim (rejects at the three missing ../OSTWUtils/… imports, matching the pinned reference), no OSTWUtils source, no classes/generics/lambdas, no optimizer/formatting parity claims, no Workshop → OSTW reconstruction.

[Teakowa]

PM acceptance

Accepted against current main (8964657).

The forward OSTW boundary now satisfies #119:

• p4-types-expressions, p5-functions-control, and p6-catalog-signatures compile natively through OSTW frontend -> shared HIR/WIR -> shared Workshop emitter;
• the differential suite compares normalized semantics against the explicit-root pinned v3.4.0 evidence from [M13 correctness] Rebaseline OSTW corpus oracle around explicit compile roots #122 and reports parity for all three targets;
• Wright-emitted Workshop reaches the declared round-trip fixed point;
• the dedicated OSTW compile differential (#119) CI job is green on current main;
• stable/MSRV Rust quality, OSTW reference baseline, OPY/reference gates, and all distribution legs are also green;
• protect-ban entry-project compilation remains correctly unclaimed because its external OSTWUtils imports are unresolved/reference-rejected;
• no OSTW-specific Workshop backend or upstream runtime dependency was introduced.

The implementation and #120 tooling work shared a commit boundary, but the resulting architecture remains the intended shared-session/shared-HIR design.