Exercise generated compiler corpus across JASS and Lua

[Frotty]

Summary

• exercise the existing generated compiler corpus through every JASS optimization mode and Lua translation
• run 64 deterministic combinations of tuples, interfaces, modules, loops, and callbacks as a normal Gradle test
• require zero compiler diagnostics from both backends
• add direct core coverage for WurstOperator, LineOffsets, and WurstKeywords
• add index lifecycle coverage for MapWithIndexes and fix stale indexes when replacing a value
• retain the SmallCheck property for runners that support @Property
• include generated source in differential failures for immediate reproduction

Why

The existing SmallCheck properties are not discovered by the normal TestNG Gradle task; only ordinary tests ran. The executable corpus closes that gap and exercises the compiler pipeline across both backends. The utility tests cover previously untouched core classes and assert their semantic contracts.

Verification

• ./gradlew.bat test --tests "tests.wurstscript.tests.CompilerFuzzTestsSC": passed (3 tests, including the 64-program corpus)
• ./gradlew.bat test --tests "tests.wurstscript.tests.WurstOperatorTests" --tests "tests.utils.LineOffsetsTests" --tests "tests.utils.MapWithIndexesTests": passed
• no full suite run locally; CI remains responsible for the complete matrix

Known gap: this is a compile/diagnostic differential gate, not runtime equivalence testing. Follow-up work should add execution-level oracle cases and IM invariants for the highest-risk lowering passes.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-30T06:58:17.904185Z	14958ea	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Frotty]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 6c20b47008

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coveralls]

coverage: 71.468% (+0.4%) from 71.087% — codex/core-compiler-coverage into master

[Frotty]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 54f1a99781

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Frotty]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep them coming!

Reviewed commit: 14958ea86a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".