fix: describe how the content is actually consumed

The overview claimed the content is consumed by "any MCP-capable client".
There is no MCP server in this repository and never has been: Cursor and
Claude Code read the files directly from a checkout. The line promised a
capability that does not exist, which is a defect rather than a wording
preference — a reader evaluating the project would go looking for a server
to register.

Describe the real mechanism instead: Cursor applies rules/*.mdc by scope
glob and takes skills by name; Claude Code reads skills/ and rules/ from the
workspace or a referenced checkout; any agent that can read workspace files
works the same way.

`pages.yml` also path-filters on a `mcp-tools.json` that has never existed in
this repository's history — it comes from the shared fleet site builder,
which supports tool repos that do ship an MCP server. Filed separately rather
than edited here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>

Author: TMHSDigital

README.md

@@ -39,7 +39,7 @@
 
 This repository ships **16 skills, 9 rules, 3 templates, 27 snippets, 59 examples, and 26 showcase pieces** for Blender Python development targeting Blender 5.2 LTS (current stable) with Blender 4.5 LTS fallback support. Blender 5.1 is prior stable.
 
-The content is consumed by AI coding agents (Cursor, Claude Code, any MCP-capable client) when working on Blender add-ons, geometry nodes scripts, batch pipelines, or animation tooling. There is no build step. Edit the markdown and Python files directly.
+The content is consumed by AI coding agents reading these files directly from a checkout — **there is no MCP server in this repository, and none is required**. Cursor applies `rules/*.mdc` automatically wherever their scope globs match and takes skills by name in chat; Claude Code reads `skills/` and `rules/` from the project workspace, or from this repo kept as a referenced checkout. Any agent that can read files in a workspace can use it the same way. There is no build step for the content — edit the Markdown and Python files directly.
 
 | Layer | Role |
 | --- | --- |