Evaluate plugins and CSP

The board adopts a focus helper only after native focus handling becomes genuinely complex and verifies the deployed CSP. This is a small part of an accessible issue board that filters, edits, persists, and progressively enhances server-rendered HTML, but the boundary it creates affects everything that follows.

Plugins extend Alpine with focused capabilities; stricter Content Security Policy can change how expressions are evaluated. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.

Watch for one shortcut in particular: trying to install plugins preemptively or weaken CSP just to preserve convenient inline expressions. It makes later failures harder to locate. Instead, measure the need, read the plugin and CSP constraints, and test the exact production build and policy. Prefer an implementation you can explain from the outside before optimizing it.

Keep the wider goal in view: Extract reuse only where it clarifies the board, keeping local components local and global state rare. A short observation with concrete evidence is more useful than a confident sentence with no reproduction path.

List the code and policy impact of one plugin and decide whether the native implementation remains simpler. Hand the result to someone else and see whether the behavior is clear without an oral explanation.