console_warning is the only signal for a GSAP selector that matches nothing — and the message omits the selector

Two related requests about hyperframes check, filed separately from the audio-dimension gap (#2775 already covers that one). This comes from a 42s general-video run on Windows. Root theme: check reports success for deliverables that are broken in ways it does model — but at a severity that does not gate.

Verified against 0.8.155 and 0.8.159.

Observed

A gsap.fromTo('[data-part="reco-title"]', …) was authored against an element that had class="reco-title" but no data-part attribute. The selector resolved to zero elements. The only report was:

⚠ console_warning: GSAP target  not found. https://gsap.com

Note the double space — the selector name is empty in the message, so the warning does not say which target was missing. It is a warning, not an error, so check still reported Check passed, and the dead animation survived several build/verify cycles before being noticed.

Why this matters more than it looks

An animation targeting nothing is a silent partial failure: the composition renders, every other element animates, and one beat simply never happens. There is no visual smoking gun in a contact sheet unless you already know that beat was supposed to move.

Requests

1. Include the selector text in the message when it is available. Warning text GSAP target not found with an empty name is not actionable.
2. Offer a way to escalate. check already has --strict; consider whether console_warning for a non-resolving selector should be an error under --strict, since it is deterministic (the DOM is known at check time) and never intentional.
3. Optionally, a dedicated rule code (e.g. gsap_target_not_found) rather than folding it into generic console_warning — that would let projects escalate it selectively. In this workspace, across 59 accumulated check reports, console_warning fired 45 times while the busiest rule (canvas_overflow) fired 388 — so console_warning is a low-frequency catch-all that nonetheless carried the only signal for a completely dead animation.

Related but separate

• The missing audio dimension of check (silent renders passing green) is already tracked in Audio pipeline: reused narration silently dropped + voice-clip seam collisions — both pass every check #2775 — not duplicated here.
• For the run that produced this case, a 34s–42s single-file general-video with 3 sub-compositions and 6 audio segments, every other check dimension passed: 0 error(s), 0 warning(s), 318/318 text checks pass WCAG AA.

Environment

• Windows 11 · hyperframes 0.8.155 (also present on 0.8.159) · Node v22.14.0
• Driver: gsap (bundled assets/vendor/gsap.min.js), selector-based targets