fix(mcp): add shared operations and secure scene APIs

packages/mcp/src/tools/scene-lifecycle/index.ts

@@ -1,6 +1,5 @@
 import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'
-import type { SceneBridge } from '../../bridge/scene-bridge'
-import type { SceneStore } from '../../storage/types'
+import type { SceneOperations } from '../../operations'
 import { registerDeleteScene } from './delete-scene'
 import { registerListScenes } from './list-scenes'
 import { registerLoadScene } from './load-scene'
@@ -10,19 +9,15 @@ import { registerSaveScene } from './save-scene'
 /**
  * Register the scene-lifecycle MCP tools (`save_scene`, `load_scene`,
  * `list_scenes`, `delete_scene`, `rename_scene`) against the given server.
- * All tools operate against the supplied `SceneStore` so tests can inject an
- * in-memory implementation.
+ * All tools operate against shared scene operations so MCP, REST, and future CLI
+ * entry points share the same storage boundary.
  */
-export function registerSceneLifecycleTools(
-  server: McpServer,
-  bridge: SceneBridge,
-  store: SceneStore,
-): void {
-  registerSaveScene(server, bridge, store)
-  registerLoadScene(server, bridge, store)
-  registerListScenes(server, store)
-  registerDeleteScene(server, store)
-  registerRenameScene(server, store)
+export function registerSceneLifecycleTools(server: McpServer, operations: SceneOperations): void {
+  registerSaveScene(server, operations)
+  registerLoadScene(server, operations)
+  registerListScenes(server, operations)
+  registerDeleteScene(server, operations)
+  registerRenameScene(server, operations)
 }
 
 export { deleteSceneInput, deleteSceneOutput, registerDeleteScene } from './delete-scene'