fix(mcp): expand challenge mode enum to all 9 modes — unblocks voice-dump suppression

[klappy]

Schema unblock for the voice-dump suppression invariant

Caught by actually testing the production preview after PR #100 merged. The MCP tool's mode parameter Zod schema only accepted exploration, planning, execution — but odd/challenge/stakes-calibration defines 9 modes. The 6 writing-lifecycle modes were unreachable from the public API.

Demonstration

$ curl -sS -X POST https://main-oddkit.klappy.workers.dev/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{
    "name":"oddkit_challenge",
    "arguments":{"input":"...","mode":"voice-dump"}
  }}'

# Returns: MCP error -32602: Invalid arguments — mode must be
# "exploration" | "planning" | "execution"

The voice-dump suppression invariant — the load-bearing feature PR #100's evidence note specifically calls out — was unreachable from the public MCP tool. Schema validation rejected the call before runtime ever saw it.

Fix

Two enum sites in workers/src/index.ts expanded from 3 modes to all 9.

How three layers of verification missed this

• TypeScript typecheck: passed (the enum is a valid Zod construct)
• Parser-fidelity test (97/97): passed (tests parsing, not schema)
• Smoke test (6/6): passed (tests CLI legacy path, not MCP)
• Cloudflare preview deploy: succeeded (deploy != contract verification)

The CI "Test CF Preview" job failed on cold-start timeout (red herring) and exercised orient/search/validate/preflight — none of them with mode: voice-dump. The bug was reachable only by calling the tool with the load-bearing mode value through the public contract.

Longer-term follow-up (not this PR)

Drop the enum entirely. Let canon be the validator. Runtime already validates against the calibration table at fetchStakesCalibration time. Having the schema also enforce vocabulary is the same Vodka Architecture anti-pattern PR #100 fixed for stop words — domain opinion living in worker source instead of canon. Tracked as a follow-up issue.

Effect on PR #101 (prod promotion)

Hold #101 until this lands. Promoting PR #100 to prod without this fix ships a feature whose load-bearing invariant is unreachable.

Verification

• npm run typecheck: clean
• workers/test/governance-parser.test.mjs: 97/97 against main
• Manual preview curl with mode=voice-dump pending after this deploys
• Cloudflare auto-deploys preview on push for re-verification

Lesson recorded

Testing the running preview is not optional. Three layers of verification missed this because none exercised the public API contract end-to-end. Adding a preview-contract test (curl-based, exercises every documented mode value) is the next workflow improvement.

---

Note

Low Risk
Low risk: only broadens Zod validation for the mode argument on oddkit and oddkit_challenge, with no execution-path changes beyond accepting additional enum values.

Overview
Updates the MCP request schemas so the mode parameter accepts all 9 canon-defined modes (adds writing-lifecycle values like voice-dump, drafting, and published-essay) instead of only exploration/planning/execution.

This unblocks clients from calling oddkit and oddkit_challenge with mode=voice-dump (and related lifecycle modes) without failing argument validation, and clarifies the mode semantics in the parameter descriptions.

^{Reviewed by Cursor Bugbot for commit 3a58851. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	oddkit	3a58851	Commit Preview URL Branch Preview URL	Apr 17 2026, 03:22 PM