fix: count severities correctly, gate remote-ref on $id, order --strict checks

Copilot review round 5.

- The sidebar tooltip applied `hasError` to the TOTAL, so a tool with one
  error and three warnings announced as "4 schema portability errors" —
  a defect the previous round introduced while adding that wording, and
  worse than the vague text it replaced. Both the tooltip and the
  accessible label now carry the breakdown, formatted by a new shared
  `summarizeToolFindings` so the fourth place to phrase a severity count
  cannot drift from the other three.

- Suppress `remote-ref` when the document declares an `$id` anywhere.
  `$id` establishes a base URI, so with a root `$id` of
  `https://example.com/root` the ref `https://example.com/root#/$defs/x`
  resolves to THIS document and needs no fetch — the finding and its
  "inline the referenced schema" remediation would both be wrong.
  Classifying correctly needs full RFC 3986 resolution against nested
  embedded resources, which this module does not do, so it declines
  rather than guessing. A missed finding is the acceptable direction.

- Run the `--strict` validations before every short-circuit return.
  `servers/list`, `servers/show`, `--list-stored-auth` and
  `--print-handoff` all return from `parseArgs` before any connect, so
  the checks further down let `--strict --method servers/list` succeed
  while silently ignoring a tools/list-only flag.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UL9retfvAXRgvi6EWk4SY4
Signed-off-by: cliffhall <cliff@futurescale.com>

clients/cli/__tests__/schema-lint-report.test.ts

@@ -255,6 +255,20 @@ describe("--strict argument validation", () => {
     ).rejects.toThrow("--strict requires --method tools/list.");
   });
 
+  it.each([
+    ["servers/list", ["--method", "servers/list"]],
+    ["--list-stored-auth", ["--method", "servers/list", "--list-stored-auth"]],
+  ])(
+    "is rejected on the %s short-circuit path, which never reaches the lint",
+    async (_label, extra) => {
+      // These return from `parseArgs` before any connect, so a validation
+      // placed further down would let `--strict` be accepted and ignored.
+      await expect(
+        runCli(["node", "cli", "--cli", "--strict", ...extra]),
+      ).rejects.toThrow("--strict requires --method tools/list.");
+    },
+  );
+
   it("is rejected alongside --app-info rather than silently ignored", async () => {
     // `tools/list --app-info` returns NDJSON straight from `runMethod` and
     // never reaches `emitResult`, so accepting the pair would hand a CI caller