[lxsmnsyc]

Adds an Issues tab that lists what the Solid runtime reports on OBSERVE.diagnostics, such as a signal read outside a tracking scope. Today these findings only appear in the console. This PR is based on #27, since the panel uses its copy button.

Changes

• An Issues tab sits after Errors. It is not named Warnings, since it lists errors, warnings and info. Its badge counts every time a finding was reported.
• Equal findings, such as the same read in each render of a component, are one row with a count. Entries are capped at 200, newest first.
• Rows can be filtered by severity (errors, warnings, info), or searched by code, message and owner.
• The detail shows the kind, owner path, node name and when it was first and last seen.
• Show in the ownership tree and Show in the reactivity graph select the owner or node the finding is about. The graph link only shows for signals and computations.
• Open the repair guide links to the code's section, from DEV.guideUrl.
• The copy button puts a Markdown report of the finding on the clipboard, with sensitive data redacted.
• The toolbar joins the channel during setup instead of in onSettled, so findings from the first render are kept even while the dock is closed.
• The runtime calls the listener inside the scope that misbehaved, where a signal write would be a finding itself. Findings are batched and written on a microtask.
• Owner paths start at the app's first component. The toolbar's own owners (<DevToolbar> › <Errored> › … › <AppScope>) are dropped.
• An entry holds its node weakly and keeps the latest one, since an earlier node can be disposed.
• The test fixture has an "emit warning" button that renders a component reading a signal in its body.

Findings from server rendering (SSR_*) are reported on the server, so they do not reach this panel.

Testing

• Unit tests in src/dev-toolbar/issues/tracker.test.ts cover grouping, the limit, owner path trimming and the report.
• A new e2e test emits a real STRICT_READ_UNTRACKED, then checks the count, the trimmed owner path, the severity filter, the repair guide link, the jump to <DraftReader> in the ownership tree, and clearing.
• pnpm test, pnpm typecheck, pnpm format:check, pnpm build, pnpm check and the full e2e suite pass locally.
• Checked by hand in Chromium against the fixture.

🤖 Generated with Claude Code