…he Test Management capabilities

Core-tool prompt examples and each named-tool product group fold into
<details> blocks. A third layer lists the 198 Test Management
capabilities the core tools reach, grouped by entity with mode and
intent, taken from the live catalog.

… one flat list

Product feedback on #463: the catalog tools should not be split into
per-entity sections with read/write counts, and should not sit at the
same level as the legacy tools.

The Tools section now reads Tools › Products › Test Management, where
Test Management is a single expandable block listing all 198 tools
alphabetically at one level. Entity groups, per-group counts and the
read/write tallies are gone. Tools now comes before Legacy Tools, and
the intro and README link text follow the new order. More products can
be added as sibling expandable blocks under Products.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…section

The five core tools and the product tools they reach are one surface,
documented by the same public docs pages, so a separate Tools layer
duplicated Core Tools. Products now sits inside Core Tools as a
sub-section, leaving two layers: Core Tools (with Products nested) and
Legacy Tools. The intro follows; the README link text already fits.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…plit

Product feedback on #463 (Slack): do not separate or count legacy tools;
list all tools together by product, the way the BrowserStack docs do.

docs/TOOLS.md is now a single Tools section with one expandable block
per product (Core tools, Test Management, Automate, App Automate, Live,
App Live, Accessibility, Percy, Test Reporting & Analytics, AI Agents).
Each block is one table of Tool / What it does / Example prompt, with
the directly registered camelCase tools and the catalog snake_case tools
for that product side by side. The intro explains the two naming styles
in one paragraph. The README link no longer mentions a tool count.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…e core tools in the intro

Product feedback on #463: product tables keep only Tool and What it
does. The expandable Core tools block is gone; the intro now names the
five core tools, shows the search → describe → invoke flow and links the
docs page. Product blocks are unchanged otherwise. README link text no
longer mentions example prompts.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Resolve the README conflict: main edited the old 51-tool list to cover
Load Testing, and this branch removes that list in favour of the Core
Tools section and docs/TOOLS.md. Keep the removal; keep main's new Load
Testing usage-examples section and point its link at Core Tools instead
of the removed Capability Registry heading. Add the 21 Load Testing
catalog tools from capability/loadtesting.capability-index.json to
docs/TOOLS.md as a product block.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…e version notes

The install buttons and the Node >= 20.9 note appeared at the top of
the README and again under Installation (the Node note a third time
inside the setup steps). Keep the top block; Installation now lists the
prerequisites and points back to it, and the setup steps are renumbered.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>