misakanet 2.38.0 → 2.40.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,19 +1,38 @@
1
1
  {
2
2
  "name": "misakanet",
3
- "version": "2.38.0",
3
+ "version": "2.40.0",
4
4
  "license": "Apache-2.0",
5
5
  "description": "MisakaNet failure-memory skill — evidence-rated failure lessons for AI agents. DSH bundle: registers the MCP tools as mcp__misakanet__* (misakanet_search/get_lesson/…), served by the public Streamable HTTP endpoint https://misakanet.org/mcp — live tools from an npm install, in any profile, with no local python. A profile that prefers the repo's own stdio server can override the bundle row.",
6
+ "icon": "icon.svg",
6
7
  "files": [
7
8
  "SKILL.md",
8
9
  "skills/",
9
10
  "index.js",
10
11
  "index.d.ts",
12
+ "icon.svg",
13
+ "lib/client.js",
11
14
  "cordis.patch.yml",
12
15
  ".codex-plugin/**"
13
16
  ],
14
17
  "dsh": {
15
18
  "bundle": {
16
19
  "patch": "./cordis.patch.yml"
20
+ },
21
+ "client": {
22
+ "platform": "web",
23
+ "inject": [
24
+ "@deepseek-ai/dsh-client-ui-chat",
25
+ "@deepseek-ai/dsh-client-ui-conversation",
26
+ "@deepseek-ai/dsh-client-ui-sidebar-right",
27
+ "@deepseek-ai/dsh-client-ui-tool"
28
+ ]
29
+ },
30
+ "compatibility": {
31
+ "dshReleases": {
32
+ "0.1.5-rc.1": "compatible",
33
+ "0.1.7-rc.2": "compatible",
34
+ "0.2.0-rc.2": "compatible"
35
+ }
17
36
  }
18
37
  },
19
38
  "repository": {
@@ -26,14 +45,19 @@
26
45
  },
27
46
  "keywords": [
28
47
  "misakanet",
48
+ "dsh",
29
49
  "dsh-plugin",
50
+ "dsh-plugins",
51
+ "deepseek-harness",
52
+ "deepseek-harness-plugin",
53
+ "cordis",
30
54
  "failure-memory",
31
55
  "mcp",
32
56
  "skill",
33
57
  "lessons"
34
58
  ],
35
59
  "peerDependencies": {
36
- "@deepseek-ai/dsh-mcp-client": ">=0.1.0-rc.8 <0.2.0"
60
+ "@deepseek-ai/dsh-mcp-client": ">=0.1.0-rc.8 <0.2.0 || >=0.1.5-rc.1 <0.2.0 || >=0.1.7-rc.1 <0.2.0 || >=0.2.0-rc.1 <0.3.0"
37
61
  },
38
62
  "peerDependenciesMeta": {
39
63
  "@deepseek-ai/dsh-mcp-client": {
@@ -51,12 +75,17 @@
51
75
  "preview": "wrangler dev"
52
76
  },
53
77
  "devDependencies": {
54
- "wrangler": "^4.134.0"
78
+ "wrangler": "^4.144.0"
55
79
  },
56
80
  "overrides": {
57
81
  "sharp": "0.35.4"
58
82
  },
59
83
  "main": "index.js",
84
+ "exports": {
85
+ ".": "./index.js",
86
+ "./client": "./lib/client.js",
87
+ "./package.json": "./package.json"
88
+ },
60
89
  "types": "index.d.ts",
61
90
  "type": "module"
62
91
  }
@@ -41,17 +41,20 @@ Do NOT use MisakaNet for:
41
41
 
42
42
  > **Which surface these examples target.** They are written against the **hosted** endpoint
43
43
  > (`https://misakanet.org/mcp`) — the one `docs/mcp.md` recommends and the one most agents are pointed
44
- > at. The two surfaces differ, and this matters for exactly one tool below:
44
+ > at. Since 2026-09-30 the surfaces agree on every tool this file teaches (issue #2000): the local
45
+ > stdio server adds `misakanet_me_events` as a **proxy** of the hosted tool, so the reuse-evidence
46
+ > steps below work on either install.
45
47
  >
46
- > * **hosted** exposes 7 tools, and `misakanet_me_events` is **one of them**
47
- > (the stdio set minus `misakanet_submit_usage` / `misakanet_usage_status` /
48
- > `misakanet_memory_context`, plus `misakanet_me_events`);
49
- > * a **local stdio** install (`python3 scripts/mcp_server.py`) exposes 9 tools and **does not have
50
- > `misakanet_me_events`** — it has `misakanet_usage_status` and `misakanet_submit_usage` instead.
48
+ > * **hosted** exposes 7 tools, `misakanet_me_events` among them;
49
+ > * a **local stdio** install (`python3 scripts/mcp_server.py`) exposes those same 7 **plus three that
50
+ > only make sense on your machine** — `misakanet_submit_usage`, `misakanet_usage_status` and
51
+ > `misakanet_memory_context`. They read this checkout's own usage meter and `lessons/` corpus, which
52
+ > a hosted endpoint has nothing to answer.
51
53
  >
52
- > So an agent running the local server will get an unknown-tool error from the reuse-evidence steps and
53
- > should use `misakanet_usage_status` there. `docs/mcp.md` carries the full table, and
54
- > `tests/test_mcp_doc_surface.py` keeps this file's tool names in step with it (issue #2000).
54
+ > One caveat that comes with the proxy: on a local install `misakanet_me_events` needs the network
55
+ > (the evidence is aggregated server-side), and answers `hosted_endpoint_unavailable` instead of
56
+ > pretending there is no evidence when it cannot reach the hosted service. `docs/mcp.md` carries the
57
+ > full table, and `tests/test_mcp_doc_surface.py` keeps this file's tool names in step with it.
55
58
 
56
59
  ### Register an agent node
57
60