pi-beyin 0.1.7 → 0.1.8

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/README.md CHANGED
@@ -77,20 +77,20 @@ The extensions call `beyin.py` (read-only unless the agent runs a write command)
77
77
  A vault whose `beyin.py` does not accept `--harness pi` needs `tools/pi-harness-patch.py ensure
78
78
  --vault <vault>` (the extension does this on session start).
79
79
 
80
- ## Relationship to beyin v3
81
-
82
- `pi-beyin` is the **pi-side** adapter; the vault, `beyin.py` and the canonical skill templates belong to
83
- beyin v3 and keep their own release cycle.
84
-
85
- - `tools/pi-harness-patch.py` is the only thing that touches beyin's files: it adds `pi` to the harness
86
- list in two managed modules (plus three pi-specific fixes) and re-syncs the install manifest so
87
- `beyin.py update` plans cleanly. **A beyin update reverts these edits**; the extension calls `ensure`
88
- on session start, so they come back by themselves. `status` is read-only.
89
- - The skills here are **copies for pi**, not links into the vault. beyin still installs its own copies
90
- under `.claude/skills/` for the other harnesses; pi does not read that directory.
91
- - Notifications stay in the adapter: the injected context, the receipt reminder, the distillation
92
- suggestion and the `beyin_jev_*` tool descriptions ship with this package. They are written in Turkish
93
- today (the author's language); anything a *skill* writes follows the user's language.
80
+ ## Scope
81
+
82
+ This package is the **pi side**: extensions, skills and the harness patch. The vault and its `beyin.py`
83
+ CLI are yours to install and update separately; this package never needs to know their version.
84
+
85
+ - `tools/pi-harness-patch.py` is the only piece that touches the vault's Python: it adds `pi` to the
86
+ harness list in five managed modules and re-syncs the install manifest so updates plan cleanly.
87
+ An update of the vault reverts those edits; the extension calls `ensure` on session start, so they
88
+ come back by themselves. `status` is read-only.
89
+ - The skills here are **copies for pi**, not links into the vault. Other harnesses keep their own copies
90
+ under `.claude/skills/`; pi does not read that directory.
91
+ - Notifications live in the adapter: the injected context, the receipt reminder, the distillation
92
+ suggestion and the `beyin_jev_*` tool descriptions ship here. They are written in Turkish today (the
93
+ author's language); anything a *skill* writes follows the user's language.
94
94
 
95
95
  ## Project memory skills
96
96
 
@@ -0,0 +1,33 @@
1
+ # Third-party notices
2
+
3
+ ## beyin
4
+
5
+ `tools/pi-harness-patch.py` contains short source excerpts from the beyin vault code that it patches
6
+ (the harness tuples, the Jev request headers and the assessment entry point). Those excerpts remain
7
+ under beyin's license:
8
+
9
+ ```
10
+ MIT License
11
+
12
+ Copyright (c) 2026 Forn
13
+
14
+ Permission is hereby granted, free of charge, to any person obtaining a copy
15
+ of this software and associated documentation files (the "Software"), to deal
16
+ in the Software without restriction, including without limitation the rights
17
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
18
+ copies of the Software, and to permit persons to whom the Software is
19
+ furnished to do so, subject to the following conditions:
20
+
21
+ The above copyright notice and this permission notice shall be included in all
22
+ copies or substantial portions of the Software.
23
+
24
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
25
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
26
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
27
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
28
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
29
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
30
+ SOFTWARE.
31
+ ```
32
+
33
+ Everything else in this repository is MIT, see [LICENSE](LICENSE).
@@ -1,5 +1,5 @@
1
1
  /**
2
- * Beyin V3 — pi-native bridge (the pi equivalent of the beyin hook).
2
+ * pi-native bridge for the beyin vault (the pi equivalent of the beyin hook).
3
3
  *
4
4
  * Beyin's OMP/OpenCode/Claude/Codex hooks do not run in pi. This extension pulls
5
5
  * relevant notes from the local second brain on every user prompt and injects them
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-beyin",
3
- "version": "0.1.7",
3
+ "version": "0.1.8",
4
4
  "description": "pi-native bridge for the beyin second brain: context injection, distillation reminders, and Jev advisor tools.",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -34,7 +34,8 @@
34
34
  "skills",
35
35
  "tools",
36
36
  "README.md",
37
- "LICENSE"
37
+ "LICENSE",
38
+ "THIRD-PARTY-NOTICES.md"
38
39
  ],
39
40
  "scripts": {
40
41
  "test": "bash test/run.sh",
@@ -236,14 +236,14 @@ the applications are closed. In sparse-check or manual mode, refresh the source
236
236
  information is needed; don't assume an old session context is current. Work started earlier may have finished;
237
237
  turning it off stops the next jobs.
238
238
 
239
- The default V3 engine makes no automatic call to Luna, Sonnet or any other model. The Jev auto_context feature,
239
+ The default engine makes no automatic call to Luna, Sonnet or any other model. The Jev auto_context feature,
240
240
  which the user enables explicitly and separately, is a limited, optional remote consultation outside that rule.
241
241
  Local checks consume no tokens; the results the agent writes and the context it reads or adds count toward the
242
242
  client's usage. A character limit is not a guarantee of token count or cost. A 15-minute agent automation the
243
243
  user installed separately is not governed by this setting; examine it separately. Don't add a paid scheduler, a
244
244
  model runner or a new dependency without being asked.
245
245
 
246
- V3.1: the `updates` section inside `doctor` shows the latest version check; a network error does not prove being
246
+ The `updates` section inside `doctor` shows the latest version check; a network error does not prove being
247
247
  up to date. Use `beyin.py update --check --metadata-only` only for a version question. Route an update request to
248
248
  the `brain-update` skill.
249
249
 
@@ -64,7 +64,7 @@ Tell the user three things: the part that works, the unverified/broken part, and
64
64
  one. Give a short, concrete result instead of raw JSON. If the user's existing approval covers the safe fix, don't
65
65
  ask again for nothing.
66
66
 
67
- V3.1: the `updates` section inside `doctor` shows the latest version check; a network error does not prove being up
67
+ The `updates` section inside `doctor` shows the latest version check; a network error does not prove being up
68
68
  to date. Use `beyin.py update --check --metadata-only` only for a version question. Route an update request to the
69
69
  `brain-update` skill.
70
70
 
@@ -33,7 +33,7 @@ user step.
33
33
  In the result message give the previous→new version, the verification result and any step left open. Don't share
34
34
  tokens, local user paths, personal settings dumps or raw logs.
35
35
 
36
- If `--metadata-only` is not recognized (a version before V3.1), fall back to the existing `update --check`. Version
36
+ If `--metadata-only` is not recognized (older beyin), fall back to the existing `update --check`. Version
37
37
  notifications are an on-by-default daily GitHub metadata check; they post no notes. Apply an off/on request with
38
38
  `preferences --update-notifications off/on`. To silence one version use `update --dismiss X.Y.Z`. A metadata-only
39
39
  result is not proof that the package can be installed.
@@ -1,11 +1,11 @@
1
1
  #!/usr/bin/env python3
2
- """Add "pi" as a first-class Beyin V3 harness, update-safely.
2
+ """Add "pi" as a first-class beyin harness, update-safely.
3
3
 
4
4
  Why this exists
5
5
  ---------------
6
- Beyin V3 knows the harnesses codex/claude/antigravity/hermes/opencode/omp, but not
6
+ beyin knows the harnesses codex/claude/antigravity/hermes/opencode/omp, but not
7
7
  pi. That blocks `beyin.py receipt --harness pi` and `context --harness pi`, so pi
8
- work is mislabeled. Pi runs outside Beyin's own hooks, so the fix has to live here.
8
+ work is mislabeled. pi runs outside beyin's own hooks, so the fix has to live here.
9
9
 
10
10
  How it stays update-safe
11
11
  ------------------------