mjolnir-qa 2.0.0 → 2.1.0

package/README.md

@@ -1,11 +1,11 @@
 <div align="center">
 
-<img src="assets/readme/hero.svg" alt="Mjölnir. Tests tell you what passed. Mjölnir tells you what you can trust." width="100%" />
+<img src="assets/readme/hero.svg" alt="Mjölnir. Prevents release-blocking false-green." width="100%" />
 
 <br />
 
-Mjölnir finds tests that cannot fail and pipelines that cannot go red,<br />
-then scores how far the result can be trusted, with the evidence for every point.
+Mjölnir quantifies how much you can trust your CI — and blocks releases
+when verification isn't earning its keep.
 
 <br />
 
@@ -39,8 +39,9 @@ it; `npm run docs:translations` reports how far.
 
 ## A green check is a claim, not a proof
 
-A green check means the pipeline did not fail. It does not mean the tests
-ran, or that they could have failed. Every one of these ships green:
+A green check means the pipeline did not fail. It does not mean
+the tests ran, or that they could have failed. Every one of these
+ships green — and every one of them makes your release untrustworthy:
 
 - a committed `.only` that ran 3 tests instead of 900
 - `continue-on-error: true` on the job that was supposed to gate
@@ -50,8 +51,10 @@ ran, or that they could have failed. Every one of these ships green:
 - a report the workflow uploads but never generated
 - a hard sleep holding a race condition together
 
-None of them turns the pipeline red, and each one looks deliberate in
-review. That is why they survive. Here is Mjölnir reading a real one:
+None of them turns the pipeline red, and each one looks deliberate
+in review. That is why they survive. **They are the reason releases ship bugs.**
+
+Here is Mjölnir reading a real one:
 
 <p align="center">
   <img src="assets/readme/scan.svg" alt="The demo repository's CI workflow, read line by line. Mjölnir flags each finding at the line it reported, with its rule, what is wrong, its evidence level and its measured false-positive rate." width="800" />
@@ -98,7 +101,7 @@ A real scan of [`examples/demo-repo`](examples/demo-repo), a small
 Playwright suite with a CI workflow. This is where its points went:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir's deduction breakdown: WORTHINESS 75/100 NEEDS WORK, the score by category, the per-severity deduction box, and a FIX THIS FIRST list" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir's deduction breakdown: WORTHINESS 80/100 WORTHY, the score by category, the per-severity deduction box, and a FIX THIS FIRST list" width="520" />
 </p>
 
 <sub>Generated by `npm run docs:hero` from a real scan and drift-locked in
@@ -147,6 +150,17 @@ FP risk:     low (author estimate)
 Languages:   yaml
 Frameworks:  github-actions, azure-pipelines
 
+COPY-READY REVIEW COMMENT
+  Advisory finding — this does not block merging: Job `security-scan` runs a
+  verification gate under `continue-on-error: true`.
+  Why it weakens verification: This job can fail every day and CI will still
+  show green. The checkmark on this workflow cannot be trusted.
+  Confidence: high, evidence E2, tier quarantine; measured FP 11% (19 verdicts).
+  Suggested fix: Remove continue-on-error, or scope it to individual
+  non-blocking steps only.
+  Verify with: mjolnir --scope changed, then mjolnir explain QA-CI-001 if the
+  finding still appears.
+
 WHAT WAS FOUND (real detector output, not a mockup)
   Job `security-scan` runs a verification gate under `continue-on-error: true`.
 
@@ -188,65 +202,78 @@ That is the unit of value: one place where CI reports a pass it did not earn.
 npx mjolnir-qa@latest
 ```
 
-It scans the current directory and prints the Trust Report: what it found,
-how far you can trust it, why, and what to do next. It exits `0` when
-nothing at or above the gate was found.
+Three steps to trust your release pipeline:
 
-In CI, scan only what the branch introduced, so a legacy suite does not
-drown your first pull request:
+1. **Scan** — `npx mjolnir-qa@latest` — scans the current directory, prints the Trust Report, exits `1` if findings at the gate
+2. **Block in CI** — `npx mjolnir-qa@latest --scope changed` — scans only changed lines, blocks PRs with error findings
+3. **Fix and re-verify** — `mjolnir fix` applies safe auto-fixes, then re-scans to prove each one landed
+
+Install the advisory PR workflow first, so existing trust debt cannot break
+CI on day one:
 
 ```bash
