🐛 Fix jeff status return placement

[burgholzer]

🤖 AI text below 🤖

Summary

• Insert the synthesized Jeff status return at the original terminator position.
• Add a regression for result-less Jeff entry points with operations in the body.
• Treat mlir/** changes as Python-relevant so binding-level tests and lint run on affected pull requests.

Root cause

The entry-point restoration introduced in #1934 created the replacement func.return at the current rewriter insertion point, which remained near the start of the block after creating the zero status constant. Result-less Jeff programs therefore placed operations after the terminator and failed conversion.

The original pull request did not expose this through Python because the shared change detector did not classify mlir/** changes as Python-relevant, so all Python jobs were skipped.

Impact

Serialized result-less Jeff programs can again be compiled through the Python compile_program entry point. Future MLIR changes will exercise the Python bindings in pull-request CI.

Validation

• Jeff round-trip suite: 117 passed
• Jeff entry-point regressions: 2 passed
• Exact failing Python test: 1 passed
• Full Python suite: 394 passed, 3 skipped
• Repository lint and GitHub workflow validation: passed
• git diff --check: passed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!