Textures: the texture field shows only pictures, an old animation id appears as <id>? (#143); check total 1034

Development.md

@@ -12,7 +12,7 @@ npm run check        # typecheck + lint + format:check + tests, the gate CI runs
                      #   code is lost (tail's is reported), so a red run reads as green
 npm run build        # writes dist/ and regenerates index.html
 ./build.sh           # the same under `set -o pipefail`, for callers that pipe the output
-node tools/seed-e2e.mjs && node tools/e2e.mjs                 # 1032 editor checks, screenshots in /tmp/gm-e2e-*.png
+node tools/seed-e2e.mjs && node tools/e2e.mjs                 # 1034 editor checks, screenshots in /tmp/gm-e2e-*.png
 GM_STEPS=20 node tools/e2e.mjs                                # or 1-12, or 6,20 — a subset while working on one step
 ./e2e.sh start [GM_STEPS]                                     # the same run detached, see below
 ./e2e.sh status                                               # live progress, or the last run's result

Textures.md

@@ -5,6 +5,11 @@ design: because it is an ordinary property, instance overrides, **Apply to conta
 One coin instance can wear a different picture than its nine siblings, and swapping a texture
 at runtime is a graph node that already exists.
 
+**The Texture row offers pictures only:** every texture, each followed by its frames. An
+animation is played, not worn (see [Animations](Animations)), so it is not in the list. A
+project from before that change may still hold an animation id in the field; it reads as
+`<id>?` like any other dangling reference and draws the plain colour.
+
 **Getting an image in.** **Dropping image files onto the canvas** or **Ctrl+V** pasting one
 uploads it and makes the asset in one go; several files at once are imported one after another,
 and a file that fails does not stop the rest.