-npx mjolnir-qa@latest --scope changed
+mjolnir ci install
+```
+
+After reviewing the findings or baselining existing debt, opt into blocking:
+
+```bash
+mjolnir ci install --gate error
 ```
 
-`mjolnir ci install` writes that as a GitHub Actions workflow, using the
-[action](https://github.com/Sergey-Bar/Mjolnir#readme) pinned to the `v1`
-major tag (or plain `npx` with `--no-action`). It stays advisory until you
-decide it should block.
-
-| Command                             | What it does                                     |
-| ----------------------------------- | ------------------------------------------------ |
-| `mjolnir`                           | Trust Report: verdict, confidence, next action   |
-| `mjolnir --scope changed`           | Only what your branch introduced (the CI form)   |
-| `mjolnir ci install`                | Generate the advisory PR workflow (action-based) |
-| `mjolnir explain QA-CI-001`         | What, why and fix, plus the measured FP rate     |
-| `mjolnir why src/a.spec.ts:42`      | Why this exact line was flagged. Never gates.    |
-| `mjolnir forensics ./test-results/` | Runtime evidence from a real run                 |
-| `mjolnir trust-report`              | Self-contained Trust Artifact (md + json)        |
-| `mjolnir handoff`                   | Remediation plan for a coding agent              |
-| `mjolnir --json` / `--format sarif` | Machine-readable output, GitHub Code Scanning    |
-| `mjolnir --format codequality`      | GitLab Code Quality report (MR widget artifact)  |
-| `mjolnir --strict`                  | Also run quarantine-tier rules (higher FP risk)  |
+| Command                             | What it does                                    |
+| ----------------------------------- | ----------------------------------------------- |
+| `mjolnir`                           | Trust Report: verdict, confidence, next action  |
+| `mjolnir --scope changed`           | Only what your branch introduced (CI form)      |
+| `mjolnir --blocking error`          | Exit 1 on error findings — gate releases        |
+| `mjolnir ci install`                | Write the advisory PR workflow (default)        |
+| `mjolnir ci install --gate error`   | Opt into the blocking PR workflow               |
+| `mjolnir business-case`             | ROI estimate: projected savings per finding     |
+| `mjolnir explain QA-CI-001`         | What, why and fix, plus the measured FP rate    |
+| `mjolnir why src/a.spec.ts:42`      | Why this exact line was flagged. Never gates.   |
+| `mjolnir forensics ./test-results/` | Runtime evidence from a real run                |
+| `mjolnir trust-report`              | Self-contained Trust Artifact (md + json)       |
+| `mjolnir handoff`                   | Remediation plan for a coding agent             |
+| `mjolnir --json` / `--format sarif` | Machine-readable output, GitHub Code Scanning   |
+| `mjolnir --format codequality`      | GitLab Code Quality report (MR widget artifact) |
+| `mjolnir --strict`                  | Also run quarantine-tier rules (higher FP risk) |
 
 <details>
 <summary><strong>Every other command</strong> — flake triage, reporting, governance</summary>
 
 <br />
 
-| Command                             | What it does                                         |
-| ----------------------------------- | ---------------------------------------------------- |
-| `mjolnir --classic`                 | The pre-Trust-Report score banner render             |
-| `mjolnir explain verdict`           | Why the saved scan's verdict is what it is           |
-| `mjolnir triage ./test-results/`    | Guided triage. Every row ends in a next action.      |
-| `mjolnir pw-report ./test-results/` | Playwright run summary: retries, flakes, slowest     |
-| `mjolnir doctor:playwright`         | Playwright-only deep scan plus Selector Health Score |
-| `mjolnir fix --dry-run` / `fix`     | Safe auto-fixes, each re-scanned to prove it landed  |
-| `mjolnir baseline` / `diff`         | Snapshot findings, then report only new or worse     |
-| `mjolnir impact --since <ref>`      | What a commit introduced and resolved                |
-| `mjolnir summary`                   | CI annotations and a step summary from a report      |
-| `mjolnir pr-comment`                | A scoped PR comment, as Markdown                     |
-| `mjolnir debt`                      | Test-debt register with a cost model                 |
-| `mjolnir handover`                  | Onboarding map of the suite for a new QA engineer    |
-| `mjolnir init`                      | Detect frameworks, print a setup checklist           |
-| `mjolnir suppressions`              | List suppressed findings, for governance             |
-| `mjolnir rules --unmeasured`        | The rules running on assumption, not measurement     |
-| `mjolnir rules --md`                | Full rule catalog (JSON or Markdown)                 |
-| `mjolnir doctor`                    | Self-audit of Mjölnir's own rule base                |
-| `mjolnir create-rule <ID>`          | Scaffold a new rule and its fixtures                 |
-| `mjolnir stats`                     | Local all-time counters of fixes seen                |
-| `mjolnir badge`                     | shields.io endpoint JSON and snippet                 |
-| `mjolnir --cache`                   | Incremental re-scans via a local verdict cache       |
-| `mjolnir --format mermaid`          | Test-architecture diagram for a PR comment           |
+| Command                             | What it does                                          |
+| ----------------------------------- | ----------------------------------------------------- |
+| `mjolnir --classic`                 | The pre-Trust-Report score banner render              |
+| `mjolnir explain verdict`           | Why the saved scan's verdict is what it is            |
+| `mjolnir triage ./test-results/`    | Guided triage. Every row ends in a next action.       |
+| `mjolnir pw-report ./test-results/` | Playwright run summary: retries, flakes, slowest      |
+| `mjolnir doctor:playwright`         | Playwright-only deep scan plus Selector Health Score  |
+| `mjolnir fix --dry-run` / `fix`     | Safe auto-fixes, each re-scanned to prove it landed   |
+| `mjolnir baseline` / `diff`         | Snapshot findings, then report only new or worse      |
+| `mjolnir impact --since <ref>`      | What a commit introduced and resolved                 |
+| `mjolnir summary`                   | CI annotations and a step summary from a report       |
+| `mjolnir pr-comment`                | A scoped PR comment, as Markdown                      |
+| `mjolnir debt`                      | Test-debt register with a cost model                  |
+| `mjolnir handover`                  | Onboarding map of the suite for a new QA engineer     |
+| `mjolnir init`                      | Detect frameworks, print a setup checklist            |
+| `mjolnir suppressions`              | List suppressed findings, for governance              |
+| `mjolnir ci-integrity`              | Verify blocking CI scans and suppression policy       |
+| `mjolnir framework-maturity`        | Inspect bounded maturity with human calibration       |
+| `mjolnir suppression-gate`          | Enforce expiry, allowlist, and mass-suppression rules |
+| `mjolnir cross-file`                | Analyze duplicate, shared, and circular test signals  |
+| `mjolnir contract-verify`           | Verify a persisted machine contract artifact          |
+| `mjolnir trust-trend`               | Persist and compare trust snapshots over time         |
+| `mjolnir evidence-graph`            | Build or query the verification evidence graph        |
+| `mjolnir rules --unmeasured`        | The rules running on assumption, not measurement      |
+| `mjolnir rules --md`                | Full rule catalog (JSON or Markdown)                  |
+| `mjolnir doctor`                    | Self-audit of Mjölnir's own rule base                 |
+| `mjolnir create-rule <ID>`          | Scaffold a new rule and its fixtures                  |
+| `mjolnir stats`                     | Local all-time counters of fixes seen                 |
+| `mjolnir badge`                     | shields.io endpoint JSON and snippet                  |
+| `mjolnir --cache`                   | Incremental re-scans via a local verdict cache        |
+| `mjolnir --format mermaid`          | Test-architecture diagram for a PR comment            |
 
 `mjolnir help <command>` prints usage, examples and the next step for any
 of them.
@@ -360,8 +387,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 This measures **resilience, not correctness**.
@@ -543,24 +570,33 @@ propagate, always-success steps, reports consumed but never generated, and
 gates skipped on the events that should block. Each finding names the job,
 the step and the line, and carries its own evidence level.
 
-Generate the PR workflow, advisory by default:
+Generate an advisory PR workflow first. It reports findings without blocking
+and is pinned to this version, so adopting it cannot change gate semantics:
 
 ```bash
 mjolnir ci install
 ```
 
-Or add the Marketplace action to a workflow you already have:
+After reviewing existing debt, opt into an enforcing gate:
+
+```bash
+mjolnir ci install --gate error
+```
+
+In your existing workflow, pin the action and explicitly opt into an error gate:
 
 ```yaml
