chore: npm audit fix and ESLint 9 migration

[redreceipt]

Summary

• Apply npm audit fix and upgrade ESLint to 9 with Next.js flat config.
• Resolve lint errors related to form values, prop mutation, and effect state updates.
• Address lint warnings (a11y, hooks deps, display names, Link usage).

Testing

• npm run lint

Vercel Preview Validation Plan (E2E Click-Around)

• Home: load, scroll, verify hero + CTA buttons; click a few nav items and ensure pages render.
• Auth modal: open sign-in, submit invalid/valid identity, verify transitions.
• Content pages: open a universal content item, ensure HTML renders and links work (including my.longhollow.com links if authenticated).
• Watch: open /watch, verify primary/secondary buttons, click a message card, load more videos.
• Profile: open profile page, confirm sign-in redirect/modal behavior, verify form fields update and save.
• Video player: open a page with video, verify play/pause and controls show/hide.
• Global: ensure no console errors; 404 page renders.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
longhollow-web	Ready	Preview, Comment	Dec 20, 2025 4:13am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Video player disposed on every parent rerender

The useEffect now depends on onError and returns a disposer, so any parent rerender that recreates the handler (e.g., onError={() => setPlayerError(true)} in MediaContentItem) triggers the cleanup, disposes the player, and then re-enters the effect with the stale player reference still truthy. Because no new player is created, the subsequent player.src call runs on a disposed instance, causing playback to stop or throw as soon as the parent component updates state (selecting a carousel item, handling errors, etc.).

Useful? React with 👍 / 👎.