fix: call ColumnCard hooks unconditionally, enforce lint in CI

[aaronjmars]

What

npm run lint was reporting 26 errors and 7 warnings on main. ESLint was already configured — CI just never ran it, so the tree drifted. This gets it to zero and wires it into CI so it stays there.

The bug worth reviewing

ColumnCard returned its "Unknown column type" card at column-card.tsx:106, above ~10 useMemo/useRef/useEffect calls. A column's type resolves through the plugin registry, so type can flip between renders — which changes hook order and crashes the component. Moving the bail-out below the hooks clears all 14 rules-of-hooks errors at once. The hooks above already tolerate a missing type (paginated optional-chains; the refresh effect has its own guard).

Three refs were also assigned during render. That's unsafe under concurrent rendering — a render that never commits would still have written. Now synced in effects; the useRef seeds cover the first frame and both consumers only dereference asynchronously.

Suppressed, not fixed

Three set-state-in-effect reports are disabled with inline rationale, because a mechanical rewrite would change behavior:

• sticky search-open — deriving searchOpen || searchActive would auto-close the row when the query is cleared mid-type, which is exactly what the existing comment rules out
• / shortcut routed through the store — an external signal, no render-time value to derive from
• snapshot fetch-on-open — properly removing the cascade means moving it behind Suspense

Happy to do the Suspense refactor separately if preferred.

Cosmetic

6 unescaped entities → HTML entities. Removed MODE_LABELS from producthunt/client.tsx — verified dead, every other plugin references its own.

Config

Added argsIgnorePattern: "^_" to no-unused-vars. The six plugin ConfigForm(_: ConfigFormProps<…>) params are deliberately unused and already say so with _ — a convention gap, not six bugs.

CI

New Lint & Test job (eslint --max-warnings=0 + vitest), parallel to Build so lint failures report without waiting on the production bundle. --max-warnings=0 holds the line now that the tree is clean. The build job id is unchanged in case any required check references it.

Verification

npm run lint clean · 279/279 tests pass · TypeScript + npm run build succeed. No behavior changes intended — the hook reordering is the only semantic change, and it strictly widens when hooks run.