@voiden/runner 2.3.0-beta.1 → 2.3.0-beta.11
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 +68 -0
- package/bundled-runners/versions.json +2 -0
- package/bundled-runners/voiden-faker-runner.js +6 -13
- package/bundled-runners/voiden-mcp-client-runner.js +1 -0
- package/bundled-runners/voiden-mcp-tool-runner.js +143 -0
- package/dist/cliPrint.d.ts +7 -0
- package/dist/cliPrint.d.ts.map +1 -0
- package/dist/cliPrint.js +166 -0
- package/dist/cliPrint.js.map +1 -0
- package/dist/envFile.d.ts +12 -1
- package/dist/envFile.d.ts.map +1 -1
- package/dist/envFile.js +77 -19
- package/dist/envFile.js.map +1 -1
- package/dist/headlessContext.d.ts.map +1 -1
- package/dist/headlessContext.js +34 -0
- package/dist/headlessContext.js.map +1 -1
- package/dist/index.js +268 -9
- package/dist/index.js.map +1 -1
- package/dist/lib.d.ts +8 -1
- package/dist/lib.d.ts.map +1 -1
- package/dist/lib.js +10 -2
- package/dist/lib.js.map +1 -1
- package/dist/mcpServing.d.ts +39 -0
- package/dist/mcpServing.d.ts.map +1 -0
- package/dist/mcpServing.js +154 -0
- package/dist/mcpServing.js.map +1 -0
- package/dist/mcpToolCapability.d.ts +158 -0
- package/dist/mcpToolCapability.d.ts.map +1 -0
- package/dist/mcpToolCapability.js +87 -0
- package/dist/mcpToolCapability.js.map +1 -0
- package/dist/plugins/loader.d.ts.map +1 -1
- package/dist/plugins/loader.js +4 -0
- package/dist/plugins/loader.js.map +1 -1
- package/dist/runner.d.ts.map +1 -1
- package/dist/runner.js +7 -2
- package/dist/runner.js.map +1 -1
- package/dist/runtimeVars.d.ts.map +1 -1
- package/dist/runtimeVars.js +18 -0
- package/dist/runtimeVars.js.map +1 -1
- package/dist/toolRegistry.d.ts +102 -0
- package/dist/toolRegistry.d.ts.map +1 -0
- package/dist/toolRegistry.js +38 -0
- package/dist/toolRegistry.js.map +1 -0
- package/package.json +11 -5
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,74 @@
|
|
|
3
3
|
All notable changes to `@voiden/runner` are documented here. This package is
|
|
4
4
|
versioned and released independently of the Voiden desktop app.
|
|
5
5
|
|
|
6
|
+
## v2.3.0-beta.8 - 2026-08-11
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
- `voiden-mcp-tool`'s `planServedTools()` now resolves the project's `.voiden/env-public.yaml`/`env-private.yaml` before running verification, not just before registering an already-served tool's real calls — previously only `registerServedTools()` applied that merge, so a tool whose own request or verify-target request needed a variable that already lives in the project's env file (but wasn't separately handed to the headless process's own env, e.g. via `.mcp.json`'s `env` block) would fail verification and get wrongly withdrawn, even though calling it afterward would have resolved fine. Same class of gap as beta.6's `source: environment` fix, this time for the general env merge rather than declared toolparams. Fixed upstream in `plugin-voiden-mcp-tool`'s `toolCapability.ts`, re-bundled here.
|
|
10
|
+
|
|
11
|
+
## v2.3.0-beta.7 - 2026-08-11
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
- `mcp install`/`mcp uninstall` no longer corrupt `~/.codex/config.toml` — the section-matching regex stopped at the first `[` it saw, which was the `args = [...]` array inside the `[mcp_servers.voiden-mcp]` table itself, so it never consumed that line. A re-install left the old `args` array orphaned as a dangling, unparseable line; an uninstall left it behind entirely, breaking the file for Codex on next launch. Bumps `@voiden/executors` to `0.1.6` for the underlying fix.
|
|
15
|
+
|
|
16
|
+
## v2.3.0-beta.6 - 2026-08-07
|
|
17
|
+
|
|
18
|
+
### Added
|
|
19
|
+
- `source: environment` toolparams can now pin their own `envProfile`/`envName`, resolving that exact profile/environment regardless of how many the project has — previously this only ever auto-resolved when the project had exactly one environment, and silently resolved nothing otherwise. Params without either field keep the old single-environment auto-detect behavior, so existing tools need no changes.
|
|
20
|
+
|
|
21
|
+
### Fixed
|
|
22
|
+
- A tool's verification requests now see the same environment-resolved values a real agent call would — `source: environment` params were previously only resolved for actual tool calls, never for verification, so any tool using one would always fail verification (and get withdrawn) even though the tool itself worked fine when called directly.
|
|
23
|
+
|
|
24
|
+
## v2.3.0-beta.5 - 2026-08-06
|
|
25
|
+
|
|
26
|
+
### Fixed
|
|
27
|
+
- `run_request`/served `/tool` results now report the actually-sent
|
|
28
|
+
`requestHeaders`/`requestBody` (post `{{...}}` substitution) instead of
|
|
29
|
+
the raw, pre-substitution block text — bumps `@voiden/executors` to
|
|
30
|
+
`0.1.5` for the underlying pipeline executor fix. Previously, whenever a
|
|
31
|
+
header or body value contained a template placeholder, the result always
|
|
32
|
+
echoed back the literal `{{token}}` text regardless of whether it actually
|
|
33
|
+
resolved correctly — the request sent was always right, only what got
|
|
34
|
+
reported about it was wrong. Affects every caller of the shared pipeline
|
|
35
|
+
executor, not just `/tool`-served requests.
|
|
36
|
+
|
|
37
|
+
## v2.3.0-beta.4 - 2026-08-06
|
|
38
|
+
|
|
39
|
+
### Fixed
|
|
40
|
+
- A served `/tool`'s `source: environment` param now actually resolves from
|
|
41
|
+
the project's `.voiden/env-public.yaml` / `.voiden/env-private.yaml` files
|
|
42
|
+
(private overrides public), not just the bare `@voiden/mcp-server` process's
|
|
43
|
+
own OS environment. Deliberately simplified vs. the app's full environment
|
|
44
|
+
system — no profiles, no hierarchical/child environments, no "active
|
|
45
|
+
environment" selection (nothing to select from headlessly) — only resolves
|
|
46
|
+
when a project has exactly one environment defined; ambiguous otherwise.
|
|
47
|
+
|
|
48
|
+
## v2.3.0-beta.3 - 2026-08-06
|
|
49
|
+
|
|
50
|
+
### Fixed
|
|
51
|
+
- A verify entry (or a tool's own home section) targeting a file with no
|
|
52
|
+
`request-separator` blocks — i.e. a file that's just one request, with no
|
|
53
|
+
real "sections" to disambiguate between — no longer requires its
|
|
54
|
+
`sectionLabel` to exactly match anything. Previously an unlabeled first
|
|
55
|
+
section's real label (`undefined`, from `parseVoidFileSections()`) never
|
|
56
|
+
matched a saved label like `"Request 1"`, so any tool verifying against
|
|
57
|
+
such a file was incorrectly excluded as `missing-section` even though the
|
|
58
|
+
target was unambiguous. `runVoidFile()`, and both the headless and
|
|
59
|
+
Electron-app tool-capability implementations, now treat a single-section
|
|
60
|
+
file as always resolving to its one request regardless of what
|
|
61
|
+
`sectionLabel` (or none) was given.
|
|
62
|
+
|
|
63
|
+
## v2.3.0-beta.2 - 2026-08-06
|
|
64
|
+
|
|
65
|
+
Published out of lockstep with the desktop app (still `2.3.0-beta.1`) — this
|
|
66
|
+
is an early test release of the `/tool` MCP-serving work below, ahead of the
|
|
67
|
+
next full app release.
|
|
68
|
+
|
|
69
|
+
### Added
|
|
70
|
+
- `voiden-runner tool list` / `voiden-runner tool verify` — discovers `/tool` blocks (the `voiden-mcp-tool` plugin) project-wide and runs their verification requests, reporting `verified`/`unverified`/`failing` per tool. `--cadence` filters which verify entries run; `--json` for machine-readable output; `--write` (opt-in) records the last-computed status back into each `/tool` block. Structural problems (unbound/unresolved placeholders, a verify entry pointing at a missing section, duplicate tool names, a read-only tool on a mutating request) exclude a tool from the report entirely, reported distinctly from a verification failure.
|
|
71
|
+
- `voiden-runner mcp serve [path]` — serves the project as a live MCP server: the same `list_void_files`/`list_requests`/`run_request`/`write_result` tools `@voiden/mcp-server` exposes, plus declared `/tool` capabilities that pass verification. Defaults to stdio; `--http [--port <n>] [--host <addr>]` serves streamable-HTTP instead, bound to `127.0.0.1` only unless `--host` explicitly opts into wider exposure. `--check` prints served/withdrawn/degraded/excluded without starting a live server.
|
|
72
|
+
- New public exports (`discoverTools`, `validateTools`, `verifyTools`, `buildMcpServer`, `registerFixedTools`, `registerDynamicTools`, `planServedTools`, and their types) — the same functions `@voiden/mcp-server` now imports rather than maintaining its own copy of this logic.
|
|
73
|
+
|
|
6
74
|
## v2.2.0 - 2026-07-23
|
|
7
75
|
|
|
8
76
|
### Added
|