[Bin-Huang]

A Halloween theme built around one shareable moment: when an agent in another pane needs you, the sidebar jack-o'-lantern turns its eyes to that pane and its candle flares.

What's in it

• Art: a locked 24-colour palette (palette.gpl) and hand-placed sprite sheets with their sequences in apps/web/src/themes/halloween/art/sheets (PNG + JSON, editable in Aseprite). One art pixel = 4 CSS px; the scene crops, never scales. Rules: art/README.md.
• Player: player.ts picks frames from the hand-made sequences; scene.tsx stacks the layers on a 60×64 canvas shown 4× with image-rendering: pixelated.
• Behaviour: alert on a working → done/error transition in an unfocused pane; reduced motion holds still; the scene rests when the window is unfocused or idle for 30 s.
• Layout: the scene keeps at least 192 px; long page lists scroll instead of hiding the pumpkin.
• Showcase: ?theme=halloween&showcase=<ms> in the demo build freezes a scripted 6 s loop with real, path-scrubbed Claude Code and Codex screens; scripts/halloween-showcase.mjs exports the PNG (byte-identical across runs) or the MP4.

Checks

• npm test in apps/web: every sheet pixel is opaque or transparent and in the palette; player rules. (382 tests pass.)
• npx playwright test in apps/web, by hand: scene snapshots at dpr 1 and 2 for the share pose, a 480 px window and a 60-page sidebar. (6 pass.)

Numbers (contrast with real Claude Code/Codex output, idle CPU, flashing) and the launch plan: docs/halloween/README.md.

Not done / not verified

• Idle CPU with the window visible and the scene resting is not measured yet (scripts/halloween-cpu.sh). Animating costs ~3% of a core, over the 0.5-point budget; resting is the mitigation.
• PEAT was not run (no Windows machine).
• The in-app invitation and wind-down cards are a proposal, not built.