dominus-cli 2.1.0 → 2.2.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.
@@ -13,8 +13,8 @@ set of Studio inspection, mutation, documentation, and verification tools.
13
13
  text fallbacks, `isError`, and accurate tool risk annotations.
14
14
  - Keep stdio as the MCP transport. It limits the MCP server itself to the process
15
15
  that launched it and avoids exposing another localhost HTTP endpoint.
16
- - Do not depend on legacy sampling, roots, or MCP logging. They are deprecated in
17
- the 2026-07-28 release candidate.
16
+ - Use optional MCP Sampling only for the explicit parallel coordinator. Detect the
17
+ client capability first and keep every normal Studio tool independent of it.
18
18
  - Do not adopt the legacy experimental Tasks API. Long Studio calls remain normal
19
19
  cancellable tool calls until the July Tasks extension is final and broadly
20
20
  supported by clients and the TypeScript SDK.
@@ -30,8 +30,8 @@ Official references:
30
30
 
31
31
  1. MCP host starts `dominus-mcp` over stdio.
32
32
  2. Dominus owns or securely relays to one loopback WebSocket bridge on port 18088.
33
- 3. The Studio plugin authenticates with a persistent random bridge token. First
34
- use requires a six-digit pairing code displayed inside Studio.
33
+ 3. The installer embeds a persistent random bridge token into that user's local
34
+ Studio plugin, allowing automatic authentication without a manual pairing flow.
35
35
  4. Every Studio window receives a unique connection ID. MCP callers select that
36
36
  ID, so two windows editing the same place cannot overwrite each other's target.
37
37
  5. Studio instances are returned as session-scoped instance references with path
@@ -40,16 +40,20 @@ Official references:
40
40
  Failed batches are cancelled and automatically undone.
41
41
  7. Script writes require the revision hash returned by the read operation.
42
42
  8. There is no arbitrary Luau execution tool.
43
+ 9. Broad tasks can opt into an MCP-native coordinator. It partitions immediate
44
+ child branches, sends bounded read-only evidence to concurrent Sampling workers,
45
+ validates scoped proposals, and owns the only atomic Studio write.
43
46
 
44
47
  ## MCP tool surface
45
48
 
46
- - `dominus_status`, `dominus_pair_studio`, `dominus_select_studio`
49
+ - `dominus_status`, `dominus_select_studio`
47
50
  - `studio_get_tree`, `studio_inspect`, `studio_get_selection`
48
51
  - `studio_read_script`, `studio_update_script`
49
52
  - `studio_apply`, `studio_delete_instances`
50
53
  - `studio_build_ui`, `studio_snapshot_ui`
51
54
  - `studio_run_test`, `studio_get_output`
52
55
  - `roblox_search_api`, `roblox_get_api`
56
+ - `run_parallel_task` for Sampling-capable MCP clients
53
57
 
54
58
  The intended agent loop is inspect, plan, apply, read back, test. Tool descriptions
55
59
  and the server prompt make that workflow explicit without embedding another LLM
@@ -62,12 +66,14 @@ inside the MCP server.
62
66
  tool arrays/depth/source lengths.
63
67
  - Dedicated mutation tools only; no `loadstring` or generic `run_code` path.
64
68
  - Explicit destructive tool for deletion.
69
+ - Parallel workers are proposal-only; stable refs must match supplied evidence,
70
+ writes must remain in owned scopes, and overlapping proposals are rejected.
65
71
  - Atomic UI replacement: build and validate off-tree before replacing the live UI.
66
72
  - Output watcher filters every Dominus-prefixed message to prevent feedback loops.
67
73
 
68
74
  ## Verification
69
75
 
70
- - Transport tests cover authentication, pairing, wrong-target responses,
76
+ - Transport tests cover authentication, credential rejection, wrong-target responses,
71
77
  disconnect isolation, duplicate place sessions, and payload rejection.
72
78
  - Protocol and MCP tests cover schema validation and structured result shapes.
73
79
  - Static plugin checks plus `rojo build` verify the packaged plugin model.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dominus-cli",
3
- "version": "2.1.0",
3
+ "version": "2.2.0",
4
4
  "description": "Dominus 2: a secure, MCP-native Roblox Studio engineering agent bridge.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -12,7 +12,7 @@
12
12
  "dev": "tsx src/mcp/index.ts",
13
13
  "dev:mcp": "tsx src/mcp/index.ts",
14
14
  "build": "tsup",
15
- "build:plugin": "rojo build plugin/default.project.json -o plugin/Dominus.rbxm",
15
+ "build:plugin": "rojo build plugin/default.project.json -o plugin/Dominus.rbxmx",
16
16
  "start": "node dist/mcp.js",
17
17
  "test": "vitest run",
18
18
  "test:watch": "vitest",
@@ -55,7 +55,9 @@
55
55
  },
56
56
  "files": [
57
57
  "dist",
58
- "plugin",
58
+ "plugin/default.project.json",
59
+ "plugin/Dominus.rbxmx",
60
+ "plugin/src",
59
61
  "CHANGELOG.md",
60
62
  "docs/DOMINUS_2_PLAN.md"
61
63
  ],