setup-dstacklisted

# Setup DStack This is an explicit setup and diagnostics workflow. It configures the agent client, not the user's game. Do not edit Roblox source, project design documents, or repository instructions unless the user separately asks for that work. Read [`../../references/roblox-engineering.md`](../../references/roblox-engineering.md), [`../../references/roblox-mcp-setup.md`](../../references/roblox-mcp-setup.md), and [`../../models.json`](../../models.json) before changing setup or promising a reviewer lane. ## 1. Identify the parent client Use the active tool surface to identify Claude Code or Codex. Never ask a child to guess the parent. Keep the two install surfaces separate: - Claude Code loads `.claude-plugin/plugin.json`, exposes skills as `/dstack:<skill>`, and refreshes an installed plugin with `/reload-plugins`. - Codex loads `.codex-plugin/plugin.json`, exposes the same skill folders by name, and needs a new task after an install or update so its skill catalog is rebuilt. Do not reference a versioned cache path. If the plugin is not visible under the `dstack` namespace, stop and give the client-specific install command from the repository README rather than pretending setup succeeded. ## 2. Verify the skill surface Check the installed plugin's manifest and canonical `skills/` tree. Confirm: 1. `david-mode` is explicit and is the entry point for non-trivial Roblox work. 2. `unslop` is the only implicitly invoked skill. 3. Other skills remain explicit in the c