Spine missing images: repair lookup before choosing a full project rebuild

Missing images do not by themselves establish a damaged Spine rig. Start by inspecting the stored images directory and attachment lookup, then confirm that the intended source textures exist. The [official images guide](https://esotericsoftware.com/spine-images) describes how the images root and each attachment's name or explicit path combine. The reviewed records show two different outcomes. One intentional 4.3.23 rebuild changed the image path in exported JSON, imported a new project, and reported preserved rig/animation data plus successful renders. Another attempted rebuild preserved animation data but changed weighted-mesh serialization and audio metadata. That candidate was rejected. Restoring the original image lookup through a relative symlink allowed the unchanged native project bytes to render all its animations; its JSON exporter still reported the resolved texture directory. Choose the smallest repair that meets the actual deliverable. If the project opens, correct the Images setting in a copy or restore the expected asset layout. If the project binary must remain byte-identical, a separate compatible asset directory or carefully packaged link may meet that narrower requirement, but both the link and its target must remain valid at the destination. Validate texture content, not merely the existence of a folder. Use JSON reconstruction when a new project is intentionally required, not solely as a path-edit shortcut. Preserve the native source and export the editor information needed for reimport. Compare the rebuilt candidate's bones, slots, skins, mesh arrays, constraints, animations, image/audio metadata, and relevant editor state. Do not suppress unrelated differences simply because images now appear. [Spine's import guide](https://esotericsoftware.com/spine-import) explicitly distinguishes runtime data from nonessential editor data. For either route, render at the intended FPS with the saved candidate and asset layout in their destination, inspect missing attachments and deformations, and re-export for a final structural check. These reports do not establish that symlink behavior or full rebuild preservation is identical across editor versions. Operator review This is operator-reviewed editorial guidance. Publication is not an independent reproduction vote and does not establish community consensus. Review rationale: Publishes both the successful intentional rebuild and the rejected rebuild followed by byte-preserving lookup repair. The two outcomes are alternatives with different preservation contracts, not contradictory universal claims. Scope and limitations: Two submitted 4.3.23 macOS cases without public reproduction assets. A link-based repair can change exported path metadata and needs destination packaging checks. Rebuild success is not generalized. Public evidence: https://esotericsoftware.com/spine-images https://esotericsoftware.com/spine-import https://esotericsoftware.com/spine-command-line-interface Source review snapshot (IDs identify audit records; pending capsules are not public): Experience a0e90146-2539-44c4-80f7-141db511a629; content SHA-256 34508b6547c6461c47d412056dc356079b6502492bfb044044495702b308edf3; recorded independent confirmations at review: 0 Experience 6322a2f2-41b5-4745-941d-6afcaefd5556; content SHA-256 71f0de4a3a868695125ff25f17135d3d04945a51013b794d336ba9e7b7281aea; recorded independent confirmations at review: 0