@inventarch/mcp-door 3.6.0 → 3.7.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/SPEC.md CHANGED
@@ -2,10 +2,12 @@
2
2
 
3
3
  Knowledge membership budgets apply after intersecting the original Door membership with the optional persisted `.ia/knowledge.json` selection, using the KB library's shared eligibility predicate. Excluded authored records, floor records and excluded body resources do not widen the selected view. The adapter validates the selector before budgeting and passes it to capture, retaining the Door revision check before body reads.
4
4
 
5
- Public language mechanism. The [language reference](LANGUAGE.md) defines vocabulary and evaluation limits. Package exports describe the installed API. Curated agent methods and hosted services are supplied independently.
5
+ Public language mechanism. The [language reference](LANGUAGE.md) defines vocabulary and evaluation limits. Package exports describe the installed API. Curated agent methods and hosted services are [supplied independently](../../docs/reference/hosted-service/README.md).
6
6
 
7
7
  Token expiry (2026-10-30; database D08c, runtime R12): a scope token can expire within this process, and a client reads about tokens here, not in the protocol's prose. The frozen version 1 rows cannot say so, so `initialize` instructions, the `ia_scope` description and the `within` description of all sixteen tools that take one each do, with the recovery: `ia_scope` for a new token, with the same narrowing, not a call without `within`, which reads the initial boundary. `tools/list` stays the table's projection plus `format` and this text. A knowledge tool keeps IA-KB-SCOPE-UNAVAILABLE for a token the Door refuses, and its message says when that token expired. `tests/protocol.test.ts` pins each of those places, the refusals, and that an unknown token's message is unchanged.
8
8
 
9
9
  Knowledge integration adds five tools: `ia_kb_check`, `ia_kb_search`, `ia_kb_read`, `ia_kb_resolve`, `ia_kb_traverse`. They use the public KB protocol DTOs. The original Door validates any scope token, supplies membership, and must agree with the KB native graph revision before bodies are read. Unknown/stale tokens, budget overflow and graph changes refuse without widening scope. Arguments cannot change root or select export paths. Local checks expose selected-record admission and closure; workspace compliance is explicitly not evaluated, and excluded records do not contribute diagnostics. The complete JSON-RPC KB tool-result envelope, including text plus structured content and request id, is bounded to 48 KiB. An oversized result returns a bounded refusal. If the request id itself prevents even that refusal from fitting, the server rejects the request before executing a KB operation with JSON-RPC error -32600 and echoes the original id. That protocol error can exceed 48 KiB; truncating or replacing the id would prevent the caller from matching its request. Existing twelve tools and protocol negotiation are preserved.
10
10
 
11
+ The [kit runtime specification](../../docs/specs/kit-runtime/README.md) is normative for the method tools' contract (kit layout, bindings, sidecars, lanes and resolver equivalence); the paragraph below keeps this package's detail and defers to it on any disagreement.
12
+
11
13
  Method tools: `ia_session`, `ia_catalogue` and `ia_method` follow the kit foundation's door contract (C1). They take structured input only; `subject` reaches no position and is kept only as `sha256:<hex>`, the value the packet's `scope.subject` and the pin's `intent.subject` carry. Each takes an optional absolute `root`, which must be the launch root or a row of `<IA home>/workspace-locations.json` (any of its three formats, runtime `readRegistry`), and refuses `IA-CORE-ROOT-UNREGISTERED` otherwise; a root holding `.ia/src` must open and its governing mandates must admit the read mode for the default actor (runtime `checkRoot`). Kits are the bundled folder (`--kits`, else `IA_KITS_DIR`), then `<IA home>/kits/<folder>/<version>/` unless `IA_CORE_NO_HOME_KITS=1`. At a workspace whose lock installs kits through a `package` entry (contract C7b, `dec-133`, db lock engine 0.1.2), the door reads them from the workspace store through runtime `workspaceKits`, between the bundled kits and the home's, and never from the npm package or another copy; one the store lacks refuses `IA-CORE-KIT-RESTORE-REQUIRED`. `ia_session` at a workspace whose installation needs restoring (a fresh clone of a committed lock) opens with no workspace instead of refusing, and adds `restore` and a briefing line saying to run `ia restore`. `tests/kits-package.test.ts` packs the method fixture's ia-kb kit into the archive its `releases.json` names for 0.9.0, installs it through a package entry and reads it from the store. `ia_method` is runtime `resolveMethod`: the packet `resolve.mjs` prints, field for field and with the same digest, for the same consumer, bindings, kit bytes, carrier and task, with `envelope.host` `mcp-door` and `envelope.cliSource` `in-process`. A `task` pins under `<IA home>/work-v1/<projectOf(root)>/<task>/`: the plugin's `lib/pin.mjs` takes its project from the caller and derives none, and the lanes pass a task only, so the project is the workspace folder's name as a slug (runtime `projectOf`). When the bundled folder is a plugin's `config/kits`, that plugin's `scripts/` and support files are the carrier its implementation digest and retained bytes cover, so a pin written by either reader verifies in the other. A kit's read root is restored in process, under `<IA home>/kit-roots-v1/` and never in the shared temporary folder, from the language base this package carries in `assets/base/` (generated with the CLI's); a kit locked on another base refuses `IA-CORE-CLI-UNSUPPORTED`. `tests/method.test.ts` holds the packets and the pin to the goldens in `tests/fixtures/method`, whose `PROVENANCE.json` names the marketplace commit they were made from and `generate.mjs`, the script that makes them again from a `git archive` of that commit and a built CLI, byte for byte. The seventeen read tools, their schemas and their order are unchanged; the method tools follow them.
package/assets/base.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "id": "inventarch/language",
3
- "version": "3.2.0",
4
- "archive": "7b36e4b4959a7bead1c57906cd346b419f32570dac0ac764af805ad20cd63b16",
5
- "manifest": "03a226569c510efaea971dbc41c353998319c33b77ab636d192b549e50f4e732"
3
+ "version": "3.2.1",
4
+ "archive": "ee6e65018df2ebef705913d9da1947f040edf44c2e7ade6c9750c6fa0185985e",
5
+ "manifest": "b6c5e0cc9149b874c11898e63c19082c9742acaf71bde192a2ec9fa6dd3f9fab"
6
6
  }
@@ -2,7 +2,7 @@
2
2
  "version": 1,
3
3
  "language": "ia 1.0",
4
4
  "status": "public IA 1.0 language contract",
5
- "sourceDigest": "6b36475d89b787e364c44ad5b8ba479b19787990c9fdb1d93a72af8b825c993a",
5
+ "sourceDigest": "56953848c899f9b29e39d697b477b178a4fc6d472d995a6177039fd383d55b20",
6
6
  "words": [
7
7
  {
8
8
  "word": "agent",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@inventarch/mcp-door",
3
- "version": "3.6.0",
3
+ "version": "3.7.0",
4
4
  "type": "module",
5
5
  "main": "./dist/main.js",
6
6
  "types": "./dist/main.d.ts",
@@ -14,9 +14,9 @@
14
14
  "LANGUAGE.md"
15
15
  ],
16
16
  "dependencies": {
17
- "@inventarch/distribution": "3.6.0",
18
- "@inventarch/kb": "3.6.0",
19
- "@inventarch/runtime": "3.6.0"
17
+ "@inventarch/distribution": "3.7.0",
18
+ "@inventarch/kb": "3.7.0",
19
+ "@inventarch/runtime": "3.7.0"
20
20
  },
21
21
  "devDependencies": {
22
22
  "@types/node": "^22.19.0",