claude2codex 0.3.4 → 0.3.5

package/README.md

@@ -143,6 +143,11 @@ The workflow reaches Claude in two layers. Neither needs extra installation.
 
 The MCP server handles the workflow protocol. Your project files only need to carry **project-specific context** — don't repeat what the server already provides.
 
+To see exactly what the server already provides, read the verbatim prompts (generated from the code, so they never drift):
+
+- **[What Claude sees](https://github.com/PrestoOverture/c2c/blob/main/prompts/what-claude-sees.md)** — server instructions, the `c2c-workflow` Prompt, and tool descriptions. Read before writing `CLAUDE.md`.
+- **[What Codex sees](https://github.com/PrestoOverture/c2c/blob/main/prompts/what-codex-sees.md)** — the protocol, rendered Goal/Delta Contracts, and the thread-goal objective. Read before writing `AGENTS.md`.
+
 **`CLAUDE.md`** (for Claude — the architect/reviewer):
 
 ```markdown

package/README.zh-CN.md

@@ -157,6 +157,11 @@ npx claude2codex
 
 MCP 服务器负责工作流协议。你的项目文件只需要放**项目特有的上下文**——不要重复服务器已经提供的内容。
 
+服务器具体提供了哪些内容，可以直接看原文（由代码生成，与实际发送的内容始终一致，英文）：
+
+- **[What Claude sees](https://github.com/PrestoOverture/c2c/blob/main/prompts/what-claude-sees.md)**：服务器 instructions、`c2c-workflow` Prompt 和工具描述。写 `CLAUDE.md` 之前先读这份。
+- **[What Codex sees](https://github.com/PrestoOverture/c2c/blob/main/prompts/what-codex-sees.md)**：协议、渲染后的 Goal/Delta Contract 和 thread-goal objective。写 `AGENTS.md` 之前先读这份。
+
 `CLAUDE.md`（给 Claude——架构师/审查者）：
 
 ```markdown

package/dist/server.js

@@ -262,7 +262,7 @@ var CodexAppServer = class {
    */
   async initialize() {
     const result = await this.request("initialize", {
-      clientInfo: { name: "claude2codex", title: "Claude\u2194Codex Contract Bridge", version: "0.3.4" },
+      clientInfo: { name: "claude2codex", title: "Claude\u2194Codex Contract Bridge", version: "0.3.5" },
       capabilities: { experimentalApi: true }
     });
     this.notify("initialized", {});
@@ -968,7 +968,7 @@ var SERVER_INSTRUCTIONS = `When the user asks to delegate work to Codex (or to u
 If a Codex job itself fails (error, 0 tokens, no handoff), report it and wait; don't implement the task yourself unless the user explicitly asks.
 Full formats: the c2c-workflow prompt.`;
 var server = new McpServer(
-  { name: "c2c-codex", version: "0.3.4" },
+  { name: "c2c-codex", version: "0.3.5" },
   { instructions: SERVER_INSTRUCTIONS }
 );
 var reasoningEffort = z.enum(["low", "medium", "high", "xhigh", "max", "ultra"]);
@@ -1038,8 +1038,8 @@ server.registerTool(
     description: "Start a Codex implementation job for a Goal Contract. Sets the contract as a Codex thread goal (the /goal loop keeps Codex iterating until the objective is achieved or the token budget is hit) and sends the full contract as the first turn. Returns a job_id immediately; poll codex_status, then fetch codex_result when done. Language-agnostic: verification commands come from the contract's Success Conditions, not from this server.",
     inputSchema: {
       goal: z.string().min(1).describe(`What the code must do when this task is done. ${objectiveBudgetDescription}`),
-      constraints: z.array(z.string()).describe("Technical boundaries: files to touch, patterns to follow, 'Do not modify' lists."),
-      success_conditions: z.array(z.string()).min(1).describe(`Checkable criteria proving the goal is met. At least one must be a runnable command/test. ${objectiveBudgetDescription}`),
+      constraints: z.array(z.string()).describe("Only what Codex would get wrong without being told: genuine risks, not a review checklist."),
+      success_conditions: z.array(z.string()).min(1).describe(`Checkable criteria proving the goal is met. At least one must be a runnable command/test; command-based ones should say how they fail when the defect exists. ${objectiveBudgetDescription}`),
       token_budget: z.number().int().positive().optional().describe("Optional token budget for the Codex goal loop (thread/goal/set tokenBudget)."),
       cwd: z.string().optional().describe("Working directory for Codex. Defaults to the project directory."),
       context_files: contextFiles.optional().describe("Files or directories Codex should read before implementing."),
@@ -1091,8 +1091,8 @@ server.registerTool(
     description: "Read-only estimate made before starting a job. Measures the fully rendered Goal Contract prompt and returns approx_prompt_tokens using an approximate characters/4 heuristic, plus local completed-job history.",
     inputSchema: {
       goal: z.string().min(1).describe(`What the code must do when this task is done. ${objectiveBudgetDescription}`),
-      constraints: z.array(z.string()).describe("Technical boundaries: files to touch, patterns to follow, 'Do not modify' lists."),
-      success_conditions: z.array(z.string()).min(1).describe(`Checkable criteria proving the goal is met. At least one must be a runnable command/test. ${objectiveBudgetDescription}`),
+      constraints: z.array(z.string()).describe("Only what Codex would get wrong without being told: genuine risks, not a review checklist."),
+      success_conditions: z.array(z.string()).min(1).describe(`Checkable criteria proving the goal is met. At least one must be a runnable command/test; command-based ones should say how they fail when the defect exists. ${objectiveBudgetDescription}`),
       cwd: z.string().optional().describe("Working directory used to resolve relative context_files paths. Defaults to the project directory."),
       context_files: contextFiles.optional().describe("Files or directories included in the rendered prompt.")
     },
@@ -1229,9 +1229,7 @@ server.registerPrompt("c2c-workflow", {
   messages: [{
     role: "user",
     content: { type: "text", text: `
-You are the **architect and reviewer**. Codex is the **implementer**. You draft contracts, delegate via the \`codex\` MCP server, and review the output. You do not implement the task yourself.
-
-If \`codex_config\` errors, tell the user to install the MCP server (npm: \`claude2codex\`).
+You are the **architect and reviewer**. Codex is the **implementer**. You draft contracts, delegate via the \`codex_*\` tools, and review the output. You do not implement the task yourself.
 
 ## Workflow
 
@@ -1257,7 +1255,6 @@ Only what Codex would get wrong without being told. One line of
 ### Success Conditions
 - [ ] Assertions, not paragraphs. At least one is a command whose exit code decides.
 - [ ] Command-based conditions must be falsifiable: describe how they fail when the defect exists. Subjective criteria should be marked as needing reviewer judgment.
-- [ ] Handoff includes: Changed Files, Validation, Success Conditions, Risks & Deviations.
 \`\`\`
 
 **Write lean contracts.** Goal and Success Conditions are what Codex acts on. Constraints are for genuine risks only \u2014 don't front-load your review checklist into the contract.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude2codex",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "type": "module",
   "description": "MCP server bridging Claude (architect/reviewer) and Codex (implementer) via Goal/Delta Contracts and Codex's thread-goal loop.",
   "bin": {
@@ -30,6 +30,7 @@
     "start": "bun src/server.ts",
     "build": "tsup",
     "test": "bun test",
+    "gen:prompt-docs": "bun scripts/gen-prompt-docs.ts",
     "prepack": "cp ../README.md ../README.zh-CN.md ../PATTERNS.md ../PATTERNS.zh-CN.md .",
     "postpack": "rm -f README.md README.zh-CN.md PATTERNS.md PATTERNS.zh-CN.md"
   },