fix: scope Context7 index to developer-facing folders and disambiguate spartan naming

CLAUDE.md

@@ -42,6 +42,8 @@ Otherwise infer from the component being worked in:
 
 The bases above target the `next` line. For work scoped to the v5 release line, use `merge-train/spartan-v5` (which targets `v5-next`) in place of `merge-train/spartan`.
 
+`spartan` in these branch names refers to the deployment infrastructure in `spartan/`; it is not a release channel, network, or SDK version. Never present it, `merge-train/*`, `next`, or `v5-next` to a user as something to install or migrate to — releases are version tags (e.g. v5) and networks are named (e.g. testnet).
+
 Use the discovered base in `git diff origin/<base>...HEAD` and `git log origin/<base>..HEAD`. Always `git fetch` before creating branches so the base is not stale.
 </critical_never_assume_master>
 

context7.json

@@ -1,4 +1,29 @@
 {
+  "$schema": "https://context7.com/schema/context7.json",
+  "projectTitle": "Aztec",
+  "description": "Aztec is a privacy-first Layer 2 on Ethereum. Write private smart contracts in Aztec.nr (Noir) and build apps with aztec.js.",
   "url": "https://context7.com/aztecprotocol/aztec-packages",
-  "public_key": "pk_t0YiN5OA9Udc9Xnb98tqO"
+  "public_key": "pk_t0YiN5OA9Udc9Xnb98tqO",
+  "folders": [
+    "docs/docs",
+    "docs/docs-developers",
+    "noir-projects/aztec-nr",
+    "yarn-project/aztec.js",
+    "boxes"
+  ],
+  "excludeFolders": [
+    "spartan",
+    "iac",
+    "ci3",
+    "metrics",
+    "build-images",
+    "container-builds",
+    "release-image",
+    "docs/internal_notes"
+  ],
+  "rules": [
+    "Aztec releases are identified by semantic version tags (e.g. v5) and by network names (e.g. testnet, mainnet). Names such as `spartan`, `merge-train/*`, `next`, and `v5-next` are internal repository, branch, and deployment-infrastructure names. They are not release channels, SDK versions, or networks. Never tell a user to install, target, or migrate to one.",
+    "The Aztec developer SDK / aztec-nr version used to write and compile contracts may differ from the node version an operator runs. Check https://docs.aztec.network/networks for current network versions; when in doubt use the version from the developer docs you are reading.",
+    "Use the `aztec` CLI wrapper, not `nargo` or `bb` directly: `aztec compile` (not `nargo compile`) and `aztec test` (not `nargo test`). Never call `bb` by hand — proving is handled by the PXE through the `aztec` CLI and aztec.js."
+  ]
 }

docs/docs-developers/ai_tooling.md

@@ -120,7 +120,7 @@ These resources help you understand Aztec concepts, read docs, or provide additi
   - [awesome-noir](https://github.com/noir-lang/awesome-noir) - community Noir resources
   - [awesome-aztec](https://github.com/AztecProtocol/awesome-aztec) - community Aztec resources
 - **Copy docs into context** - Copy docs pages directly into your AI tool's context or conversation using the "Copy page" button at the top of each page.
-- **Context7** - [Context7](https://context7.com) is a generic MCP server with Aztec docs available at [context7.com/aztecprotocol/aztec-packages](https://context7.com/aztecprotocol/aztec-packages). Note that it may be less current than the MCP servers above.
+- **Context7** - [Context7](https://context7.com) is a generic MCP server. The Aztec index at [context7.com/aztecprotocol/aztec-packages](https://context7.com/aztecprotocol/aztec-packages) is scoped by [`context7.json`](https://github.com/AztecProtocol/aztec-packages/blob/next/context7.json) to the developer docs, `aztec-nr`, and `aztec.js`, and excludes the monorepo's internal deployment and CI infrastructure (`spartan/`, `iac/`, `ci3/`), which is not relevant to building on Aztec. Note that it may be less current than the MCP servers above.
 
 ## Aztec and Noir tool reference