@reportforge/playwright-pdf 0.25.0 → 0.27.0

package/README.md

@@ -2,7 +2,7 @@
 
 > Playwright PDF reporter: generate branded PDF reports from [Playwright Test](https://playwright.dev/) results. Three templates (minimal, detailed, executive) for developers, QA teams, and stakeholders. CI-ready, self-contained, with embedded screenshots and charts.
 
-Drop it into any Playwright project and get a PDF report on every CI run. No changes to your tests.
+Drop it into any Playwright project and get a PDF report on every CI run. No changes to your tests. Testing with Python? The same reports ship as [`reportforge-playwright-pdf` on PyPI](https://pypi.org/project/reportforge-playwright-pdf/) for pytest-playwright, on the same license key (see [Python](#python)).
 
 [![npm](https://img.shields.io/npm/v/@reportforge/playwright-pdf.svg)](https://www.npmjs.com/package/@reportforge/playwright-pdf)
 [![Node](https://img.shields.io/node/v/@reportforge/playwright-pdf.svg)](https://nodejs.org/)
@@ -58,6 +58,7 @@ Three templates, one reporter. Every PDF is fully offline: fonts, charts, and sc
 - **Notifications**: post pass/fail summaries to Slack, Teams, Discord, or email after each run; configurable trigger (`always` / `failure` / `success`) per channel; email and Discord support optional PDF attachment via `attachPdf`
 - **Flakiness trend**: top-N flakiest tests table with per-test dot sparkline across stored history runs in the `detailed` template; `flakinessTopN` option (default 5, `0` disables)
 - **Pass-rate trend**: cross-run trend chart from stored history; opt-in `remoteHistory` keeps the trend alive on ephemeral CI runners by storing aggregate numbers only (pass rate, counts, duration, verdict; no test titles or error text, and the branch name never travels in plaintext), with no extra network calls
+- **Run-over-run diff**: every report shows what changed since the previous run on the same branch: new failures, fixed tests, and still-failing tests, and the same summary rides along in Slack, Teams, Discord, and email notifications
 - **Offline failure analysis**: sorts each failure into one of 7 root-cause buckets and renders a root-cause chip under each failed test in the `detailed` PDF (dominant-cause one-liner in `executive`). No network, no AI service: a small embedded classifier with automatic updates; pin it any time. Full details at [reportforge.org/docs/advanced/failure-analysis](https://reportforge.org/docs/advanced/failure-analysis).
 - **On-device training**: teach the classifier your team's failures without any data leaving your machine. Label locally-collected samples (`npx @reportforge/playwright-pdf label-feedback`), then `train-model` trains and cross-validates a personal layer on-device; it activates only when it measurably beats the base model on your own labeled set (`evaluate-model` shows the comparison any time). Commit the model file to your repo via `failureAnalysis.localModelPath` to share it with CI. Training data, the trained model, and evaluation are all local files; the analysis code cannot even name a network primitive (enforced by an automated source audit).
 - `npx @reportforge/playwright-pdf export-feedback`: merges your locally-collected feedback (tokenized + redacted) into one CSV for review or moving between machines. Local file only; there is no upload.
@@ -66,6 +67,7 @@ Three templates, one reporter. Every PDF is fully offline: fonts, charts, and sc
 - **Executive report brief band**: leads with a plain-language brief (trend + root causes) and one hero pass-rate number instead of a flat KPI grid
 - **Data protection**: AES-256 password-protected PDFs (no external tools) and opt-in redaction of credentials/PII in report content and live streams
 - **Hybrid licensing**: one short key unlocks it; reports keep rendering offline via a locally cached license between refreshes
+- **Python support**: the same reports for pytest-playwright via the `reportforge-playwright-pdf` PyPI package; one subscription key covers both ecosystems (live runs and step trees are Node.js-only today)
 - **Update notice**: when a newer reporter version is published, each run ends with one info line naming it and the update command; no extra network calls
 
 ---
@@ -156,6 +158,31 @@ reporter: [['@reportforge/playwright-pdf', {
 
 ---
 
+## Python
+
+The same reports for [pytest-playwright](https://playwright.dev/python/) runs, from the `reportforge-playwright-pdf` PyPI package. One subscription key covers Node.js and Python, and both count against the same machine allowance.
+
+```bash
+pip install reportforge-playwright-pdf
+python -m playwright install chromium
+
+export RF_LICENSE_KEY=RFSU-XXXX-XXXX-XXXX-XXXX
+pytest --pdf
+```
+
+Project defaults go in `pyproject.toml` with the same camelCase option names as this reporter:
+
+```toml
+[tool.reportforge]
+enabled = true
+template = "detailed"
+outputFile = "reports/{date}-{branch}-report.pdf"
+```
+
+The plugin reuses the Node runtime and Chromium that Playwright for Python already ships, so there is nothing else to install. pytest-xdist and pytest-rerunfailures are supported; failure screenshots from `--screenshot only-on-failure` are embedded. Live runs and step trees are Node.js-only today. Full guide: [reportforge.org/docs/python](https://reportforge.org/docs/python).
+
+---
+
 ## Pricing
 
 | Plan | INR | USD | Includes |
@@ -213,7 +240,7 @@ All options are the second element of the reporter tuple.
 | `slowTestThreshold` | `number` | `10` | Minimum timed-test count before `SLOW` badges appear in the suite breakdown: below this, every test is trivially the "slowest" so badges stay hidden. On larger runs only genuine outliers (at least 2× the median test duration) are badged, so the badge stays rare. Set to `0` to drop the run-size gate (outliers still required). |
 | `requirementTagPattern` | `string` | `'^@?[A-Z][A-Z0-9]*-\\d+$'` | Regex deciding which tags count as requirement IDs in the Requirements Traceability section (`detailed` template). Matching tags (ticket shapes like `@ODP-5328`, `REQ-001`) get the traceability matrix; everything else (`@regression`, `@sanity`) collapses into a compact tag summary instead of repeating identical rows. Set to `''` to disable the split and list every tag in the matrix. |
 | `templatePath` | `string \| string[]` | n/a | Path to a custom Handlebars (`.hbs`) template file. Takes precedence over `template`. Pass an array to generate one PDF per custom template. See the Custom Templates docs. |
-| `sections` | `object` | per-template | Override which report sections appear, on top of the chosen template's defaults. Flat keys are the baseline for every chosen template; per-template keys (`minimal`\|`detailed`\|`executive`) override per template. Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`, `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`, `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`. Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`, `stackTraces`. See the Report Sections docs. |
+| `sections` | `object` | per-template | Override which report sections appear, on top of the chosen template's defaults. Flat keys are the baseline for every chosen template; per-template keys (`minimal`\|`detailed`\|`executive`) override per template. 20 keys total. Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`, `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`, `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`, `runDiff`. Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`, `stackTraces`. `runDiff` (block toggle, on by default in all three templates) shows new failures, fixed tests, and still-failing tests compared with the previous run on the same branch. See the Report Sections docs. |
 <!-- AUTOGEN:options-table END -->
 
 Full reference: [reportforge.org/docs/configuration](https://reportforge.org/docs/configuration).
@@ -269,7 +296,9 @@ reporter: [
 
 The merge step can run against a dummy test file with zero tests: `shardResults` takes precedence over live results.
 
-> **Note:** Timed-out tests are counted as failures in shard mode (Playwright JSON stats do not distinguish `timedOut` from `failed`).
+Timed-out tests keep their own count in shard mode: the aggregate JSON stats fold them into failures, but the per-test result status carries `timedOut` and the report recovers it for the KPI cards and charts.
+
+The merger also honors two optional fields in the JSON report's `config` block when the emitting run provides them: `workers` (shown as the worker count in the environment panel, defaults to 1) and `metadata.playwrightVersion` (shown as the Playwright version when the merge runs where `@playwright/test` is not installed).
 
 ### Notifications
 
@@ -316,7 +345,7 @@ The `on` trigger controls when the message fires:
 
 **PDF attachment** (`attachPdf: true`) is available on `email` and `discord`: Slack and Teams webhooks cannot carry file uploads. On Discord the PDF is uploaded with the message; if the upload fails or the PDF exceeds Discord's file-size cap, the summary still posts without the attachment. With multiple templates, the first PDF is attached.
 
-The summary includes pass rate, test counts, duration, and the report filename. Notifications require a valid license and fire after PDF generation (or after a PDF failure; you still get the ping).
+The summary includes pass rate, test counts, duration, and the report filename. When a previous run on the same branch exists, the message also carries a run-over-run diff line: new failures, fixed tests, and tests still failing. Notifications require a valid license and fire after PDF generation (or after a PDF failure; you still get the ping).
 
 ### Data Protection
 
@@ -364,6 +393,8 @@ Full details at [reportforge.org/docs/advanced/security](https://reportforge.org
 
 After each run the reporter appends a summary entry to a local JSON file and renders a pass-rate sparkline + verdict row in the `detailed` template.
 
+**Since Last Run**: every report also gets a section (`runDiff`, on by default in all three templates) comparing the current run against the previous run on the same branch: new failures, fixed tests, and tests still failing, with the same summary line carried into Slack, Teams, Discord, and email notifications. The first run after upgrading has no comparable prior run to diff against, so the section starts appearing from the second run onward. It reads only the local history file, so test names never leave your machine; see the ephemeral-CI note below for keeping that file around between runs. Like the flakiness table, it rides history tracking (`showTrend`, on by default), and the notification line follows history availability rather than the `runDiff` section toggle.
+
 **Local dev (zero config)**: history is written automatically to `~/.reportforge/{projectKey}/history.json`. The sparkline appears once two or more runs have been recorded.
 
 **CI with ephemeral runners (recommended)**: enable the server-side trend store; the local file is wiped with the workspace, leaving the chart stuck at one data point:
@@ -375,7 +406,7 @@ reporter: [['@reportforge/playwright-pdf', {
 }]]
 ```
 
-One small authenticated request per run, carrying aggregate numbers only (pass rate, counts, duration, verdict; no test titles, no error text, and the branch name never travels in plaintext). The server keeps roughly the last 100 runs per project + branch, expiring after 180 days, and returns them for the chart; any failure falls back to the local file. The flakiness table stays local-only by design (it needs test titles, which never leave your machine). Bitbucket Pipelines users especially: Bitbucket caches are immutable once written, so `remoteHistory` is the practical path there.
+One small authenticated request per run, carrying aggregate numbers only (pass rate, counts, duration, verdict; no test titles, no error text, and the branch name never travels in plaintext). The server keeps roughly the last 100 runs per project + branch, expiring after 180 days, and returns them for the chart; any failure falls back to the local file. This feeds the trend chart only: the flakiness table and the Since Last Run diff both stay local-only by design (they need test titles, which never leave your machine); to keep either alive on ephemeral runners, use the CI caching alternative below to persist `historyFile` instead. Bitbucket Pipelines users especially: Bitbucket caches are immutable once written, so `remoteHistory` is the practical path for the trend chart there.
 
 **CI caching alternative** (keeps even aggregate numbers off the server): set `historyFile` to a project-relative path and cache it between runs:
 
@@ -673,6 +704,7 @@ ReportForge ships a **hybrid offline-first** model:
 3. Every subsequent run is **fully offline**: the cached license is validated on-device. No network call.
 4. The reporter refreshes the cache automatically in the background before it expires.
 5. Each subscription allows up to **25 active machines**. Machines that haven't run in 30 days free up automatically.
+6. The key is **language-neutral**: the same subscription activates the Node.js reporter and the Python plugin, and a machine running both uses one slot.
 
 Cancel the subscription and the reporter keeps working until the end of the current billing period, then stops generating PDFs until you restart. **A license issue never aborts your test run**: the reporter logs a warning and skips PDF generation; your Playwright tests still pass.
 
@@ -733,6 +765,7 @@ Full guide: [reportforge.org/docs/troubleshooting](https://reportforge.org/docs/
 Full documentation at [reportforge.org/docs](https://reportforge.org/docs):
 
 - [Quick start](https://reportforge.org/docs/quickstart): install, configure, activate
+- [Python](https://reportforge.org/docs/python): the pytest-playwright plugin, same license key
 - [Chrome setup](https://reportforge.org/docs/running-tests#chrome-setup): Windows, Linux, macOS
 - [CI/CD integration](https://reportforge.org/docs/ci-cd): GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps
 - [Configuration reference](https://reportforge.org/docs/configuration): all options

package/dist/cli/index.js

@@ -311,6 +311,24 @@ function buildDemoCharts(passed, failed, skipped, flaky, total) {
     ]
   };
 }
+function buildDemoRunDiff() {
+  return {
+    newFailures: [
+      { id: "auth-5", title: "should block brute-force attempts after 5 tries" },
+      { id: "cat-7", title: "should lazy-load images on scroll" }
+    ],
+    stillFailing: [
+      { id: "co-3", title: "should reject expired promo code" }
+    ],
+    fixed: [
+      { id: "co-5", title: "should complete Stripe checkout" }
+    ],
+    noLongerRun: [],
+    baselineRunId: "demo-1d",
+    baselineTimestamp: DEMO_BASE_TS - 864e5,
+    baselineTruncated: false
+  };
+}
 function buildDemoReportData(template = "detailed") {
   const projects = [
     makeProject("chromium", [
@@ -362,7 +380,8 @@ function buildDemoReportData(template = "detailed") {
       projectCount: 2,
       workerCount: 4
     },
-    charts
+    charts,
+    runDiff: buildDemoRunDiff()
   };
 }
 var DEMO_BASE_TS, DEMO_LICENSE_INFO, DEMO_AUTH_TESTS, DEMO_CHECKOUT_TESTS, DEMO_CATALOG_TESTS;
@@ -6498,6 +6517,7 @@ var init_sections = __esm({
       "slowTests",
       "defectLog",
       "briefBand",
+      "runDiff",
       // display modifiers
       "passRate",
       "fullEnvironment",
@@ -6521,6 +6541,7 @@ var init_sections = __esm({
         slowTests: false,
         defectLog: false,
         briefBand: false,
+        runDiff: true,
         passRate: true,
         fullEnvironment: false,
         retries: true,
@@ -6542,6 +6563,7 @@ var init_sections = __esm({
         slowTests: true,
         defectLog: true,
         briefBand: false,
+        runDiff: true,
         passRate: true,
         fullEnvironment: true,
         retries: true,
@@ -6568,6 +6590,7 @@ var init_sections = __esm({
         slowTests: true,
         defectLog: false,
         briefBand: true,
+        runDiff: true,
         passRate: true,
         fullEnvironment: false,
         retries: false,
@@ -6929,13 +6952,25 @@ var init_engine = __esm({
 });
 
 // src/screenshots/ScreenshotEmbedder.ts
-var import_fs2, import_sharp, ScreenshotEmbedder;
+function loadSharp() {
+  if (sharpModule === void 0) {
+    try {
+      sharpModule = require("sharp");
+    } catch {
+      sharpModule = null;
+      logger.warn(
+        "sharp is not available \u2014 screenshots are embedded at original size. Reports with many screenshots may exceed maxFileSizeMb more often."
+      );
+    }
+  }
+  return sharpModule;
+}
+var import_fs2, sharpModule, ScreenshotEmbedder;
 var init_ScreenshotEmbedder = __esm({
   "src/screenshots/ScreenshotEmbedder.ts"() {
     "use strict";
     init_cjs_shims();
     import_fs2 = __toESM(require("fs"));
-    import_sharp = __toESM(require("sharp"));
     init_logger();
     ScreenshotEmbedder = class {
       async embedAll(failures, opts) {
@@ -6972,7 +7007,11 @@ var init_ScreenshotEmbedder = __esm({
         if (this.looksLikeSvg(buf)) {
           return { buffer: buf, mime: "image/svg+xml" };
         }
-        const img = (0, import_sharp.default)(buf, { failOn: "none" });
+        const sharp = loadSharp();
+        if (!sharp) {
+          return { buffer: buf, mime: this.detectMimeType(buf) };
+        }
+        const img = sharp(buf, { failOn: "none" });
         const meta = await img.metadata();
         const needsResize = (meta.width ?? 0) > opts.maxWidth;
         let pipeline = img.rotate();

package/dist/index.d.mts

@@ -1,11 +1,11 @@
 import { Reporter, FullConfig, Suite, TestCase, TestResult, TestStep, FullResult } from '@playwright/test/reporter';
 
 /**
- * Canonical section catalog. 14 block toggles (section present/absent) followed
+ * Canonical section catalog. 15 block toggles (section present/absent) followed
  * by 5 display modifiers (tweak a section that is on). Single source of truth —
  * the Zod schema in src/config/schema.ts builds its flag shape from this array.
  */
-declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
+declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "runDiff", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
 type SectionKey = (typeof SECTION_KEYS)[number];
 /** A partial map of section flags — used both as the flat baseline and per-template. */
 type SectionFlags = Partial<Record<SectionKey, boolean>>;
@@ -406,12 +406,18 @@ interface ReporterOptions {
      * every chosen template; per-template keys (`minimal` / `detailed` /
      * `executive`) override the baseline for that template only.
      *
+     * 20 keys total: 15 block toggles, 5 display modifiers.
+     *
      * Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`,
      * `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`,
-     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`.
+     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`,
+     * `runDiff`.
      * Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`,
      * `stackTraces`.
      *
+     * `runDiff` shows new failures, fixed tests, and still-failing tests against
+     * the previous run on the same branch; on by default in all three templates.
+     *
      * `trend` renders only when `charts` is also on and history data exists (`showTrend` enabled). Sections gated on data
      * (`failureAnalysis`, `requirementsMatrix`, `slowTests`, `defectLog`) appear
      * only when matching data exists — this option never changes data collection.
@@ -426,43 +432,6 @@ interface ReporterOptions {
     sections?: SectionsOption;
 }
 
-/**
- * The resolved license for the current reporter run.
- *
- * The mere existence of a LicenseInfo means the subscription is active —
- * "no license" is represented by `LicenseClient.resolve()` returning null,
- * not by a sentinel plan or `valid: false` flag.
- *
- * `source` surfaces how the license was obtained so the reporter can log
- * actionable diagnostics:
- *   - 'jwt-online'  → freshly activated/refreshed against the server
- *   - 'jwt-cache'   → served from ~/.reportforge/license.json (offline)
- */
-interface LicenseInfo {
-    plan: LicensePlan;
-    source: 'jwt-online' | 'jwt-cache' | 'demo';
-    expiry: Date;
-    key: string;
-    /** Raw Ed25519-signed JWT from the server. Absent only in demo mode. */
-    jwt?: string;
-    machinesUsed?: number;
-    machineLimit?: number;
-    /**
-     * Entitlement flags carried on the signed JWT (`features` claim). Surfaces
-     * server-gated capabilities (e.g. `'live'`) to the reporter without a second
-     * network trip. Undefined for caches written by reporter versions before this
-     * field was persisted — treat absence as "no extra features".
-     */
-    features?: string[];
-    /**
-     * Latest published npm version of the reporter, as last reported by the
-     * license server (activate/refresh piggyback). Absent when the server
-     * could not reach the registry or the cache predates this field. Used
-     * only for the non-blocking run-end update notice.
-     */
-    latestVersion?: string;
-}
-
 /**
  * PdfReporter — Playwright custom reporter that generates professional PDF reports.
  *
@@ -520,9 +489,6 @@ declare class PdfReporter implements Reporter {
     onExit(): Promise<void>;
     onEnd(result: FullResult): Promise<void>;
     private _collectData;
-    private _appendTrend;
-    private _populateHistoryCharts;
-    private _buildReportData;
     printsToStdio(): boolean;
     /**
      * Memoized license resolution shared by the live stream (kicked early in
@@ -560,8 +526,43 @@ declare class PdfReporter implements Reporter {
      * posts one message, not N. The banner still prints from every shard's own log.
      */
     private announceLive;
-    private resolveProjectName;
-    private openPdf;
+}
+
+/**
+ * The resolved license for the current reporter run.
+ *
+ * The mere existence of a LicenseInfo means the subscription is active —
+ * "no license" is represented by `LicenseClient.resolve()` returning null,
+ * not by a sentinel plan or `valid: false` flag.
+ *
+ * `source` surfaces how the license was obtained so the reporter can log
+ * actionable diagnostics:
+ *   - 'jwt-online'  → freshly activated/refreshed against the server
+ *   - 'jwt-cache'   → served from ~/.reportforge/license.json (offline)
+ */
+interface LicenseInfo {
+    plan: LicensePlan;
+    source: 'jwt-online' | 'jwt-cache' | 'demo';
+    expiry: Date;
+    key: string;
+    /** Raw Ed25519-signed JWT from the server. Absent only in demo mode. */
+    jwt?: string;
+    machinesUsed?: number;
+    machineLimit?: number;
+    /**
+     * Entitlement flags carried on the signed JWT (`features` claim). Surfaces
+     * server-gated capabilities (e.g. `'live'`) to the reporter without a second
+     * network trip. Undefined for caches written by reporter versions before this
+     * field was persisted — treat absence as "no extra features".
+     */
+    features?: string[];
+    /**
+     * Latest published npm version of the reporter, as last reported by the
+     * license server (activate/refresh piggyback). Absent when the server
+     * could not reach the registry or the cache predates this field. Used
+     * only for the non-blocking run-end update notice.
+     */
+    latestVersion?: string;
 }
 
 /**

package/dist/index.d.ts

@@ -1,11 +1,11 @@
 import { Reporter, FullConfig, Suite, TestCase, TestResult, TestStep, FullResult } from '@playwright/test/reporter';
 
 /**
- * Canonical section catalog. 14 block toggles (section present/absent) followed
+ * Canonical section catalog. 15 block toggles (section present/absent) followed
  * by 5 display modifiers (tweak a section that is on). Single source of truth —
  * the Zod schema in src/config/schema.ts builds its flag shape from this array.
  */
-declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
+declare const SECTION_KEYS: readonly ["coverPage", "analysisOneliner", "releaseGate", "summary", "charts", "trend", "requirementsMatrix", "ciEnvironment", "suiteBreakdown", "failureDeepDive", "failureAnalysis", "slowTests", "defectLog", "briefBand", "runDiff", "passRate", "fullEnvironment", "retries", "fullFailures", "stackTraces"];
 type SectionKey = (typeof SECTION_KEYS)[number];
 /** A partial map of section flags — used both as the flat baseline and per-template. */
 type SectionFlags = Partial<Record<SectionKey, boolean>>;
@@ -406,12 +406,18 @@ interface ReporterOptions {
      * every chosen template; per-template keys (`minimal` / `detailed` /
      * `executive`) override the baseline for that template only.
      *
+     * 20 keys total: 15 block toggles, 5 display modifiers.
+     *
      * Block toggles: `coverPage`, `analysisOneliner`, `releaseGate`, `summary`,
      * `charts`, `trend`, `requirementsMatrix`, `ciEnvironment`, `suiteBreakdown`,
-     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`.
+     * `failureDeepDive`, `failureAnalysis`, `slowTests`, `defectLog`, `briefBand`,
+     * `runDiff`.
      * Display modifiers: `passRate`, `fullEnvironment`, `retries`, `fullFailures`,
      * `stackTraces`.
      *
+     * `runDiff` shows new failures, fixed tests, and still-failing tests against
+     * the previous run on the same branch; on by default in all three templates.
+     *
      * `trend` renders only when `charts` is also on and history data exists (`showTrend` enabled). Sections gated on data
      * (`failureAnalysis`, `requirementsMatrix`, `slowTests`, `defectLog`) appear
      * only when matching data exists — this option never changes data collection.
@@ -426,43 +432,6 @@ interface ReporterOptions {
     sections?: SectionsOption;
 }
 
-/**
- * The resolved license for the current reporter run.
- *
- * The mere existence of a LicenseInfo means the subscription is active —
- * "no license" is represented by `LicenseClient.resolve()` returning null,
- * not by a sentinel plan or `valid: false` flag.
- *
- * `source` surfaces how the license was obtained so the reporter can log
- * actionable diagnostics:
- *   - 'jwt-online'  → freshly activated/refreshed against the server
- *   - 'jwt-cache'   → served from ~/.reportforge/license.json (offline)
- */
-interface LicenseInfo {
-    plan: LicensePlan;
-    source: 'jwt-online' | 'jwt-cache' | 'demo';
-    expiry: Date;
-    key: string;
-    /** Raw Ed25519-signed JWT from the server. Absent only in demo mode. */
-    jwt?: string;
-    machinesUsed?: number;
-    machineLimit?: number;
-    /**
-     * Entitlement flags carried on the signed JWT (`features` claim). Surfaces
-     * server-gated capabilities (e.g. `'live'`) to the reporter without a second
-     * network trip. Undefined for caches written by reporter versions before this
-     * field was persisted — treat absence as "no extra features".
-     */
-    features?: string[];
-    /**
-     * Latest published npm version of the reporter, as last reported by the
-     * license server (activate/refresh piggyback). Absent when the server
-     * could not reach the registry or the cache predates this field. Used
-     * only for the non-blocking run-end update notice.
-     */
-    latestVersion?: string;
-}
-
 /**
  * PdfReporter — Playwright custom reporter that generates professional PDF reports.
  *
@@ -520,9 +489,6 @@ declare class PdfReporter implements Reporter {
     onExit(): Promise<void>;
     onEnd(result: FullResult): Promise<void>;
     private _collectData;
-    private _appendTrend;
-    private _populateHistoryCharts;
-    private _buildReportData;
     printsToStdio(): boolean;
     /**
      * Memoized license resolution shared by the live stream (kicked early in
@@ -560,8 +526,43 @@ declare class PdfReporter implements Reporter {
      * posts one message, not N. The banner still prints from every shard's own log.
      */
     private announceLive;
-    private resolveProjectName;
-    private openPdf;
+}
+
+/**
+ * The resolved license for the current reporter run.
+ *
+ * The mere existence of a LicenseInfo means the subscription is active —
+ * "no license" is represented by `LicenseClient.resolve()` returning null,
+ * not by a sentinel plan or `valid: false` flag.
+ *
+ * `source` surfaces how the license was obtained so the reporter can log
+ * actionable diagnostics:
+ *   - 'jwt-online'  → freshly activated/refreshed against the server
+ *   - 'jwt-cache'   → served from ~/.reportforge/license.json (offline)
+ */
+interface LicenseInfo {
+    plan: LicensePlan;
+    source: 'jwt-online' | 'jwt-cache' | 'demo';
+    expiry: Date;
+    key: string;
+    /** Raw Ed25519-signed JWT from the server. Absent only in demo mode. */
+    jwt?: string;
+    machinesUsed?: number;
+    machineLimit?: number;
+    /**
+     * Entitlement flags carried on the signed JWT (`features` claim). Surfaces
+     * server-gated capabilities (e.g. `'live'`) to the reporter without a second
+     * network trip. Undefined for caches written by reporter versions before this
+     * field was persisted — treat absence as "no extra features".
+     */
+    features?: string[];
+    /**
+     * Latest published npm version of the reporter, as last reported by the
+     * license server (activate/refresh piggyback). Absent when the server
+     * could not reach the registry or the cache predates this field. Used
+     * only for the non-blocking run-end update notice.
+     */
+    latestVersion?: string;
 }
 
 /**