denpex-mcp 0.2.8 → 0.2.10

package/README.md

@@ -7,7 +7,7 @@ straight off disk and hands back the root cause and the fix.
 
 - 🩺 **Root cause + escalating fix** (primary → fallback → emergency), verification command, and prevention.
 - 🧭 **Find the culprit rank** in a distributed/NCCL hang, and route GPU Xid faults to the right node action — offline, instantly.
-- 📚 **Bundled failure encyclopedia** (300+ classes offline; the full corpus runs online) searchable by error code or symptom.
+- 📚 **Bundled failure encyclopedia** (500+ documented classes) searchable by error code or symptom.
 - 🔒 **Zero-egress mode** (`DENPEX_LOCAL=1`): diagnose entirely on-host, nothing leaves the machine. Plus client-side PII scrubbing even in cloud mode.
 
 ---
@@ -95,10 +95,11 @@ secure data centers, and privacy-sensitive labs. Add `DENPEX_LOCAL=1`:
 } } }
 ```
 
-The bundled engine (fast patterns + a 300+-class encyclopedia snapshot + Xid routing + cascade
-localization) covers the common failure classes; the full, continuously-grown corpus and the
-deep-analysis tiers run online. The LLM fallback for novel
-errors is cloud-only and simply unavailable offline.
+The package bundles the same canonical deterministic diagnosis pipeline used by the hosted
+wrapper: 10,700+ patterns, causal detectors and contradiction gates, Xid routing, cross-rank
+cascade localization, and the 500+ class encyclopedia. It returns the initiating rank/node
+when the evidence identifies one. Only the hosted LLM fallback and live-research enrichment
+are unavailable offline.
 
 ---
 
@@ -107,7 +108,7 @@ errors is cloud-only and simply unavailable offline.
 | Tool | What it does | Needs |
 |------|--------------|-------|
 | `diagnose_crash` | Root cause + escalating fix from `logs` / `file` / `dir`. Also accepts `telemetry` (dmesg / nvidia-smi / ibstat), `codeContext`, `topologyMap`, typed `operatorAnswers`, and (after an anonymous MCP restart) the prior `refinementToken`. | canonical cloud by default; explicit offline mode |
-| `lookup_failure` | Search the bundled encyclopedia (300+ classes) by code/keyword/symptom. | works offline |
+| `lookup_failure` | Search the bundled encyclopedia (500+ classes) by code/keyword/symptom. | works offline |
 | `analyze_cascade` | Find the culprit rank in a distributed hang; route Xid faults. | works offline |
 | `submit_fix_outcome` | Report whether a fix worked. **This is what makes the next diagnosis better.** | API key |
 | `check_quota` | Your plan and remaining diagnoses this month. | API key |
@@ -134,10 +135,9 @@ Two fields deserve attention when you write the agent loop:
 - **`confidence: null`** does not mean zero. It means the engine measured this band's
   historical accuracy and declined to state a number. Treat the verdict as a lead. Do
   not substitute the raw score.
-- **`unfalsified: true`** means no falsification contract ran on the verdict. It is
-  always true offline (the offline engine has no contract layer), so an offline
-  `GPU_XID_ECC` has *not* been checked against telemetry that would contradict it.
-  Confirm before you drain a node or file an RMA.
+- **`unfalsified: true`** identifies only the explicitly enabled reduced compatibility
+  fallback, where the canonical contradiction graph did not run. Normal cloud and
+  `DENPEX_LOCAL=1` diagnosis both use the canonical engine and set it to false.
 
 ---
 
@@ -156,10 +156,11 @@ Two fields deserve attention when you write the agent loop:
 
 ```bash
 npm install
-npm run build      # regenerates the offline corpus, then bundles dist/index.js
+npm run build      # regenerates the canonical engine + corpus, then bundles dist/index.js
 npm test           # 111 unit + protocol-integration tests
 npm run inspector  # interactive protocol inspector (MCP Inspector)
 ```
 
-The offline corpus (`src/data/denpex_patterns.json`) is generated from the repo's single
-source of truth via `npm run bundle:patterns` — never hand-edit it.
+The offline corpus (`src/data/denpex_patterns.json`) and canonical engine
+(`src/offline/canonical-engine.mjs`) are generated from the repo's single source of truth
+during `npm run build` — never hand-edit either artifact.