Extract Alpine.data components

Before choosing a tool or writing more code, make the requirement concrete. Every issue editor uses the same focused factory with explicit initial values rather than copying a large inline object.

Alpine.data() gives a component a named factory, initialization, methods, getters, and a testable JavaScript home. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.

A common failure is to extract every two-line component and create a registry of abstractions nobody can navigate. The happy path may still work, which makes the mistake easy to miss. extract when behavior repeats or markup becomes hard to read, and pass only the initial inputs the component owns. Keep the first version small enough that every important input and output remains visible.

This supports the module goal: Extract reuse only where it clarifies the board, keeping local components local and global state rare. Capture the request, command, trace, screenshot, test result, or other evidence that proves the result.

Build two editor instances with different starting data and prove their state remains independent. Change one condition on purpose, predict the result, and compare the prediction with what actually happened.