From d2a9b5a0f52a2a8aa41c20b7c94370d94454e359 Mon Sep 17 00:00:00 2001
From: Anton Antonov <antonov@trtd.pro>
Date: Thu, 15 Oct 2026 15:35:58 +0300
Subject: [PATCH] Install into the desktop profile and diagnose browser
 delivery

The host half is confirmed working end to end: the ledger holds 24 calls
and the authenticated route returns a real total (6.42 RUB, 14 calls, all
attributed, zero unpriced or unattributed). The plugin is present in the
browser boot manifest, so its bundle is served.

Remaining issue is browser delivery only: the pill stays silent, and the
client swallows the transport error. Recon scripts added to pin down
whether the route answers 200, 401 or 404 from the page origin.
---
 package.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package.json b/package.json
index 5634cf8..b563350 100644
--- a/package.json
+++ b/package.json
@@ -28,6 +28,6 @@
     }
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh": "^0.2.0-rc.2"
+    "react": "^18.0.0"
   }
 }