@apex-inc/mcp-server 0.28.1 → 0.30.0

package/package.json

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

package/skills/apex-adoption/SKILL.md

@@ -32,7 +32,11 @@ Do not say reminder, congratulations, clock, or watch list as names they see.
 
 ## Core idea
 
-- A Milestone is per person, per feature. Event (`report_run`) or trait (`plan = pro`).
+- A Milestone is **This person** unless they set **Anyone here**. Absent `finish_when` = This person. Existing rows stay This person until they flip them.
+- **This person** — only that person finishes. Their letters stay theirs.
+- **Anyone here** — first person on the same **Account** (`identify({ account: { id } })`) finishes it for the company. Leftover Nudges stop for the others. **Only the person who did it gets the Celebration.** Trait finishes stay This person.
+- Company facts (snippet live, SSO, billing) → Anyone here. Person skills (ran a report, invited a teammate) → This person.
+- `update_adoption_milestone` can flip a live event Milestone. Flipping to Anyone here backfills leftover Nudges for Accounts that already have a doer. A teammate who joins later inherits Done.
 - Hours or days from signup (or the anchor). `0` is right away. 1 hour is not right away.
 - New Milestones default to **from now on** (`enroll_mode: "future"`). Do not publish a short clock on everyone already here (`enroll_mode: "all"`).
 - Each Send gets its **own** Communication. Never reuse `comm-adoption-nudge` or `comm-adoption-celebration`.