-- uses: Sergey-Bar/Mjolnir@v1
+- uses: Sergey-Bar/Mjolnir@4a588bc62d517bc85fc44c0eae64c6587d3bf70b0
   with:
     scope: changed
     fail-on: error
 ```
 
-Pin `@v1` to follow the major line, or an exact tag (`@v0.5.32`) for a
-reproducible gate. [docs/DISTRIBUTION-KIT.md](docs/DISTRIBUTION-KIT.md)
-covers the Marketplace, Smithery and the MCP registries.
+The `--blocking error` flag does the same in any CI pipeline:
+
+```bash
+npx mjolnir-qa@latest --scope changed --blocking error
+```
 
 To put findings in GitHub Code Scanning, upload SARIF (requires
 `security-events: write` at workflow or job scope):
@@ -610,11 +646,11 @@ SCAN → EVIDENCE → HANDOFF → AGENT → RE-SCAN → PROOF
 **AI writes the fix. Mjölnir verifies it.** The proof comes from the
 re-scan, never from the agent's own report of success.
 
-| Command           | What the agent gets                                                                                                                                           |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `mjolnir mcp`     | An [MCP](https://modelcontextprotocol.io) server over stdio. `scan`, `explain` and `diff` become callable tools.                                              |
-| `mjolnir handoff` | A saved `--json` report becomes a deterministic Markdown plan: what was detected, the evidence boundary per finding, what must **not** change, how to verify. |
-| `mjolnir install` | Writes into the agent surfaces your repo already has (`.claude/`, `.cursor/`, `.kilo/`, `AGENTS.md`) so the agent re-scans before it claims it is done.       |
+| Command           | What the agent gets                                                                                                                                                    |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `mjolnir mcp`     | An [MCP](https://modelcontextprotocol.io) server over stdio. `scan`, `explain`, `diff`, `verify`, `forensics`, `triage`, and `pw-report` are read-only callable tools. |
+| `mjolnir handoff` | A saved `--json` report becomes a deterministic Markdown plan: what was detected, the evidence boundary per finding, what must **not** change, how to verify.          |
+| `mjolnir install` | Writes into the agent surfaces your repo already has (`.claude/`, `.cursor/`, `.kilo/`, `AGENTS.md`) so the agent re-scans before it claims it is done.                |
 
 Add it to a client that ships its own CLI:
 
@@ -719,6 +755,7 @@ The full docs site is at <https://sergey-bar.github.io/Mjolnir/>.
 
 | Document                                               | What's in it                                      |
 | ------------------------------------------------------ | ------------------------------------------------- |
+| [docs/EXECUTIVE-ROI.md](docs/EXECUTIVE-ROI.md)         | Business case for decision-makers                 |
 | [docs/SCORING.md](docs/SCORING.md)                     | Score normalization and evidence weighting        |
 | [docs/TERMINOLOGY.md](docs/TERMINOLOGY.md)             | Canonical vocabulary: one word per concept        |
 | [docs/FP-AUDIT.md](docs/FP-AUDIT.md)                   | Measured false-positive rates and the method      |

package/README.no.md

@@ -81,7 +81,7 @@ Mjölnir leser testsuiten, CI-workflowene og, hvis du har en, rapporten fra en e
 En ekte skanning av [`examples/demo-repo`](examples/demo-repo), en liten Playwright-suite med en CI-workflow. Her er hvor poengene ble av:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Mjölnirs oversikt over trekk: WORTHINESS 75/100 NEEDS WORK, scoren per kategori, trekkboksen per alvorlighetsgrad og en FIX THIS FIRST-liste" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Mjölnirs oversikt over trekk: WORTHINESS 80/100 WORTHY, scoren per kategori, trekkboksen per alvorlighetsgrad og en FIX THIS FIRST-liste" width="520" />
 </p>
 
 <sub>Generert av `npm run docs:hero` fra en ekte skanning og låst mot avvik i CI. Den fullstendige `--verbose`-rapporten fra samme skanning er [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 Dette måler **robusthet, ikke korrekthet**. `.btn.btn-primary > div:nth-child(2)` består i dag og fortsetter å bestå til noen rører markupen. En lav score påstår aldri at testen er ødelagt, bare at den avhenger av markup ingen har lovet å beholde.

package/README.pl.md

@@ -81,7 +81,7 @@ Mjölnir czyta zestaw testów, workflow CI oraz, jeśli go masz, raport z prawdz
 Prawdziwy skan [`examples/demo-repo`](examples/demo-repo), małego zestawu Playwright z workflow CI. Oto, gdzie poszły jego punkty:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Rozbicie potrąceń Mjölnira: WORTHINESS 75/100 NEEDS WORK, wynik według kategorii, ramka potrąceń według ważności i lista FIX THIS FIRST" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Rozbicie potrąceń Mjölnira: WORTHINESS 80/100 WORTHY, wynik według kategorii, ramka potrąceń według ważności i lista FIX THIS FIRST" width="520" />
 </p>
 
 <sub>Wygenerowane przez `npm run docs:hero` z prawdziwego skanu i zabezpieczone w CI przed rozjazdem. Pełny raport `--verbose` z tego samego skanu to [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 To mierzy **odporność, a nie poprawność**. `.btn.btn-primary > div:nth-child(2)` przechodzi dziś i będzie przechodzić, dopóki ktoś nie ruszy znaczników. Niski wynik nigdy nie twierdzi, że test jest zepsuty, tylko że zależy od znaczników, których nikt nie obiecał zachować.

package/README.ru.md

@@ -81,7 +81,7 @@ Mjölnir читает набор тестов, CI-workflow и, если он е
 Реальное сканирование [`examples/demo-repo`](examples/demo-repo), небольшого набора тестов Playwright с CI-workflow. Вот куда ушли его баллы:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Разбивка вычетов Mjölnir: WORTHINESS 75/100 NEEDS WORK, оценка по категориям, блок вычетов по серьёзности и список FIX THIS FIRST" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Разбивка вычетов Mjölnir: WORTHINESS 80/100 WORTHY, оценка по категориям, блок вычетов по серьёзности и список FIX THIS FIRST" width="520" />
 </p>
 
 <sub>Сгенерировано командой `npm run docs:hero` из реального сканирования и защищено от расхождений в CI. Полный отчёт `--verbose` того же сканирования — [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 Это измеряет **устойчивость, а не корректность**. `.btn.btn-primary > div:nth-child(2)` проходит сегодня и будет проходить, пока кто-нибудь не тронет разметку. Низкая оценка никогда не утверждает, что тест сломан, — только что он зависит от разметки, сохранять которую никто не обещал.

package/README.th.md

@@ -81,7 +81,7 @@ Mjölnir อ่านชุดเทสต์ CI workflow และรายง
 การสแกนจริงของ [`examples/demo-repo`](examples/demo-repo) ซึ่งเป็นชุดเทสต์ Playwright ขนาดเล็กที่มี CI workflow คะแนนของมันหายไปตรงนี้:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="รายละเอียดการหักคะแนนของ Mjölnir: WORTHINESS 75/100 NEEDS WORK คะแนนแยกตามหมวดหมู่ กล่องการหักคะแนนตามความรุนแรง และรายการ FIX THIS FIRST" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="รายละเอียดการหักคะแนนของ Mjölnir: WORTHINESS 80/100 WORTHY คะแนนแยกตามหมวดหมู่ กล่องการหักคะแนนตามความรุนแรง และรายการ FIX THIS FIRST" width="520" />
 </p>
 
 <sub>สร้างโดย `npm run docs:hero` จากการสแกนจริง และถูกล็อกไม่ให้คลาดเคลื่อนใน CI รายงาน `--verbose` ฉบับเต็มของการสแกนเดียวกันคือ [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`)</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 สิ่งนี้วัด **ความทนทาน ไม่ใช่ความถูกต้อง** `.btn.btn-primary > div:nth-child(2)` ผ่านในวันนี้ และจะผ่านต่อไปจนกว่าจะมีคนแตะ markup คะแนนต่ำไม่เคยอ้างว่าเทสต์พัง เพียงบอกว่ามันพึ่งพา markup ที่ไม่มีใครสัญญาว่าจะคงไว้

