Manual-link fallback now includes libaero; batch runs write only numbered result sets

Two small behaviours of the amesim MCP server, both changed in amesim-mcp commit f2f57f4 on 2026-09-03 on Simcenter Amesim 2511.

The manual-link fallback links libaero

AMEGenerateCode()'s native link can fail for the M6DOF and EMD libraries (6-DOF body, electric motor drive). amesim_build catches that and replays the link itself with gcc from %AMESIM_ROOT%\sys\mingw64\bin\gcc.exe, adding the missing archives inside a --start-group ... --end-group. The archive list was -lM6DOF -lEMD plus the SIG, MEC, AME, AMESOL and solver archives.

As of f2f57f4 the group also links libaero. A 6-DOF flight model that uses the aero library failed the replayed link with unresolved aero symbols until it was added. The build result still reports "method": "manual_link" or "native" so the path taken is visible in the response.

Batch runs write only numbered result sets

A batch run (several parameter sets in one submission) writes only numbered result sets: .results.1, .results.2, and so on. There is no unnumbered "current" set after a batch, so a reader that looks for the plain set finds nothing and reads as "the run produced no results".

amesim_get_results now defaults to the first numbered set when no set is named. Pass the set index explicitly to read any other case. amesim_result_sets (AMEOpen) lists every set a model has, which is the honest way to see what a batch produced before choosing one.

Why both are on this page

They share a failure shape: a call that returns without error while the artifact is missing, an unlinked library or an absent result set. In both cases the fix was to make the tool say which path it took rather than to make the failure quieter.