@@ -57,10 +61,12 @@ Name live hosts (`list_workspace_environments` / `set_workspace_environments` or
 | `get_adoption_milestone` | Inspect one |
 | `create_adoption_milestone` | Define a Milestone (just-track unless they compose) |
 | `compose_adoption_milestone` | Create a Milestone and stamp **one** Adaptive Journey |
-| `update_adoption_milestone` | Change priority / order / hours or days / on-off |
+| `update_adoption_milestone` | Change priority / order / hours or days / on-off / `finish_when` |
 | `reorder_adoption_milestones` | Sequence for the Path funnel |
 | `delete_adoption_milestone` | Remove a Milestone |
 | `get_adoption_metrics` | Funnel + one lift number |
+| `get_adoption_user_progress` | One person's Path (Not yet / Started / Done) |
+| `get_adoption_account_progress` | One company's Path: who finished, how many are still Not yet |
 | `attach_adoption_milestone_still` | Attach Not yet or Done |
 | `list_adoption_milestone_stills` | List those two pictures |
 | `recapture_adoption_milestone_stills` | Capture from public pages on a named host |
@@ -81,7 +87,7 @@ Read-only summary: `apex://adoption`.
 
 Returns one `journey_id` (also `nudge_journey_id` for old callers) and each Send as `{ role, step_id, comm_id }`. `celebration_journey_id` is null on new rows.
 
-Params: `action_label`, `gap_hours` or `gap_days`, `nudge_clocks` (each hours or days), `save_not_yet_segment`, `save_done_segment`, `enroll_mode`.
+Params: `action_label`, `gap_hours` or `gap_days`, `nudge_clocks` (each hours or days), `save_not_yet_segment`, `save_done_segment`, `enroll_mode`, `finish_when` (`this_person` or `anyone_here`; event finishes only).
 
 Preview each Communication, then `publish_journey`. Leave the Milestone off until they confirm.
 
@@ -133,6 +139,11 @@ Only when they are not using compose:
 ### "Just track — no letter"
 1. `compose_adoption_milestone` `scaffold: "none"`.
 
+### "First person at the company finishes it for everyone"
+1. Event finish only. Pass `finish_when: "anyone_here"` on compose, or `update_adoption_milestone` on a live row.
+2. Company facts (snippet, SSO, billing) — not person skills.
+3. A flip on a live row backfills leftover Nudges. Use `get_adoption_account_progress` for the company report.
+
 ### "Save not-yet as a Segment"
 Pass `save_not_yet_segment: true` (and/or `save_done_segment`) on compose. Names: `Not yet: {name}` / `Done: {name}`. Completing drops them from not-yet. The Adaptive Journey watch list stays private if they do not check this.
 

package/skills/apex-communications/SKILL.md

@@ -86,11 +86,10 @@ you did:
 
 `in_experiment` is a hard stop, not an intent question — the content is a
 treatment mid-measurement. `edit_communication` accepts
-`confirm_live_experiment: true` to override, and that **marks the experiment
-invalid and excludes its result from the belief graph**. Never pass it on your
-own initiative. Offer the alternatives first: wait for the experiment to
-finish, or end it with `conclude_experiment` / `promote_winner` so the learning
-is captured.
+`confirm_live_experiment: true` to override, and that **marks the numbers
+untrustworthy: Apex will not call a winner and will not learn from mixed
+counts**. Never pass it on your own initiative. Offer the alternatives first:
+wait for the experiment to finish, or end it so the learning is captured.
 
 If you omit `intent` when it's needed, the server returns a 409 that names both
 options. That's a fork in the road, not a failure — read it, ask the user, and
@@ -219,6 +218,10 @@ Examples:
 
 When generating communications for a journey, **mention exit rules in the same breath**. The apex-journeys skill has the full pattern.
 
+## Sender domain is a hop
+
+`start_sender_domain` issues DNS records. That is not green. The shop pastes them at the registrar; you cannot click the registrar for them. Poll `get_sender_domain` until status is verified.
+
 ## Proactive nudge: missing exit rules
 
 When a user generates or creates a marketing journey with `wait` steps and a purchase or activation goal, proactively check whether exit rules exist:

package/skills/apex-experimentation/SKILL.md

@@ -164,6 +164,7 @@ Match Apex UI terminology in user-facing copy: e.g. **Adaptive traffic allocatio
 - Hiding the page until `/assign` returns (worse LCP; not the React-hook promise).
 - Changing variant implementation mid-flight without versioning (invalidates analysis).
 - Only using p-values without effect size or business context.
+- Shipping onto a live test. Before you edit a page, commit, or push — even if they never said experiment — call `check_live_tests` with the **full file contents**, not the diff hunk. Before you change a letter, Adaptive Journey, or Milestone, call it with `communication_ids`, `journey_ids`, or `milestone_ids`. If something live is on those files or ids, **stop and ask**. Three outs: end the test then ship; wait; or they say this change is not the thing under test (they mark that on the experiment page). Do not edit. Do not commit. Do not pass `confirmLiveExperiment` / `confirmTreatmentChange` / `confirmLiveMilestone` unless they picked an out.
 
 ## Prove incrementality — "is our growth real?"
 
@@ -190,6 +191,8 @@ Surface specifically: `create_experiment` auto-detects mobile vs web from repo s
 
 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.
 
+Shipping onto a live website, app test, letter, Adaptive Journey, or Milestone: `check_live_tests` (before edit / commit / push / publish). That is a different question from two tests on the same page.
+
 Avoiding interaction effects: two experiments on the **same surface/component** contaminate each other. `create_experiment` (preview) and `activate_experiment` auto-run a conflict check and surface an advisory; you can also call `check_experiment_conflicts` yourself. Resolve it by either (a) **mutual exclusion** — `set_experiment_mutex` so no visitor is in both (run concurrently, the scientifically clean default), or (b) **sequencing** — launch the second only after the first concludes. If two experiments share a surface AND the same primary metric, they're usually arms of ONE experiment — add a variant instead of creating a second. Pass `target_component` (e.g. "ProductCard") on create so the guard can detect overlap precisely, especially for mobile/SDK experiments.
 
 ## Related

package/skills/apex-integration-cookbook/SKILL.md

@@ -334,3 +334,14 @@ ad accounts + Stripe in their workspace; per-client spend/revenue/ROI
 and the transparent at-risk rule roll up on the agency org
 (`GET /api/agency/clients` — org owner/admin sessions only; it is a
 financial boundary with no API-key lane).
+
+## Recipe: Set up Apex from this repo
+
+If get_setup_state shows first-run incomplete, name the shop before inventing events.
+
+1. Call `get_setup_state`. If the shop has no name, no vertical, or no conversion model, stop.
+2. `update_organization` with the shop's real name. `update_workspace` with `workspace_name`, `vertical`, `conversion_model`, and `website_url` when you know them. The rail finishes from those saves — do not look for a mark-complete tool.
+3. Name Production (and optional Beta) sites with `list_workspace_environments` / `set_workspace_environments` before you trust the Production slice.
+4. Install the snippet or SDK and wire the events the shop actually fires. Do not invent event names to make a step look done.
+5. Finish writable setup with the matching tools (`claim_links_subdomain`, `set_consent_posture`, webhooks, scoring, invitations, engagement, app platforms, attribution, sender domain, push keys, protect auto-pause). Consent answers are not a live-site tap. Sender-domain records issued are not green — poll `get_sender_domain` until verified.
+6. Hop only when the next incomplete step is a hop: `start_integration_install` for GitHub, Stripe, Meta, Google, LinkedIn, or TikTok. Legal acknowledgements stay on the opened page. You cannot click the ad consoles or the DNS registrar for them.

package/skills/apex-partner-network/SKILL.md

@@ -188,4 +188,5 @@ Policies:
 
 - `apex-integration-cookbook` — end-to-end patterns combining partner network + communications + experiments
 - MCP tools: `list_partner_programs`, `create_partner_program`, `invite_partner`, `approve_payouts`, `vouch_for_partner`, `get_effective_fees`
+- Stripe Connect for the shop is a hop: `start_integration_install` with `type: "stripe"`. Legal acknowledgements stay on the opened page.
 - Docs: `/docs/partner-network/` for concept walkthroughs + integration guides