Fix PostHog Issues

Active PostHog error-tracking issues are mostly browser exceptions from the JS SDK, plus server-side $exception captures. In a Livewire / Alpine SPA most of them are transient navigation races, vendor throws, or browser noise, not bugs. Read the stack, the occurrence spread, and the session timeline, not the headline. Walk from the newest last-seen to the oldest.

Project context. Read .agents/posthog.md when the repo has one. It holds the project id, the before_send filter file, the app's registration patterns, and the precedent fixes. Then follow the repo's AGENTS.md / CLAUDE.md rules for tests, asset builds, cache clears, and a dirty tree.

1. Load the working set

Read references/posthog-mcp.md before your first PostHog call. It covers the single exec tool, the error-tracking tools, the status lag, and resolved vs suppressed. Stay on the project named in the project context: never switch projects. List active issues ordered by last seen.