ForgeaX-Games/forgeax-dsh-game-plugin

## Core Features
- The plugin adds a DSH bundle layer that connects the published @forgeax/game MCP server into a DeepSeek Harness profile.
- It exposes mcp__forgeax__forgeax_status_lite and mcp__forgeax__forgeax_run_current_game as DSH tools.
- It registers the forgeax-game Skill and every forgeax-engine-* Skill shipped in the resolved package on ctx.skills at boot.
- It enforces a workspace guard that denies ForgeaX tool calls whose target_dir is not the current session cwd after realpath resolution.
- It verifies the resolved @forgeax/game package identity instead of containing game logic or a copy of ForgeaX.

## Use Cases
- Running ForgeaX game development workflows inside a DSH session without manually installing ForgeaX Skills into the repository.
- Checking ForgeaX runtime status through the DSH tool surface.
- Running the current ForgeaX game from a DSH session while keeping tool calls confined to the active workspace.

## Technical Details
- The bundle inserts four namespaced rows for launch specification, MCP client, Skill source, and workspace guard.
- The resolver module @forgeax/dsh-game/forgeax-package locates the pnpm-installed @forgeax/game package and publishes the forgeaxGameLaunch service.
- The MCP client uses a stdio transport with serverName: forgeax and bridges tools rather than resources.
- The workspace guard evaluates tools/pre-execute and reports unverifiable calls on tools/post-execute when no session cwd is available.

## Notes
- pnpm must be on PATH because dsh plugin is a thin pnpm forwarder, and Node must be version 22 or higher, matching DSH.
- macOS arm64, Linux x64, and Windows x64 are supported, while platforms without a published @forgeax/game-runtime variant install but fail when the runtime starts.
- DSH must be restarted after adding the bundle, and one-time ForgeaX operations remain CLI subcommands rather than MCP tools.