package/README.tr.md

@@ -81,7 +81,7 @@ Mjölnir test paketini, CI workflow'larını ve varsa gerçek bir çalıştırma
 CI workflow'u olan küçük bir Playwright paketi olan [`examples/demo-repo`](examples/demo-repo) üzerinde gerçek bir tarama. Puanlarının nereye gittiği burada:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir'in kesinti dökümü: WORTHINESS 75/100 NEEDS WORK, kategoriye göre puan, önem derecesine göre kesinti kutusu ve bir FIX THIS FIRST listesi" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir'in kesinti dökümü: WORTHINESS 80/100 WORTHY, kategoriye göre puan, önem derecesine göre kesinti kutusu ve bir FIX THIS FIRST listesi" width="520" />
 </p>
 
 <sub>`npm run docs:hero` ile gerçek bir taramadan üretilir ve CI'da sapmaya karşı kilitlenir. Aynı taramanın tam `--verbose` raporu [`demo.svg`](assets/readme/demo.svg) dosyasıdır (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 Bu, **doğruluğu değil dayanıklılığı** ölçer. `.btn.btn-primary > div:nth-child(2)` bugün geçer ve biri işaretlemeye dokunana kadar geçmeye devam eder. Düşük bir puan asla testin bozuk olduğunu iddia etmez; yalnızca kimsenin korumayı vaat etmediği işaretlemeye bağlı olduğunu söyler.

