Wawa
e618175bba
Wholesale swap of packages/{core,viewer,editor,mcp} and apps/editor with the
versions from the private editor repo, which is the production source of truth.
Setup changes:
- packages/{core,viewer,editor} versions held at 0.7.0 baseline (matching
the most recent published release) so a bump=minor publishes 0.8.0
- packages/mcp held at 0.1.1 (never published; first publish will go through
the new release.yml flow)
- peerDependencies and devDependencies for inter-package @pascal-app/*
references pinned to ^0.7.0 instead of '*' / 'workspace:*' so they are
valid for npm consumers
- Root package.json: TypeScript bumped to 6.0.2, added overrides for
@types/react, @types/react-dom, @types/three to prevent JSX namespace
fragmentation across the workspace
- release.yml extended to also publish editor and mcp; 'both' option renamed
to 'all'; added a sync step that updates inter-package peerDeps/devDeps to
match the new versions on every bump (so viewer/editor/mcp tarballs always
reference the version of core they were built against)
- Root scripts gained release:editor and release:mcp shortcuts
Verification:
- bun install --frozen-lockfile is consistent
- packages/{core,viewer,mcp} build cleanly, dist/index.d.ts emitted
- packages/editor check-types reports 21 pre-existing errors, identical to
what private-editor currently reports
Open PRs against editor-v2 will need rebasing/conflict resolution.
38 lines
1.8 KiB
TypeScript
38 lines
1.8 KiB
TypeScript
import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'
|
|
import type { SceneOperations } from '../../operations'
|
|
import { registerCreateProject } from './create-project'
|
|
import { registerDeleteScene } from './delete-scene'
|
|
import { registerGetProjectStatus } from './get-project-status'
|
|
import { registerListScenes } from './list-scenes'
|
|
import { registerLoadScene } from './load-scene'
|
|
import { registerRenameScene } from './rename-scene'
|
|
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 shared scene operations so MCP, REST, and future CLI
|
|
* entry points share the same storage boundary.
|
|
*/
|
|
export function registerSceneLifecycleTools(server: McpServer, operations: SceneOperations): void {
|
|
registerCreateProject(server, operations)
|
|
registerGetProjectStatus(server, operations)
|
|
registerSaveScene(server, operations)
|
|
registerLoadScene(server, operations)
|
|
registerListScenes(server, operations)
|
|
registerDeleteScene(server, operations)
|
|
registerRenameScene(server, operations)
|
|
}
|
|
|
|
export { createProjectInput, createProjectOutput, registerCreateProject } from './create-project'
|
|
export { deleteSceneInput, deleteSceneOutput, registerDeleteScene } from './delete-scene'
|
|
export {
|
|
getProjectStatusInput,
|
|
getProjectStatusOutput,
|
|
registerGetProjectStatus,
|
|
} from './get-project-status'
|
|
export { listScenesInput, listScenesOutput, registerListScenes } from './list-scenes'
|
|
export { loadSceneInput, loadSceneOutput, registerLoadScene } from './load-scene'
|
|
export { registerRenameScene, renameSceneInput, renameSceneOutput } from './rename-scene'
|
|
export { registerSaveScene, saveSceneInput, saveSceneOutput } from './save-scene'
|