Skip to content

fix(experiment-setup): use get-contexts in place of search-contexts - #251

Draft
davidbrackbill wants to merge 1 commit into
mainfrom
experiment-setup-get-contexts
Draft

davidbrackbill wants to merge 1 commit into
mainfrom
experiment-setup-get-contexts

Conversation

@davidbrackbill

Copy link
Copy Markdown
Contributor

Why

The hosted MCP server retires search-contexts and get-context-instances in favor of get-contexts (launchdarkly/mcp PR to follow), and mcp's skill tests reject a pinned skill that names a retired tool.

Details

  • experiment-setup 0.3.2 finds stored context kinds for the randomization unit with get-contexts; its default resource: "contexts" takes the same kind and filter, so the logic is unchanged.
  • Eval tool definition (from the server's tools/list), mock, trajectory checks, and mock tests use the new name. node --test: same 93/100 as main (7 files fail to load locally on both).

Claude claude@anthropic.com

The hosted MCP server retires search-contexts and get-context-instances
in favor of get-contexts, whose default resource takes the same kind and
filter arguments.

Claude <claude@anthropic.com>
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown

Skill eval results

Skill Before After Δ
agentcontrol/configs-create 100/100 (4/4) 75/100 (3/4) -25
agentcontrol/configs-update 80/100 (4/5) 80/100 (4/5) no change
agentcontrol/configs-variations 80/100 (4/5) 80/100 (4/5) no change
agentcontrol/tools 75/100 (3/4) 75/100 (3/4) no change
aws-devops-agent/experiment-orchestration - 100/100 (9/9) new
experiments/launchdarkly-experiment-guide - 100/100 (5/5) new
experiments/launchdarkly-experiment-hypothesis-builder - 100/100 (13/13) new
experiments/launchdarkly-experiment-setup - 100/100 (8/8) new
feature-flags/flag-and-release-change - 100/100 (4/4) new
feature-flags/flag-release - 80/100 (4/5) new
feature-flags/launchdarkly-flag-command - 100/100 (3/3) new
feature-flags/launchdarkly-flag-create 100/100 (3/3) 100/100 (4/4) no change
feature-flags/launchdarkly-flag-drift - 100/100 (4/4) new
feature-flags/should-flag-change - 100/100 (17/17) new
onboarding - 100/100 (7/7) new
release-autopilot/launchdarkly-release-autopilot-onboarding - 96/100 (24/25) new

Only suites whose source actually changed since their last recorded score were re-run. Soft-failing while we stabilise the baseline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant