OCR caution, scanner warning, table-fact labels and deleted-document titles (split from #3707)

data/hazard-register-snapshot.json

@@ -19,7 +19,7 @@
       "authority": "Static evidence register only. It does not establish clinical adequacy, regulatory classification, or risk acceptance.",
       "signedOff": false,
       "gate": "check:clinical-hazard-controls",
-      "reviewedAt": "2026-08-23",
+      "reviewedAt": "2026-10-21",
       "reviewExpiresAt": "2026-11-23",
       "reviewExpired": false,
       "hazards": [

data/repo-awareness-snapshot.json

@@ -5483,6 +5483,11 @@
         "section": "decisions",
         "catalogued": true
       },
+      {
+        "path": "docs/decisions/2026-10-21-no-malware-scan-before-upload-storage.md",
+        "section": "decisions",
+        "catalogued": true
+      },
       {
         "path": "docs/superpowers/rag-upgrade/execution-artifacts/rag-answer-quality-and-repository-coverage-v1/README.md",
         "section": "superpowers",

docs/clinical-hazard-analysis.md

@@ -90,7 +90,7 @@ So an unvalidated, unknown-provenance document is routinely presented as a high-
 | ID      | Failure scenario                                                                                                                                                                                                                                                                                                                                                                        | Severity | Plaus.                      | Control                                                                                          | Test                                                           | Gap                                                                          |
 | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | --------------------------- | ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | ---------------------------------------------------------------------------- |
 | **H2b** | An `outdated` chunk out-ranks a current one. Freshness/status penalties exist (`-0.04` at [`clinical-search.ts:1646`](../src/lib/clinical-search.ts), [`rag-second-stage.ts:100`](../src/lib/rag/rag-second-stage.ts); date-decay in `ranking-config.ts`) but are an order of magnitude below relevance boosts (`+0.06…+0.38`) and are **zero when dates are null** (the default).      | High     | Medium (needs metadata set) | small penalties [`clinical-search.ts:1646`](../src/lib/clinical-search.ts)                       | `ranking-config.test.ts` proves the _math_, not the _ordering_ | No "current beats outdated on tie" rule; penalty is summed flat and clamped. |
-| **H2c** | The one hard block, `sourceGovernanceRefusalAnswer` ([`source-governance.ts:57`](../src/lib/source-governance.ts)), fires only on `severity==="danger"` — i.e. literal `document_status==="outdated"` or `extraction_quality==="poor"` ([`source-governance.ts:164`](../src/lib/source-governance.ts)). Because `outdated` is essentially never set, this block is dormant in practice. | High     | Medium                      | `hasDangerSourceGovernanceWarning` [`source-governance.ts:364`](../src/lib/source-governance.ts) | `tests/source-governance.test.ts`                              | Depends on metadata that the pipeline never populates.                       |
+| **H2c** | The one hard block, `sourceGovernanceRefusalAnswer` ([`source-governance.ts:57`](../src/lib/source-governance.ts)), fires only on `severity==="danger"` — i.e. literal `document_status==="outdated"` or `extraction_quality==="poor"` ([`source-governance.ts:164`](../src/lib/source-governance.ts)). Because `outdated` is essentially never set, this block is dormant in practice. | High     | Medium                      | `hasDangerSourceGovernanceWarning` [`source-governance.ts:393`](../src/lib/source-governance.ts) | `tests/source-governance.test.ts`                              | Depends on metadata that the pipeline never populates.                       |
 | **H2d** | `review_due` is filtered **out** of the frontend banner (`frontendVisibleWarningCodes` omits it, [`source-governance.ts:84`](../src/lib/source-governance.ts)); a review-due source surfaces with only a badge tone.                                                                                                                                                                    | Medium   | Low                         | —                                                                                                | test asserts it is _hidden_                                    | No review-due caveat in the answer prose or the warnings channel.            |
 
 ### H3 — A safety caveat present on screen is stripped on copy/export