@apex-inc/mcp-server 0.12.0 → 0.14.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apex-inc/mcp-server",
-  "version": "0.12.0",
+  "version": "0.14.0",
   "description": "MCP server for Apex — currently in private beta.",
   "type": "module",
   "main": "dist/index.js",

package/skills/apex-experimentation/SKILL.md

@@ -135,7 +135,9 @@ Editability is gated by lifecycle, keyed to DATA:
 - **Running, or any exposures recorded:** the pre-registration (hypothesis, metric, guardrails) and bucketing (surface, variants) FREEZE. `update_experiment` returns `experiment_locked` with the reason — that's intentional, so results stay valid. Do not fight it.
 - **After freeze:** call `fork_experiment({ experimentId })`. It duplicates the design into a fresh draft (no data carries over, lineage recorded), which you then edit and activate.
 
-Surface specifically: `create_experiment` auto-detects mobile vs web from the workspace's data sources; if a Capacitor app got mislabeled `web`, fix it on the draft with `update_experiment({ experimentId, surface: "mobile" })` before the first exposure, or fork if it's already running.
+Surface specifically: `create_experiment` auto-detects mobile vs web from repo signals (capacitor.config.* / @apex-inc/capacitor-plugin) and the workspace's registered data sources when you omit `surface`; if a Capacitor app got mislabeled `web`, fix it on the draft with `update_experiment({ experiment_id, surface: "mobile" })` before the first exposure, or fork if it's already running.
+
+Parameter casing: all tool parameters are **snake_case** (`experiment_id`, `traffic_split`, `primary_metric_event`, `guardrail_event`) — the same convention as event names. camelCase is accepted as a fallback, but snake_case is canonical.
 
 ## Related
 

package/skills/apex-journeys/SKILL.md

@@ -158,6 +158,14 @@ If the answer involves a wait, the real question is "what should stop this from
 - **branch.condition**: A step that routes execution based on a predicate over subject attributes (e.g., `cart.itemCount >= 2`).
 - **Send-time gate**: The authoritative re-check that runs immediately before any send step.
 
+## Parameter casing
+
+All Apex tool parameters are **snake_case** (`journey_id`, `trigger_contract_id`,
+`rule_id`, `when_true_comm_id`, `field_path`) — the same convention as event
+names and traits. Discover trigger-contract ids with `list_trigger_contracts`
+before calling `set_journey_trigger`. (camelCase is also accepted as a fallback,
+but snake_case is canonical and what the schemas advertise.)
+
 ## Resources
 
 - `apex://journeys` — current journeys list with exit-rule counts (if available as an MCP resource)