feat(wizard): pull provider context packs via get_context_pack - #62
Merged
Conversation
The wizard consumed the context-mill's example-apps but never its context-packs. Extend the integration agent's system prompt (buildSystemAppend) to call mcp__seam-docs__list_context_packs + get_context_pack for a targeted provider, so runs benefit from the per-provider SKILL.md guidance the MCP already serves. Gated to JavaScript/Python (the only SDKs the mill compiles packs for — none for ruby/php), and phrased to fetch a pack only when a specific provider is in play (a Connect Webview defers the provider choice, so generic guidance applies then). This also makes context-mill/ARCHITECTURE.md's "wizard run" diagram — which already showed get_context_pack — accurate. Closes ENG-2939.
itelo
force-pushed
the
itelo/eng-2939-wire-get-context-pack
branch
from
August 25, 2026 14:25
babc9c9 to
388b7da
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The wizard used the context-mill's example-apps (
get_example_app) but never its context-packs — the per-(provider, SDK) SKILL.md guidance the MCP already builds and serves (list_context_packs/get_context_pack). This wires them in.src/lib/steps/integrate.tsbuildSystemAppendnow instructs the agent to callmcp__seam-docs__list_context_packs→get_context_packfor a targeted provider, alongside the existing example-app instruction.Design decisions (from ENG-2939)
Resolved against the real tool contract (
get_context_packrequiresprovider+sdk; packs exist only forjavascript/python):get_context_packcalls there.ARCHITECTURE drift
seam-aicontext-mill/ARCHITECTURE.md's "A wizard run" diagram already showed the wizard callingget_context_pack({ provider, sdk })— the shipped wizard didn't. This wiring makes the diagram accurate, so no doc edit is needed.Testing
npm run lintcleannpm run typecheckcleannpm test— 170 passedPrompt-only change (the
buildSystemAppendbuilder is private and untested, same as the existingget_example_appwiring). Verified the context-pack lines are added for js/python and omitted for ruby/php by construction (SDK-gated spread).Security & Compliance
🤖 Generated with Claude Code