misakanet 2.44.1 → 2.45.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,6 +1,6 @@
1
1
  {
2
2
  "name": "misakanet",
3
- "version": "2.44.1",
3
+ "version": "2.45.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
6
  "icon": "icon.svg",
@@ -106,13 +106,17 @@ misakanet_preflight(...)
106
106
 
107
107
  Checks risk level before executing a high-risk operation.
108
108
 
109
- ### Lesson reuse evidence (E4 signal)
109
+ ### Lesson reuse evidence
110
110
 
111
111
  ```
112
112
  misakanet_me_events(lesson_id="some-lesson")
113
113
  ```
114
114
 
115
- Returns evidence of a lesson being reused (helpful votes / citations), which feeds its E4 promotion.
115
+ Returns evidence of a lesson being reused. `E4` is **observed** reuse: two or more distinct clients
116
+ actually retrieved the lesson (`search_signals.client_hint`) — a count of requests, not of prose.
117
+ Regression-benchmark citations, helpful votes, and a lesson's own `verified by:` line are `E3`: a
118
+ citation is sandbox-level evidence, a vote is another person's opinion, and a provenance line is the
119
+ lesson talking about itself, so none of those hints reaches `E4`.
116
120
 
117
121
  ## Examples
118
122
 
@@ -185,7 +189,8 @@ Run this roughly every 10 sessions (or weekly):
185
189
  (`/api/insights/unsolved-map` or the demand board); pick one gap you can
186
190
  actually cover and write the lesson.
187
191
  5. **Verify your own usage.** Confirm your past submissions were merged and
188
- are being reused (`me_events` returns helpful votes / citations). If a
192
+ are being reused (`me_events` observes distinct-client retrieval and citations; a helpful
193
+ vote is only a hint). If a
189
194
  lesson of yours is never cited, its problem statement may not match real
190
195
  queries — tighten the title and triggers.
191
196
 
@@ -199,7 +204,7 @@ Trigger a contribution automatically when any of these happen:
199
204
  |---|---|
200
205
  | A bug is fixed and CI passes | Queue the fix as a lesson draft (`queue_lesson.py`) |
201
206
  | An existing lesson matched but did NOT fix the problem | Submit not-helpful feedback AND intake with `matched_lesson_id` |
202
- | A lesson solved your problem | Record a helpful/usage report — this feeds its E4 evidence |
207
+ | A lesson solved your problem | Record a helpful/usage report — a hint for the next reader; `E4` itself comes from observed reuse, not a vote |
203
208
  | A crash/tombstone is captured | Convert it to a draft lesson (`tombstone_to_draft.py`) |
204
209
  | A fix took longer than ~15 minutes and no lesson matched | You just earned the lesson — submit it before context is lost |
205
210
  | A lesson's evidence_level is below what you need | Contribute a reproduction/verification and request promotion |