WORK-400
Setting up your dashboard 0 entities found · 9/32 branches scanned
ID:WORK-400Status:ready

Build warning for non-eager sandbox in a cover media zone

A cover-backdrop sandbox is inert (SPEC-090 posture demotion) and above the fold, so the WORK-381 activation affordances contradict it: visible is a no-op there and click's poster + "Run" control is a dead end on a pointer-events: none surface. Eager is the background mode; a non-eager sandbox under cover should warn at build time (SPEC-101 §5).

Priority:lowComplexity:simpleMilestone:v0.21.0Source:SPEC-101
claude/threejs-sandbox-backgrounds-env77o View source

Criteria completion

Criteria completion: 0 of 3 (0%) checked; tracking started on Jun 11, no incremental history yet0%25%50%75%100%Jun 11Jun 15

Tracking started Jun 11 — check back for trends.

Relationships

Implements 1
Related 6
Branches 2
claude/threejs-sandbox-backgrounds-env77o current ready
main doneclaude/spec-101-hero-cover-prism done
History 1
  1. a1580fa
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • A sandbox with activation="visible" or "click" that is a cover media zone's guest emits a build warning naming the conflict (inert backdrop vs. activation affordance) and the fix (drop activation, i.e. eager).
  • Eager sandboxes under cover, and non-eager sandboxes outside cover, warn nothing — no regression to the WORK-381 paths.
  • Unit test covers warn / no-warn cases.

Approach

SPEC-084-style validation in the engine's cover handling (packages/transform/src/engine.ts §6d already walks the cover media zone for posture demotion and the WORK-399 auto-fill — check the located rf-sandbox guest's data-activation there), following the existing warnInteractiveGuestInLink pattern.

References

  • SPEC-101 §5 · SPEC-090 (posture) · WORK-381 (activation modes)