docs(mcp): fix MCP tool name testsprite_bootstrap_tests -> testsprite_bootstrap

[Yazan-O]

What

The MCP docs reference the bootstrap tool as testsprite_bootstrap_tests, but the tool the MCP server actually registers is testsprite_bootstrap — and its first parameter is pathname, not path. An agent or user copy-pasting the documented name/parameter gets a "tool not found" (or a silently ignored parameter).

This corrects the tool name across the six files that reference it, and fixes the path → pathname parameter in the tool reference.

Verified

Against the shipped plugin @testsprite/testsprite-mcp@0.0.39, via an MCP tools/list over stdio:

testsprite_bootstrap — params: [localPort, pathname, type, projectPath, testScope]

Files

• mcp/core/tools.mdx — accordion title, parameter name, usage example, workflow diagram
• mcp/concepts/key-terms.mdx
• mcp/core/create-tests-new-feature.mdx
• mcp/core/create-tests-new-project.mdx
• mcp/maintenance/cost-performance.mdx
• mcp/troubleshooting/application-detection-issues.mdx

Out of scope (flagged, not changed)

mcp/core/tools.mdx also lists testsprite_rerun_tests (beta) and omits testsprite_check_account_info compared to the current tools/list. Left untouched to keep this PR focused on the confirmed name/parameter drift — happy to follow up if you'd like those reconciled.

[zeshi-du]

Closing — this fix already shipped through the Docs-dev mirror, so there is nothing left for this branch to change.

testsprite_bootstrap_tests now has zero occurrences on v1.0:

git grep -c "testsprite_bootstrap_tests" prod-docs/v1.0   # no output — zero hits
git grep -c "testsprite_bootstrap_tests" Docs-dev/main     # no output — zero hits

It was corrected upstream in Docs-dev by 179d570 ("docs(mcp): align tool names with the published MCP package"), which reached this repo in one of the sync/from-docs-dev-main-* merges. The tool really is testsprite_bootstrap — that matches the name registered in testsprite-mcp-plugin's tool table, so the call you made here was the right one.

Two notes for next time, since the diagnosis was correct and only the delivery path was off:

1. This repo is a mirror. TestSprite/Docs v1.0 is overwritten from TestSprite/Docs-dev main by the periodic sync/from-docs-dev-main-* PRs, so a content fix made directly here gets silently reverted by the next sync. Content changes belong in Docs-dev; only the sync branches should land here.
2. Because the same fix arrived from upstream while this branch sat open, merging it now would be a no-op at best and a conflict at worst.

Thanks for catching it — the wrong tool name was live on the portal for a while.