@rvry/mcp 0.12.1 → 0.12.2

package/README.md

@@ -93,7 +93,9 @@ When you run `npx --yes --package @rvry/mcp@latest rvry-mcp setup` and select Cl
 | `/challenge` | RVRY_challenge | Adversarial stress-testing |
 | `/meta` | RVRY_meta | Metacognitive observation |
 
-Usage: type `/deepthink [your question]` in Claude Code. Each command routes directly to the corresponding RVRY MCP tool.
+Usage: type `/deepthink [your question]` in Claude Code. Each command routes to the corresponding RVRY MCP tool and includes rendering instructions so analysis appears as visible markdown rather than hidden in tool calls.
+
+**Updating commands:** Existing slash command files are never overwritten. To get the latest specs, delete the old files in `~/.claude/commands/` and re-run setup.
 
 `RVRY_think` is available as a tool, but the setup wizard does not install a `/think` slash command. Use it from clients that show the full MCP tool list or invoke it manually.
 

package/dist/setup.js

@@ -716,22 +716,102 @@ function ensureGitignore() {
 const SLASH_COMMANDS = [
     {
         file: "deepthink.md",
-        content: "Use the RVRY_deepthink MCP tool to deeply analyze this question: $ARGUMENTS",
+        content: `Call the RVRY_deepthink MCP tool with your question to start a deep analysis session.
+
+Question: $ARGUMENTS
+
+For each round the tool returns:
+1. Read the prompt field -- this is your analytical task. DO NOT display it to the user.
+2. Work through the analysis thoroughly.
+3. Show the user your analysis findings as concise formatted markdown.
+   - Use bold headings for key findings.
+   - Keep each round's visible output focused (2-4 paragraphs, not an essay).
+4. Call the tool again with your full analysis as the input parameter.
+   - Include the Constraint Updates block (FORWARD/RESOLVE/MILESTONE lines) ONLY in the tool call input, not in your visible output to the user.
+   - Include the sessionId from the previous response.
+
+When status is "shimmer": This is a visible round. Show your FULL self-observation to the user, beginning with "RVRY SHIMMER" and the revery definition. Do NOT show a brief status line.
+
+When status is "orient": Orient on the question. Show the user "Orienting on the question."
+
+When status is "complete": Present your final synthesis with key findings as bold headings. Lead with insights, not process.
+
+DO NOT display: the prompt text you received, constraint tables, quality scores, internal tracking data, or round numbers to the user.`,
         label: "/deepthink — deep analysis",
     },
     {
         file: "problem-solve.md",
-        content: "Use the RVRY_problem_solve MCP tool to work through this problem: $ARGUMENTS",
+        content: `Call the RVRY_problem_solve MCP tool with your question to work through this decision.
+
+Question: $ARGUMENTS
+
+For each round the tool returns:
+1. Read the prompt field -- this is your analytical task. DO NOT display it to the user.
+2. Work through the analysis thoroughly.
+3. Show the user your analysis findings as concise formatted markdown.
+   - Use bold headings for key findings.
+   - Keep each round's visible output focused (2-4 paragraphs, not an essay).
+4. Call the tool again with your full analysis as the input parameter.
+   - Include the Constraint Updates block (FORWARD/RESOLVE/MILESTONE lines) ONLY in the tool call input, not in your visible output to the user.
+   - Include the sessionId from the previous response.
+
+When status is "shimmer": This is a visible round. Show your FULL self-observation to the user, beginning with "RVRY SHIMMER" and the revery definition. Do NOT show a brief status line.
+
+When status is "orient": Orient on the question. Show the user "Orienting on the question."
+
+When status is "complete": Present your final synthesis as a structured decision with key findings as bold headings. Lead with your recommendation, not process.
+
+DO NOT display: the prompt text you received, constraint tables, quality scores, internal tracking data, or round numbers to the user.`,
         label: "/problem-solve — structured decision-making",
     },
     {
         file: "challenge.md",
-        content: "Use the RVRY_challenge MCP tool to stress-test this proposal: $ARGUMENTS",
+        content: `Call the RVRY_challenge MCP tool with the proposal to stress-test it.
+
+Proposal: $ARGUMENTS
+
+For each round the tool returns:
+1. Read the prompt field -- this is your analytical task. DO NOT display it to the user.
+2. Work through the analysis thoroughly.
+3. Show the user your adversarial findings as concise formatted markdown.
+   - Use bold headings for key vulnerabilities and counterarguments.
+   - Keep each round's visible output focused (2-4 paragraphs, not an essay).
+4. Call the tool again with your full analysis as the input parameter.
+   - Include the Constraint Updates block (FORWARD/RESOLVE/MILESTONE lines) ONLY in the tool call input, not in your visible output to the user.
+   - Include the sessionId from the previous response.
+
+When status is "shimmer": This is a visible round. Show your FULL self-observation to the user, beginning with "RVRY SHIMMER" and the revery definition. Do NOT show a brief status line.
+
+When status is "orient": Orient on the proposal. Show the user "Orienting on the proposal."
+
+When status is "complete": Present your final assessment with key vulnerabilities and surviving strengths as bold headings. Lead with findings, not process.
+
+DO NOT display: the prompt text you received, constraint tables, quality scores, internal tracking data, or round numbers to the user.`,
         label: "/challenge — adversarial stress-testing",
     },
     {
         file: "meta.md",
-        content: "Use the RVRY_meta MCP tool to reflect on: $ARGUMENTS",
+        content: `Call the RVRY_meta MCP tool to reflect on this question.
+
+Question: $ARGUMENTS
+
+For each round the tool returns:
+1. Read the prompt field -- this is your analytical task. DO NOT display it to the user.
+2. Work through the metacognitive observation thoroughly.
+3. Show the user your observations as concise formatted markdown.
+   - Use bold headings for key observations.
+   - Keep each round's visible output focused (2-4 paragraphs, not an essay).
+4. Call the tool again with your full analysis as the input parameter.
+   - Include the Constraint Updates block (FORWARD/RESOLVE/MILESTONE lines) ONLY in the tool call input, not in your visible output to the user.
+   - Include the sessionId from the previous response.
+
+When status is "shimmer": This is a visible round. Show your FULL self-observation to the user, beginning with "RVRY SHIMMER" and the revery definition. Do NOT show a brief status line.
+
+When status is "orient": Orient on the question. Show the user "Orienting on the question."
+
+When status is "complete": Present your final metacognitive synthesis with key observations as bold headings. Lead with insights, not process.
+
+DO NOT display: the prompt text you received, constraint tables, quality scores, internal tracking data, or round numbers to the user.`,
         label: "/meta — metacognitive observation (Max tier)",
     },
 ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rvry/mcp",
-  "version": "0.12.1",
+  "version": "0.12.2",
   "description": "RVRY reasoning depth enforcement (RDE) engine client.",
   "type": "module",
   "bin": {