Mesa 4 migration tracking

Summary

This issue tracks the Mesa 4 migration effort for mesa-llm in one place and helps avoid partial, inconsistent migration changes from being merged through unrelated PRs.

Mesa 4 support is not complete yet. Until this tracking issue is resolved, the project should remain pinned to Mesa 3.x.

Status

Mesa 4 support is not an active merge target right now. Mesa 4 is still in alpha (v4.0.0a0), and Mesa's current stable version is still 3.x. Mesa 4 development tracking issue is: https://github.com/mesa/mesa/issues/3132. We want to avoid merging partial or inconsistent Mesa 4 migration changes before the Mesa 4 API settles further.

[!IMPORTANT]
At this stage, mesa-llm is prioritizing maintenance work over Mesa 4 migration, with the near-term goal of closing existing maintenance bug tickets on Mesa 3.x.

Mesa 4 migration changes should be kept in dedicated Mesa 4 issues and PRs linked from this tracker.

If an otherwise unrelated PR includes Mesa 4 migration changes, those migration-related parts will not be reviewed as part of that PR and should be removed or split into a separate Mesa 4 PR linked here.

Related issues

• #150
• #152
• #197
• #205
• #216

Related PRs with Mesa 4 migration overlap

• #151
• #153
• #170
• #179
• #195
• #199
• #217
• #290

If I missed any related issues or PRs, please feel free to comment below and I’ll add them here.

This is a migration tracking issue, and it names no source files, tests, or entry points. Start by reviewing the linked Mesa 4 issue, related issues #150, #152, #197, #205, and #216, and overlapping PRs #151, #153, #170, #179, #195, #199, and #217. Done means Mesa 4 migration work is coordinated through dedicated linked issues and PRs rather than partial changes.