Add purposeful transitions

The issue panel fades briefly, and the stylesheet removes nonessential motion for reduced-motion preferences. That contrast gives us something useful to test instead of a rule to memorize.

A transition should help the user understand what appeared or disappeared, not delay access to information. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.

The happy path can hide a bad design: you can animate every property and force long movement before content becomes usable and still get one successful demo. Push past the demo. transition cheap visual properties, keep timing short, and provide an equivalent low-motion experience, then test the condition most likely to prove the choice wrong.

The module is moving toward one outcome: Render dynamic issue rows without losing identity, focus, or respect for reduced-motion preferences. Save the before-and-after evidence now; it will make the final project review much more honest.

Test the interaction with normal and reduced-motion settings and verify focus never waits for animation. Save the evidence, then explain which requirement would force you to choose a different design.