chore(lint): hold tests to their own max-lines ceiling (#1306)

* chore(lint): hold tests to their own max-lines ceiling

The flat 400-line cap treated a spec like a component. A spec is a flat
list of independent cases, so hitting the cap there produces arbitrary
`-2.spec.ts` splits and hides coverage instead of surfacing design debt —
65 of the 138 files over the limit were tests.

Production code keeps 400. Tests (`**/*.spec.ts`, `**/*.e2e.ts`, and
everything under `apps/*-e2e/**`) get 1200. Blank lines and comments no
longer count, so a docblock can't be the reason a file must be split.

Both limits now live in tools/eslint/max-lines-config.mjs, imported by
eslint.config.mjs and the baseline generator alike. The generator decides
who belongs on the list by running ESLint's own max-lines rule instead of
counting lines itself — a private reimplementation would disagree with the
rule the moment either side changed (a `//` inside a template literal is
enough) and yield a baseline that turns CI red while looking correct.

The baseline drops 126 -> 68 entries with nothing added, and six now-dead
`eslint-disable max-lines` directives are removed. A new eslint-tools test
asserts the committed baseline still matches what the generator produces,
so a stale entry or a forgotten regeneration fails CI.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* chore(lint): classify eslint-tools in the coverage policy

A project with a `test` target must be assigned a coverage tier, so
adding eslint-tools broke `coverage:policy:check` before the unit suite
even ran. Tier B alongside packaging and release-tools: these are Node
tests over lint tooling, and a coverage percentage across a generated
list would not mean anything.

CI runs Tier B/C through its own `--run-non-tier-a` step, so the
baseline-consistency test executes there rather than being skipped.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

apps/electron-backend-e2e/src/performance/database-worker-post-gc-probe.spec.ts

@@ -1,5 +1,4 @@
 /* eslint-disable playwright/expect-expect -- These are Node assertion-based performance contract tests. */
-/* eslint-disable max-lines -- The one-shot transport contract keeps all terminal-path fixtures together. */
 import assert from 'node:assert/strict';
 import { EventEmitter } from 'node:events';
 import test from 'node:test';

apps/electron-backend-e2e/src/performance/m3u-import-report.test-helpers.ts

@@ -1,4 +1,3 @@
-/* eslint-disable max-lines -- The deterministic fixture keeps the full production-shaped import sequence visible. */
 import type { M3uImportRendererCaptureMetrics } from './m3u-import-renderer-capture';
 import type { MainCaptureMetrics } from './m3u-refresh-cancellation-contract';
 import type { M3uImportBenchmarkManifest } from './m3u-import-summary';

apps/electron-backend-e2e/src/performance/m3u-refresh-cancellation-report.ts

@@ -1,4 +1,3 @@
-/* eslint-disable max-lines -- Summary distributions and correlated phase derivation share one auditable schema mapping. */
 import type {
     CancellationBenchmarkManifest,
     CancellationBenchmarkSummary,

apps/electron-backend-e2e/src/performance/m3u-refresh-cancellation.benchmark.ts

@@ -1,4 +1,3 @@
-/* eslint-disable max-lines -- Benchmark lifecycle, local fixture server, and artifact safeguards stay auditable in one entry point. */
 import { execFileSync } from 'node:child_process';
 import { createHash } from 'node:crypto';
 import { once } from 'node:events';

apps/electron-backend-e2e/src/performance/m3u-refresh-renderer-capture.ts

@@ -1,4 +1,3 @@
-/* eslint-disable max-lines -- Renderer CDP and injected-page lifecycle are kept together so raw artifact boundaries stay auditable. */
 import { createWriteStream } from 'node:fs';
 import { writeFile } from 'node:fs/promises';
 import { join } from 'node:path';

apps/electron-backend-e2e/src/performance/xtream-renderer-probe.ts

@@ -1,4 +1,3 @@
-/* eslint-disable max-lines -- Playwright serializes this self-contained renderer probe; external helpers would be unavailable in page context. */
 import type { Page } from '@playwright/test';
 import {
     RENDERER_PERFORMANCE_PHASE_HOOK_KEY,