dominus-cli 2.2.0 → 2.3.0

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog
 
+## 2.3.0 (2026-07-15)
+
+### Roblox building toolkit
+
+- Added `studio_clone_instances` for safe deep cloning of Parts, Models, UI,
+  scripts, and arbitrary instance trees. Clones support renaming, reparenting,
+  root property overrides, repeated copies, and spatial offsets without arbitrary
+  Luau execution.
+- Added `studio_create_parts` for building up to 200 Parts, Wedges, MeshParts,
+  Seats, SpawnLocations, and related BaseParts in one batch, with optional Model
+  or Folder grouping.
+- Added `studio_transform_instances` using `PVInstance:PivotTo()`, so Models and
+  BaseParts support exact CFrames plus world/local position and rotation offsets.
+- Added `studio_group_instances`, `studio_ungroup_instances`,
+  `studio_create_welds`, `studio_query_parts`, and `studio_set_selection` for
+  hierarchy organization, rigid assemblies, spatial inspection, and Studio UX.
+- Extended atomic `studio_apply` and parallel worker proposals with a typed
+  `clone` operation. Coordinators validate clone source and destination scopes,
+  detect destination conflicts, and verify the resulting hierarchy.
+
+### Safety and reliability
+
+- All new writes run through dedicated allowlisted plugin commands and one
+  ChangeHistoryService recording, with stable-ref validation, item limits,
+  rollback, and read-back-ready refs. Arbitrary `run_code` remains unavailable.
+- Added tests for the 25-tool MCP catalog, clone routing, batch part creation,
+  transform validation, and packaged building command hardening.
+- Pinned Rojo `7.6.1` with Rokit so plugin builds use a current reflection database
+  and consistently preserve `RunContext.Plugin`.
+
+## 2.2.1 (2026-07-13)
+
+### Stable Studio bridge architecture
+
+- Moved WebSocket ownership out of individual MCP stdio processes and into one
+  detached local bridge daemon. MCP hosts now act as controllers, so closing or
+  restarting one agent no longer disconnects Studio or other agents.
+- Added race-safe bridge startup and reuse. Concurrent MCP launches converge on
+  the same loopback bridge instead of creating separate connection state.
+- The plugin installer now starts the bridge automatically and provisions the
+  user-specific 256-bit credential into the local plugin. Manual connection IDs
+  and six-digit pairing codes are no longer part of setup or recovery.
+- Built the plugin root with `RunContext.Plugin` and added an entry-point guard.
+  Starting a Play test can no longer launch duplicate Client and Server Dominus
+  sessions from one Studio window.
+- Added regressions for plugin run context, seamless credential provisioning,
+  unauthorized plugin rejection, and bridge survival across MCP controller exits.
+
 ## 2.2.0 (2026-07-13)
 
 ### MCP-native multi-agent coordinator

package/README.md

@@ -8,14 +8,17 @@ Luau execution.
 ## What changed
 
 - MCP-only product: the old Ink chat CLI is no longer published.
-- 17 focused tools with input/output schemas, structured results, and risk hints.
+- 25 focused tools with input/output schemas, structured results, and risk hints.
 - MCP-native parallel coordination uses the host's model through Sampling, with
   proposal-only workers and coordinator-owned Studio writes.
 - Stable instance refs survive dots in names, renames, reparenting, and duplicate
   sibling names for the life of the Studio session.
 - Script writes require a revision from `studio_read_script`.
 - Mutation batches and UI replacement are undoable and roll back on failure.
-- The installer provisions a private bridge token into the local Studio plugin.
+- The installer provisions a local bridge credential automatically; users never
+  copy connection IDs or pairing codes.
+- A single background bridge keeps Studio connected while MCP hosts and agents
+  start, stop, or run in parallel.
 - Multiple Studio windows are selected by unique connection ID, not place ID.
 - Roblox Creator Docs API lookup is built in.
 
@@ -65,7 +68,7 @@ For a version-pinned configuration that does not require a global install:
   "mcpServers": {
     "dominus": {
       "command": "npx",
-      "args": ["-y", "-p", "dominus-cli@2.2.0", "dominus-mcp"]
+      "args": ["-y", "-p", "dominus-cli@2.3.0", "dominus-mcp"]
     }
   }
 }
@@ -75,9 +78,13 @@ Restart the MCP client after changing its configuration.
 
 ## First connection
 
-1. Run `dominus-install-plugin`; restart Roblox Studio only if it does not reload.
-2. Start the MCP client so `dominus-mcp` is running.
-3. Open Roblox Studio. The plugin connects and authenticates automatically.
+1. Run `dominus-install-plugin`; it installs the personalized plugin and starts
+   the local Studio bridge in the background.
+2. Open Roblox Studio and start the MCP client. Dominus authenticates
+   automatically with no connection ID or pairing code.
+
+If the local credential is replaced or lost, run `dominus-install-plugin` again.
+Studio normally reloads it without a restart.
 
 If several Studio windows are open, call `dominus_select_studio` with the exact
 connection ID before editing. Two windows on the same place ID remain distinct.
@@ -96,6 +103,12 @@ For UI fidelity work, use `studio_snapshot_ui` after `studio_build_ui` and compa
 fonts, UDim2 values, colors, strokes, and hierarchy rather than relying on a
 successful write response alone.
 
+For 3D building, use `studio_create_parts` for batches and
+`studio_clone_instances` when an existing object is the template. Models and
+parts can be moved safely with `studio_transform_instances`, organized with the
+grouping tools, connected with `studio_create_welds`, and discovered spatially
+with `studio_query_parts`.
+
 For broad tasks with independent branches, use `run_parallel_task`. Dominus
 partitions immediate child scopes, supplies each worker with hierarchy and typed
 property evidence, runs up to five Sampling workers concurrently, validates their
@@ -123,11 +136,19 @@ Studio inspection:
 - `studio_snapshot_ui`
 - `studio_get_output`
 - `studio_get_reflection`
+- `studio_query_parts`
 
 Studio changes and verification:
 
 - `studio_update_script`
 - `studio_apply`
+- `studio_create_parts`
+- `studio_clone_instances`
+- `studio_transform_instances`
+- `studio_group_instances`
+- `studio_ungroup_instances`
+- `studio_create_welds`
+- `studio_set_selection`
 - `studio_delete_instances`
 - `studio_build_ui`
 - `studio_run_test`
@@ -139,12 +160,13 @@ Roblox documentation:
 
 ## Security model
 
-The MCP transport is stdio. The separate Studio WebSocket bridge binds only to
-`127.0.0.1`, limits messages to one MiB, rate-limits sockets, times out incomplete
-handshakes, and authenticates both Studio plugins and relay controllers. The local
-installer injects a user-specific token into the plugin, so no manual pairing flow
-is needed. The plugin only accepts an explicit command allowlist and contains no
-`loadstring` executor.
+The MCP transport is stdio. A single background Studio WebSocket bridge binds
+only to `127.0.0.1`, limits messages to one MiB, rate-limits sockets, times out
+incomplete handshakes, and authenticates both Studio plugins and MCP controllers.
+The distributed plugin contains only a credential placeholder;
+`dominus-install-plugin` writes the user-specific token into the local copy. The
+plugin only accepts an explicit command allowlist and contains no `loadstring`
+executor.
 
 The bridge token protects against accidental or opportunistic access by unrelated
 local processes. Like other user-level credentials, it cannot protect against a