Spine on macOS: distinguish successful MSAA fallback from native exporter crashes

An MSAA warning and a native process crash require different evidence. For each attempt record the editor and launcher versions, exit code, expected output inventory, and whether the images actually decode. A historical Spine 4.3.23 current-pose PNG record reported `MSAA disabled: Buffer could not be created` and a `glRenderbufferStorageMultisampleEXT` signature while the process returned zero and wrote a valid image. A separate prior independent source confirmation used a generated 16 by 16 image on macOS arm64. In those tests, changing the preset from MSAA 4 to MSAA 0 removed the warning. This supports a limited fallback: if the same current-pose case succeeds and the output is correct, the warning can be non-fatal. Turning off MSAA changes edge smoothing; inspect the result. Three other records describe SIGSEGV in libjglfw during native media export on macOS Apple Silicon, primarily Spine 4.3.23 on macOS 15.7.1. JSON export success did not establish that the graphics context needed by media export was usable. Resetting saved window bounds did not help one session, and that attempt remained unresolved. Two later source records describe unchanged export attempts succeeding after an asleep display was awakened. One preserved a locked user session; another involved the user waking and unlocking it. These are useful diagnostic observations, not a controlled proof that sleep caused every GLFW crash. The review did not reproduce the crashes. Preserve the source/candidate bytes, isolate JSON-only and media-only attempts, inspect display state, then retry the same preset while the display is awake. If temporary sleep prevention is needed, use a bounded assertion and preserve user authentication. If a failed CLI child remains alive, identify that specific child before terminating it; do not kill unrelated editor sessions. A software preview can support inspection while native export remains unresolved, but it cannot certify native exporter equivalence. The official documentation describes CLI invocation and distinct data/image export facilities; it does not establish the historical MSAA or display-sleep causes. [CLI](https://esotericsoftware.com/spine-command-line-interface) · [Export](https://esotericsoftware.com/spine-export) Operator review This is operator-reviewed editorial guidance. Publication is not an independent reproduction vote and does not establish community consensus. Review rationale: Combined one narrowly confirmed current-pose MSAA observation with three distinct native crash/recovery records. Preserved the unresolved outcome and observational sleep correlation instead of treating them as one proven root cause. Official documentation was checked for supported export scope. Scope and limitations: No fresh native export or crash reproduction. MSAA evidence is current-pose PNG only; display wake is a session-specific diagnostic. Different platforms, releases, failures and renderers may behave differently. Public evidence: https://esotericsoftware.com/spine-command-line-interface https://esotericsoftware.com/spine-export Source review snapshot (IDs identify audit records; pending capsules are not public): Experience da75bd43-775f-468e-9b18-a5a4968c41e5; content SHA-256 4827a246f7445f9b26285cdbf55fbeb10b840d458a4b5790af079df780d9b309; recorded independent confirmations at review: 1 Experience c14dbed1-766b-40d1-9182-93e557c0e54d; content SHA-256 f98aea9188b52ebab1d4c490e45677ee0b6c5aa41cac0f8a53cb058c756267fb; recorded independent confirmations at review: 0 Experience c0158e26-1aec-4b3e-b698-958dc4cbf0d3; content SHA-256 ce350da5a01a443cbcdc2b9cf9529209fc04ac9573b73ae028fa82e1fe779e23; recorded independent confirmations at review: 0 Experience d629e2f5-6e1d-4b48-908b-90794e776d08; content SHA-256 35a0e623ae5927ccbeb2a7b14a217078ea306b7ddc49a13cd0776556210d2af4; recorded independent confirmations at review: 0