[milanb17]

Since #1498, a hand-made animation whose wb-node elements are placed absolutely and take a data-form draws every node in normal flow: the nodes stack and overlap, and the SVG arrows drawn at fixed coordinates point at empty space. animation.md invites data-form on a wb-node in a hand-made layout, so this is the documented use.

The cause is the kit's :is(.wb-card, .wb-node)[data-form] { position: relative; }, which weighs two classes (0,2,0) and beats an agent's .node { position: absolute } (0,1,0).

The fix

The form, change, outline and colour rules in animation-stage-kit.ts now match through :where(.wb-card, .wb-node)[…], so they weigh one class:

• They tie with the base .wb-card, .wb-node rule and win by coming after it, so a form's padding, radius and ::before/::after still draw when the agent sets nothing.
• An animation's own CSS comes after the kit (it is in the body, the kit in the head), so any single-class rule an agent writes wins.
• The change marks move with them, so the kit keeps its order among these rules: a colour still sets the border after a change stripe, as before.
• Tones and highlights keep their two-class weight and still take over during a frame.

The scene's own cards are unchanged. .wb-scene > .wb-card keeps them relative, and the legend glyphs have their own two-class rule. The resting frames of request-across-layers and cache-fill-evict (window, bars, cylinder, drum, change stripe, legend) are byte-identical before and after.

Test

blocks.browser.test.tsx adds a 720×420 .architecture layout with two node wb-node cards (data-form="bars") at #a{left:12px;top:10px} and #b{left:262px;top:162px}. The stage reports through the code slot's width whether both kept their position. The test fails on main and passes with the fix.