Clarify JSR-only Connect install docs

Author: HDauven

README.md

@@ -117,12 +117,14 @@ This demo focuses on inspecting a data-driver schema and invoking methods based
 
 ## Install
 
+Published package:
+
 ```bash
-npm i @dusk/connect
+npx jsr add @dusk/connect
+# or, in Deno:
+deno add jsr:@dusk/connect
 ```
 
-JSR uses the same package name:
-
 ```ts
 import { createDuskWallet } from "@dusk/connect";
 ```
@@ -544,7 +546,10 @@ Produces ESM + types in `dist/`.
 
 ## Publishing
 
-The package is published as `@dusk/connect` on npm and JSR.
+The package is published as `@dusk/connect` on JSR.
+
+npm publishing is intentionally separate; do not assume npm availability unless
+a later npm release under an appropriate npm scope is announced.
 
 Before publishing v0.1:
 

docs/RELEASE_CHECKLIST_v0.1.md

@@ -30,7 +30,7 @@ the owner docs instead of restating their full specifications.
 
 ## Release Hygiene
 
-- [ ] Confirm package metadata is correct for `@dusk/connect@0.1.0` on npm and JSR.
+- [ ] Confirm package metadata is correct for `@dusk/connect@0.1.0` on JSR.
 - [ ] Published package contents and extension artifacts are validated from clean builds.
 - [ ] `npx jsr publish --dry-run` passes before manual JSR publish.
 - [ ] Dependency update and security advisory PRs are triaged before release tagging.

examples/systemconfig-demo/main.js

@@ -525,7 +525,7 @@ async function sendTx(fnName, args) {
   setBadge(ui.txBadge, "info", "submitting");
 
   try {
-    /** @type {import("\-network/connect").TxHandle} */
+    /** @type {import("@dusk/connect").TxHandle} */
     const tx =
       args === undefined
         ? await c.write[fnName](undefined, { amount: "0", deposit: "0" })