docs(dometrain): note the expected /plugin shadow warning - #5210
Closed
kyle-sexton wants to merge 1 commit into
Closed
kyle-sexton wants to merge 1 commit into
kyle-sexton wants to merge 1 commit into
Conversation
With a user-scope dometrain server at the plugin's URL, Claude Code skips the plugin's server as a duplicate and /plugin shows a warning. Document that it is expected, harmless, and how to silence it. Bump to 0.4.2. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H4pw3AKPP9sNePN5qwf9jL
Contributor
|
PR body contract — issue linkage This PR body does not yet satisfy the issue-linkage contract:
Edit the body and this comment updates itself on the next run. |
kyle-sexton
added a commit
that referenced
this pull request
Sep 29, 2026
Refs #5209 ## Summary Implements option 4 of #5209. `dometrain` becomes skills only (grounding, setup, sync) at 0.5.0. The bundled HTTP server (`https://mcp.dometrain.com/mcp`) and the `dometrain_api_key` option move to a new plugin, `dometrain-mcp` 0.1.0 (optional, sensitive key; `defaultEnabled: false`). - A user with their own user-scope `dometrain` server installs `dometrain` only: no plugin server at the same endpoint, so no duplicate-server warning. - A user with no server installs `dometrain` and `dometrain-mcp` and keeps the zero-setup path. - `grounding` and `setup` accept `mcp__plugin_dometrain-mcp_dometrain__*` (plugin) and `mcp__dometrain__*` (user-scope). With neither present, `setup` names both supported setups. The prefix keeps the hyphen, as the live tool list shows for `dotnet-msbuild` (`mcp__plugin_dotnet-msbuild_binlog__*`). - The env-var and `vault-exec` override recipes moved to the `dometrain-mcp` README and now mean "skip `dometrain-mcp`". - Registered in `marketplace.json`, `docs/catalog.md` (generated), and `.claude/settings.json` `enabledPlugins` (`false`, matching `animation`). `docs/cloud-sessions.md` names `dometrain-mcp` as the plugin holding the key. ## Migration impact for existing `dometrain` users - Bundled-server users: install `dometrain-mcp` and enter the key again there. Claude Code does not carry `pluginConfigs` between plugins. Until then the skills report no server. - User-scope server users: no change; updating removes the plugin server, which was the source of the warning. - Permission rules on `mcp__plugin_dometrain_dometrain__*` need `mcp__plugin_dometrain-mcp_dometrain__*`. - The `dometrain` changelog and README ("Upgrading from 0.4.x") say this. ## Verification Run in the worktree, all passing: - `scripts/validate-plugins.sh` (all manifests plus strict catalog) - `scripts/validate-plugin-contracts.mjs` (58 setup skills checked) - `scripts/check-plugin-catalog-enablement.sh --check` (failed before the `enabledPlugins` key, passes after) - `scripts/check-changelog-parity.sh --check`, `--check-bump origin/main`, `--check-order` - `scripts/check-plugin-manifest-presence.sh --check` - `scripts/generate-catalog.mjs --check`, `scripts/sync-plugin-options-docs.py --check`, `scripts/generate-cheatsheet.mjs` (unchanged) - `scripts/check-skill-count-claims.sh` (0 mismatched), `scripts/check-purged-em-dashes.sh` (none) - `markdownlint-cli2` on the touched markdown (0 issues) - skill-quality `check-skill.sh plugins/dometrain/skills` (3 pass, 0 errors; warnings only) and `check-evals-quality.sh` on the setup evals ## Not verified - The `/plugin` menu behavior was not tested live: that no warning appears with `dometrain` only plus a user-scope server, and that `dometrain-mcp` plus a user-scope server still warns. Both follow from the documented endpoint matching in the #5209 comment. - Evals were validated for shape only, not run against a model. - `docs/architecture/landscape.json` was not regenerated; the animation add did not touch it either. ## Conflict note Draft #5210 edits the old `dometrain` README and will conflict with this branch. Its branch is untouched. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01H4pw3AKPP9sNePN5qwf9jL --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Author
|
Closing as superseded by #5213 (merged). The split moves the override recipes and the bundled server into dometrain-mcp, which rewrites the README this PR edits, so the shadow-warning note no longer applies to the dometrain plugin. |
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.
Refs #5209
Summary
dometrainserver at the plugin's URL,/pluginshows a "skipped, same command/URL" warning for the plugin. It states the text, that it is expected and harmless, that the user-scope server is the one in use, and how to silence it. The message text is stated as observed behaviour, not documented by Claude Code.dometrain0.4.1 -> 0.4.2 with a CHANGELOG entry (main already carried 0.4.1)./dometrain:setupskill not changed: it reports connectivity and tool prefix, not the/pluginwarning.Verification
scripts/check-changelog-parity.sh --check,--check-bump origin/main,--check-preserved origin/main: all pass.markdownlint-cli2on the README and CHANGELOG: 0 issues.🤖 Generated with Claude Code
https://claude.ai/code/session_01H4pw3AKPP9sNePN5qwf9jL