feat: Implement Phase 18 palette image icons and update asset card functionality

2026-10-14 18:08:06 -04:00
parent b7235c503d
commit ba85a967e3
11 changed files with 185 additions and 7 deletions
@@ -34,7 +34,9 @@ description: "Stickman Studio feature workflow: UI/UX and architecture specs, im
   - `@developer` updates code and scenes using targeted diffs based on `docs/specs/[feature-name].md`.
   - `@developer` runs Godot syntax/import checks and focused existing regression suites, then fixes failures.
   - `@developer` adds focused automated coverage where it can meaningfully verify the feature's observable acceptance outcomes. For cross-system or runtime behavior, construct a small repeatable scene or fixture (in memory or as a saved scene), use the real production spawning/input/action paths where practical, advance frames or physics ticks, and assert the resulting state. A check that nodes, signals, layers, or helper calls exist is insufficient when the requirement concerns what actually happens during play.
-   - When the outcome is visual or interactive, run the affected scene and inspect rendered output or a capture where the environment permits. Record what was observed; a headless launch or successful screenshot command alone does not prove visual correctness. If rendering or GUI access is unavailable, report that limit explicitly and leave a focused visual check for the user.
+   - For visual or interactive acceptance criteria, establish the verification route before concluding Phase 2: run the affected scene in a render-capable GUI session, capture the states named in the spec, and inspect the rendered pixels. Record the scene/state, capture location, and what was observed. A successful launch, headless run, or screenshot command/file by itself does not prove visual correctness.
+   - For interactive acceptance criteria, exercise the real production input path through the scene and controls where practical. Advance frames or physics ticks as needed, then assert the resulting world/UI state and relevant cleanup or cancellation behavior. Signal/helper checks alone do not verify the user interaction.
+   - If the environment may not support rendering or input, try to establish whether a GUI, capture, or input-automation route is available; do not infer that it is unavailable from a headless run alone. If verification still cannot be performed, record what was attempted and the specific limitation, mark the affected acceptance outcomes unverified, and leave a focused, reproducible user check. Do not report the feature as fully agent-verified while required outcomes remain unverified.
   - `@developer` reruns the relevant checks after fixes and reports commands, pass/fail results, the measured behavior, and any unverified acceptance outcome. Do not claim a feature is verified from syntax checks or debug prints alone.

 6. **Phase 3: User Hand-off (Stop)**