@panaversity/ksor 0.0.23 → 0.0.24
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/CHANGELOG.md +36 -0
- package/dist/cli.mjs +254 -3276
- package/dist/gateway-api-BF06IsJ--D-eI--yB.mjs +3225 -0
- package/dist/gateway.d.mts +144 -0
- package/dist/gateway.mjs +2 -0
- package/docs/index.md +4 -0
- package/docs/tool-surface.md +133 -0
- package/package.json +6 -1
- package/templates/scaffold/AGENTS.md +42 -0
- package/templates/scaffold/system/gateways/content.ts +162 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,41 @@
|
|
|
1
1
|
# @panaversity/ksor
|
|
2
2
|
|
|
3
|
+
## 0.0.24
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- cbdc4c2: The MCP tool surface is now adopter-owned code. `ksor init` emits
|
|
8
|
+
`system/gateways/content.ts` — ordinary `registerTool` calls with ordinary zod —
|
|
9
|
+
where a record sets what its tools are called, what it says it covers, what they
|
|
10
|
+
accept, and which of them exist at all.
|
|
11
|
+
|
|
12
|
+
Agents are the operator, and an agent pays for this surface out of its context
|
|
13
|
+
window twice. Measured against a live 81-document record: the three tool
|
|
14
|
+
definitions cost ~2,990 tokens and stay resident for the whole session, and one
|
|
15
|
+
`search` at the default `k=10` costs ~3,541 tokens per call. Until now a record
|
|
16
|
+
could change none of it. Deleting the two tools your agents never call gives back
|
|
17
|
+
~1,643 tokens a session — verified live at 5,337 bytes of definitions against the
|
|
18
|
+
default's 11,960.
|
|
19
|
+
|
|
20
|
+
Real code rather than a config API, because models are trained on the MCP SDK and
|
|
21
|
+
on zod and not on our field names — and because `registerTool` lets a record add
|
|
22
|
+
its own tools, which no config schema could have anticipated. One import
|
|
23
|
+
(`@panaversity/ksor/gateway`, which re-exports `z` and `McpServer`), so a
|
|
24
|
+
registration stays a file: no package, no build step, nothing new in your
|
|
25
|
+
lockfile. It is **deletable** — without it the door serves the identical surface.
|
|
26
|
+
|
|
27
|
+
The handlers, output schemas and framework description text stay in the package,
|
|
28
|
+
because a hand-written handler returning fabricated hits with plausible
|
|
29
|
+
`stable_id`s passes every shape check there is. Your prose composes ABOVE the
|
|
30
|
+
framework text, never instead of it — and since that is now a template literal in
|
|
31
|
+
a file you own, **the door inspects its own served surface at boot** and refuses
|
|
32
|
+
to start when a guarantee is gone: `ksor-gateway-floor-missing`,
|
|
33
|
+
`ksor-gateway-no-tools`, `ksor-gateway-unloadable`.
|
|
34
|
+
|
|
35
|
+
Adds a public subpath export, `@panaversity/ksor/gateway`.
|
|
36
|
+
|
|
37
|
+
New: `docs/tool-surface.md`.
|
|
38
|
+
|
|
3
39
|
## 0.0.23
|
|
4
40
|
|
|
5
41
|
### Patch Changes
|