package/README.uk.md

@@ -81,7 +81,7 @@ Mjölnir читає набір тестів, CI-workflow і, якщо він є,
 Реальне сканування [`examples/demo-repo`](examples/demo-repo), невеликого набору тестів Playwright із CI-workflow. Ось куди пішли його бали:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Розбивка вирахувань Mjölnir: WORTHINESS 75/100 NEEDS WORK, оцінка за категоріями, блок вирахувань за серйозністю та список FIX THIS FIRST" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Розбивка вирахувань Mjölnir: WORTHINESS 80/100 WORTHY, оцінка за категоріями, блок вирахувань за серйозністю та список FIX THIS FIRST" width="520" />
 </p>
 
 <sub>Згенеровано командою `npm run docs:hero` з реального сканування і захищено від розбіжностей у CI. Повний звіт `--verbose` того самого сканування — [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 Це вимірює **стійкість, а не коректність**. `.btn.btn-primary > div:nth-child(2)` проходить сьогодні й проходитиме, доки хтось не торкнеться розмітки. Низька оцінка ніколи не стверджує, що тест зламаний, — лише що він залежить від розмітки, яку ніхто не обіцяв зберігати.

package/README.vi.md

@@ -81,7 +81,7 @@ Mjölnir đọc bộ test, các workflow CI và, nếu bạn có, báo cáo củ
 Một lần quét thật trên [`examples/demo-repo`](examples/demo-repo), một bộ test Playwright nhỏ có workflow CI. Đây là nơi điểm của nó bị trừ:
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Bảng phân tích trừ điểm của Mjölnir: WORTHINESS 75/100 NEEDS WORK, điểm theo từng hạng mục, ô trừ điểm theo mức nghiêm trọng và danh sách FIX THIS FIRST" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Bảng phân tích trừ điểm của Mjölnir: WORTHINESS 80/100 WORTHY, điểm theo từng hạng mục, ô trừ điểm theo mức nghiêm trọng và danh sách FIX THIS FIRST" width="520" />
 </p>
 
 <sub>Được tạo bởi `npm run docs:hero` từ một lần quét thật và được khóa chống sai lệch trong CI. Báo cáo `--verbose` đầy đủ của cùng lần quét là [`demo.svg`](assets/readme/demo.svg) (`npm run docs:demo`).</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 Điều này đo **độ bền, không phải độ đúng**. `.btn.btn-primary > div:nth-child(2)` qua hôm nay và sẽ tiếp tục qua cho đến khi ai đó động vào markup. Điểm thấp không bao giờ khẳng định test bị hỏng, chỉ nói rằng nó phụ thuộc vào markup mà không ai hứa giữ nguyên.

package/README.zh.md

@@ -81,7 +81,7 @@ Mjölnir 读取测试套件、CI workflow，以及（如果有的话）一次真
 对 [`examples/demo-repo`](examples/demo-repo) 的一次真实扫描，这是一个带 CI workflow 的小型 Playwright 套件。它的分数都扣在了这里：
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir 的扣分明细：WORTHINESS 75/100 NEEDS WORK、按类别的评分、按严重级别的扣分框，以及 FIX THIS FIRST 列表" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir 的扣分明细：WORTHINESS 80/100 WORTHY、按类别的评分、按严重级别的扣分框，以及 FIX THIS FIRST 列表" width="520" />
 </p>
 
 <sub>由 `npm run docs:hero` 根据一次真实扫描生成，并在 CI 中锁定以防漂移。同一次扫描的完整 `--verbose` 报告是 [`demo.svg`](assets/readme/demo.svg)（`npm run docs:demo`）。</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 这衡量的是**韧性，而非正确性**。`.btn.btn-primary > div:nth-child(2)` 今天能通过，并会一直通过，直到有人改动标记结构。低分从不声称测试坏了，只说明它依赖于没有人承诺保留的标记结构。

package/README.zht.md

@@ -81,7 +81,7 @@ Mjölnir 讀取測試套件、CI workflow，以及（如果有的話）一次真
 對 [`examples/demo-repo`](examples/demo-repo) 的一次真實掃描，這是一個附帶 CI workflow 的小型 Playwright 套件。它的分數都扣在了這裡：
 
 <p align="center">
-  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir 的扣分明細：WORTHINESS 75/100 NEEDS WORK、依類別的評分、依嚴重程度的扣分框，以及 FIX THIS FIRST 清單" width="520" />
+  <img src="assets/readme/terminal-hero.svg" alt="Mjölnir 的扣分明細：WORTHINESS 80/100 WORTHY、依類別的評分、依嚴重程度的扣分框，以及 FIX THIS FIRST 清單" width="520" />
 </p>
 
 <sub>由 `npm run docs:hero` 根據一次真實掃描產生，並在 CI 中鎖定以防漂移。同一次掃描的完整 `--verbose` 報告是 [`demo.svg`](assets/readme/demo.svg)（`npm run docs:demo`）。</sub>
@@ -312,8 +312,8 @@ e2e/login.spec.ts
   role/text: 1 · testid: 0 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 
 e2e/checkout.spec.ts
-  [█████████████████░░░]  86 / 100
-  role/text: 3 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
+  [██████████████████░░]  88 / 100
+  role/text: 4 · testid: 1 · plain-css: 0 · css-chains: 1 ⚠ · xpath: 0
 ```
 
 這衡量的是**韌性，而非正確性**。`.btn.btn-primary > div:nth-child(2)` 今天能通過，並會一直通過，直到有人改動標記結構。低分從不聲稱測試壞了，只說明它依賴於沒有人承諾保留的標記結構。