MCP Server v0.0.1-beta.17

This release improves goal safety, split-URL creation, reporting guidance, and
privacy-safe diagnostics across the local npm server and hosted connector.

Safer experience workflows

• Visits-page goals reject ignored settings.url fields before any write and
  explain the correct triggering_rule shape, including partial goal updates.
• Split-URL creation uses a no-redirect Original and a redirect treatment with
  50/50 allocation by default. Custom setups require an explicit baseline and
  allocation. Readback verifies arm identity, traffic, and the entire requested
  change set, including rejecting unexpected extra code or redirects.
• Incomplete creation verification retains the creation receipt and does not
  recommend blindly creating a duplicate experience.
• Lifecycle permission errors distinguish creating an active experience from
  starting or pausing an existing one. User confirmation does not substitute
  for backend permissions.

Clearer reporting and guidance

• Preserve engine-specific done semantics: Bayesian chance-to-win and risk,
  sequential Frequentist significance, and other Frequentist MDE/power sample
  targets. Reaching a sample target is not necessarily a significant result.
• Explain that default-like report values do not prove computation occurred;
  keep actual reported values intact rather than inventing conclusions.
• Improve project-default inheritance guidance, daily-report goal selection,
  and the deprecated minimum-conversion alias explanation.

Better operational diagnostics

• Record tool arrival as started rather than successful. Record completion
  separately and distinguish authentication, authorization, and other bounded
  failure categories.
• Include validated operation names without recording tool arguments,
  credentials, customer data, or raw upstream diagnostics.
• Add a maintained modern-protocol live smoke harness with cancellation,
  peer-listener isolation, reconnection, and verified cleanup.

Compatibility

No OAuth endpoint, grant, credential, session binding, migration, tool name,
or protocol configuration changes. Existing authenticated customers do not need
to reconnect. Clients may refresh tool descriptions on their own schedule.
Local users running npx -y @convertcom/mcp-server@latest receive the new
version on a fresh launch; already-running processes need a restart.

The stricter goal and custom split-input checks intentionally reject ambiguous
or silently ignored payloads. Existing namespace actions remain available under
the same backend permissions and confirmation guardrails.

Verification

The reviewed runtime passed 1,133 server tests, installed-package checks with
and without optional semantic dependencies, real credentialed local stdio
calls, both hosted protocol paths, and staged deployment continuity using an
already-open authenticated session. A real split-URL draft was created,
independently read back, and archived in an approved test project. Staging
goal guards and diagnostic error classes were verified against live calls.

Full evidence: staging certification.
This does not claim website-event tracking acceptance or resolve missing
backend computation-availability metadata. Notifications and directory
submissions remain separate work.