chore(deps): bump @contentrain/mcp from 2.1.0 to 2.1.1 in the contentrain group

[dependabot]

Bumps the contentrain group with 1 update: @contentrain/mcp.

Updates @contentrain/mcp from 2.1.0 to 2.1.1

Release notes

Sourced from @​contentrain/mcp's releases.

@​contentrain/mcp@​2.1.1

Patch Changes

• c189b6f: fix(mcp): stop DEFAULT_INSTRUCTIONS advertising a universal dry_run

  The MCP server instructions told every client to "preview writes with dry_run:true, then re-run with dry_run:false" — but dry_run exists only on contentrain_apply. On every other write tool the unknown key is stripped by the schema, so an agent following the instructions performed a real write while believing it had previewed. The instructions now state the actual safety model: writes land on isolated cr/* branches, content_save validates before committing, destructive tools require confirm:true, and dry_run is the contentrain_apply preview. Still under the 512-character client-UI budget; no tool behavior changes.

Changelog

Sourced from @​contentrain/mcp's changelog.

2.1.1

Patch Changes

• c189b6f: fix(mcp): stop DEFAULT_INSTRUCTIONS advertising a universal dry_run

  The MCP server instructions told every client to "preview writes with dry_run:true, then re-run with dry_run:false" — but dry_run exists only on contentrain_apply. On every other write tool the unknown key is stripped by the schema, so an agent following the instructions performed a real write while believing it had previewed. The instructions now state the actual safety model: writes land on isolated cr/* branches, content_save validates before committing, destructive tools require confirm:true, and dry_run is the contentrain_apply preview. Still under the 512-character client-UI budget; no tool behavior changes.

Commits

• 7dce11a chore(release): version packages
• c189b6f fix(mcp): stop DEFAULT_INSTRUCTIONS advertising a universal dry_run
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions