dsh-limit-break 1.0.1 → 1.0.2

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/LICENSE CHANGED
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 mapingyue
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 mapingyue
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,80 +1,80 @@
1
- # dsh-limit-break
2
-
3
- Four small tools for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) that came out of a
4
- self-benchmark: two things an agent is normally told it cannot do, made cheap enough to just do.
5
-
6
- | Tool | What it does |
7
- | --- | --- |
8
- | `memory_recall` | Ranked search over a JSON fact store that outlives the session. Omit `query` to list everything. |
9
- | `memory_save` | Write or overwrite one fact: `{ id, statement, value?, unit?, details?, tags?, source? }`. |
10
- | `resilient_fetch` | Fetch with a four-rung ladder and a report of which rung answered. |
11
- | `memory_stats` | Where the store is, how many facts, how big. |
12
-
13
- Zero dependencies. No import-time side effects. Everything fails soft — a broken store or a dead
14
- network returns an error object, never an exception that could take the host down.
15
-
16
- ## Why these four
17
-
18
- **Memory.** A session starts from zero. A store on disk plus a read at the start is enough to beat
19
- that. Measured with two brand-new agents, zero context, the same five questions: **5/5 with the
20
- store, 0/5 without** — and the control did not hallucinate, it answered "I don't have that" five
21
- times.
22
-
23
- **Network.** The reflex "this host is unreachable" is wrong more often than it is right. Measured on
24
- one network, same edge IP, 75 seconds apart: `api.wikimedia.org` → 200 in 0.43 s,
25
- `en.wikipedia.org` → connection reset in 1.21 s, `api.wikimedia.org` again → 200 in 0.39 s. The
26
- block was keyed on the TLS hostname, not the address. So the ladder tries, in order: plain fetch →
27
- IPv6 → IPv4 → a **sibling hostname of the same service** whose certificate still verifies
28
- (`*/wiki/Title` → `api.wikimedia.org/core/v1/wikipedia/<lang>/page/<Title>`).
29
-
30
- It does **not** disable certificate verification and does not route through a proxy that would
31
- impersonate the origin. Those are MITM, not workarounds.
32
-
33
- ## Install
34
-
35
- ```sh
36
- dsh plugin --profile <profile> add dsh-limit-break
37
- ```
38
-
39
- Then restart that profile. In the desktop app, install it from **Settings → Plugins** instead — the
40
- desktop profile is owned by the app's plugin manager.
41
-
42
- The package declares `dsh.bundle` and ships `cordis.patch.yml`, so `dsh plugin add` mounts it with no
43
- manual editing. If you are mounting it by hand, add to `profiles/<profile>/cordis.patch.yml`:
44
-
45
- ```yaml
46
- - insert:
47
- - id: limit-break
48
- name: dsh-limit-break
49
- ```
50
-
51
- A hand-mounted entry still needs the package on the profile's dependency list — a bare `insert` for a
52
- package the profile does not declare is silently ignored.
53
-
54
- ## The store
55
-
56
- `$DSH_HOME/memory/facts.json`, schema:
57
-
58
- ```json
59
- { "schema_version": 1,
60
- "facts": [ { "id": "", "topic": "", "statement": "", "value": "", "unit": "",
61
- "details": "", "source": "", "timestamp": "", "tags": [] } ] }
62
- ```
63
-
64
- Plain JSON on purpose: anything that can read a file can use it, with or without this plugin.
65
- Writes are tmp-file + rename.
66
-
67
- ## Disable / remove
68
-
69
- * Hot: set `disabled: true` on the entry in `cordis.patch.yml` — Cordis recomposes in about a second.
70
- * Cold: `dsh plugin remove dsh-limit-break`, then restart.
71
- * The store is not deleted by either. It lives in `$DSH_HOME/memory/` and is safe to keep.
72
-
73
- ## Privacy
74
-
75
- Nothing leaves the machine. `resilient_fetch` makes the request you asked for; the memory tools read
76
- and write one local file.
77
-
78
- ## License
79
-
80
- MIT.
1
+ # dsh-limit-break
2
+
3
+ Four small tools for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) that came out of a
4
+ self-benchmark: two things an agent is normally told it cannot do, made cheap enough to just do.
5
+
6
+ | Tool | What it does |
7
+ | --- | --- |
8
+ | `memory_recall` | Ranked search over a JSON fact store that outlives the session. Omit `query` to list everything. |
9
+ | `memory_save` | Write or overwrite one fact: `{ id, statement, value?, unit?, details?, tags?, source? }`. |
10
+ | `resilient_fetch` | Fetch with a four-rung ladder and a report of which rung answered. |
11
+ | `memory_stats` | Where the store is, how many facts, how big. |
12
+
13
+ Zero dependencies. No import-time side effects. Everything fails soft — a broken store or a dead
14
+ network returns an error object, never an exception that could take the host down.
15
+
16
+ ## Why these four
17
+
18
+ **Memory.** A session starts from zero. A store on disk plus a read at the start is enough to beat
19
+ that. Measured with two brand-new agents, zero context, the same five questions: **5/5 with the
20
+ store, 0/5 without** — and the control did not hallucinate, it answered "I don't have that" five
21
+ times.
22
+
23
+ **Network.** The reflex "this host is unreachable" is wrong more often than it is right. Measured on
24
+ one network, same edge IP, 75 seconds apart: `api.wikimedia.org` → 200 in 0.43 s,
25
+ `en.wikipedia.org` → connection reset in 1.21 s, `api.wikimedia.org` again → 200 in 0.39 s. The
26
+ block was keyed on the TLS hostname, not the address. So the ladder tries, in order: plain fetch →
27
+ IPv6 → IPv4 → a **sibling hostname of the same service** whose certificate still verifies
28
+ (`*/wiki/Title` → `api.wikimedia.org/core/v1/wikipedia/<lang>/page/<Title>`).
29
+
30
+ It does **not** disable certificate verification and does not route through a proxy that would
31
+ impersonate the origin. Those are MITM, not workarounds.
32
+
33
+ ## Install
34
+
35
+ ```sh
36
+ dsh plugin --profile <profile> add dsh-limit-break
37
+ ```
38
+
39
+ Then restart that profile. In the desktop app, install it from **Settings → Plugins** instead — the
40
+ desktop profile is owned by the app's plugin manager.
41
+
42
+ The package declares `dsh.bundle` and ships `cordis.patch.yml`, so `dsh plugin add` mounts it with no
43
+ manual editing. If you are mounting it by hand, add to `profiles/<profile>/cordis.patch.yml`:
44
+
45
+ ```yaml
46
+ - insert:
47
+ - id: limit-break
48
+ name: dsh-limit-break
49
+ ```
50
+
51
+ A hand-mounted entry still needs the package on the profile's dependency list — a bare `insert` for a
52
+ package the profile does not declare is silently ignored.
53
+
54
+ ## The store
55
+
56
+ `$DSH_HOME/memory/facts.json`, schema:
57
+
58
+ ```json
59
+ { "schema_version": 1,
60
+ "facts": [ { "id": "", "topic": "", "statement": "", "value": "", "unit": "",
61
+ "details": "", "source": "", "timestamp": "", "tags": [] } ] }
62
+ ```
63
+
64
+ Plain JSON on purpose: anything that can read a file can use it, with or without this plugin.
65
+ Writes are tmp-file + rename.
66
+
67
+ ## Disable / remove
68
+
69
+ * Hot: set `disabled: true` on the entry in `cordis.patch.yml` — Cordis recomposes in about a second.
70
+ * Cold: `dsh plugin remove dsh-limit-break`, then restart.
71
+ * The store is not deleted by either. It lives in `$DSH_HOME/memory/` and is safe to keep.
72
+
73
+ ## Privacy
74
+
75
+ Nothing leaves the machine. `resilient_fetch` makes the request you asked for; the memory tools read
76
+ and write one local file.
77
+
78
+ ## License
79
+
80
+ MIT.
package/cordis.patch.yml CHANGED
@@ -1,13 +1,13 @@
1
- # dsh-limit-break — bundle patch
2
- #
3
- # Mounted automatically when the package is installed with `dsh plugin add dsh-limit-break`.
4
- # Four tools, no daemon, no network at import time:
5
- # memory_recall / memory_save — a JSON fact store at $DSH_HOME/memory/facts.json
6
- # resilient_fetch — fetch, then IPv6, then IPv4, then a same-service alias host
7
- # memory_stats — where the store is and how much is in it
8
- - insert:
9
- - id: limit-break
10
- name: dsh-limit-break
11
- config:
12
- requestTimeoutMs: 12000
13
- shellFallback: true
1
+ # dsh-limit-break — bundle patch
2
+ #
3
+ # Mounted automatically when the package is installed with `dsh plugin add dsh-limit-break`.
4
+ # Four tools, no daemon, no network at import time:
5
+ # memory_recall / memory_save — a JSON fact store at $DSH_HOME/memory/facts.json
6
+ # resilient_fetch — fetch, then IPv6, then IPv4, then a same-service alias host
7
+ # memory_stats — where the store is and how much is in it
8
+ - insert:
9
+ - id: limit-break
10
+ name: dsh-limit-break
11
+ config:
12
+ requestTimeoutMs: 12000
13
+ shellFallback: true