carto-md 2.1.0 → 2.1.1

package/docs/anci/v0.1-DRAFT.md

@@ -91,11 +91,25 @@ implementations only emit/parse the strict subset.
 ```yaml
 anci:
   version: "0.1.0-DRAFT"            # required, string
-  generator: "carto-md@2.0.9"       # required, string
+  generator: "carto-md@2.1.0"       # required, string
   generated_at: "2026-06-07T..."    # required, ISO-8601 UTC
+  carto_version: "2.1.0"            # required, bare producer version
+  contains:                         # required, capability list (≥1 entry)
+    - "structural"
   body:
     file: "anci.bin"                # required, relative to header
     bytes: 12345                    # required, body length on disk
+    content_digest: "sha256:9f86…"  # optional, hash of the body bytes
+
+source:                             # required block; fields null if non-git
+  commit: "a4334a2c…"               # git HEAD commit SHA, or null
+  tree_hash: "e7d3f1…"              # git HEAD tree hash, or null
+  branch: "main"                    # current branch, or null (detached)
+
+grammar_versions:                   # optional; { pkg: version }
+  tree-sitter: "0.25.0"
+  tree-sitter-javascript: "0.25.0"
+  tree-sitter-typescript: "0.23.2"
 
 project:
   total_files: 7567                 # required
@@ -130,6 +144,32 @@ Field names are stable for the v0.x line. Adding new optional fields is
 not a breaking change. Removing or renaming a field IS breaking and
 requires a version bump.
 
+### 4.1.1 Container identity (v0.1)
+
+The identity fields turn ANCI from "a folder" into a versioned,
+verifiable artifact:
+
+| Field                       | Meaning                                                              |
+|-----------------------------|----------------------------------------------------------------------|
+| `anci.carto_version`        | Bare producer version (distinct from the free-form `generator`).     |
+| `anci.contains`             | Capability list — which memory layers the container carries. v0.1 producers emit `["structural"]` (the import graph, domains, routes, models). Episodic/temporal/semantic/procedural layers are **not** in the file; they remain live in the producing engine. |
+| `anci.body.content_digest`  | `"<algorithm>:<hex>"` hash of the exact `anci.bin` bytes. Optional but recommended. Consumers recompute it to verify integrity. |
+| `source.commit`             | Git commit the container was built from, or `null` (non-git repo).   |
+| `source.tree_hash`          | Git tree hash of that commit — identifies exact committed content.   |
+| `source.branch`             | Branch name at build time, or `null` (detached HEAD / non-git).      |
+| `grammar_versions`          | Map of tree-sitter core + grammar package versions used to extract. Enables reproducibility checks (same repo + same grammars → same digest). |
+
+**Consumer integrity check.** A consumer that reads `content_digest`
+SHOULD recompute `<algorithm>(anci.bin)` and compare. On mismatch it
+SHOULD warn; a strict consumer MAY refuse to load. The reference
+consumer (`loadAnci`) exposes `reader.verifyDigest()` and a
+`{ verify: true }` option that promotes a mismatch to a thrown error.
+
+**Staleness.** `source.commit`/`source.tree_hash` let a consumer detect
+that the container was built from an older repo state than the current
+`HEAD` (e.g. "graph is N commits stale — results may be inaccurate").
+The reference engine surfaces this in MCP responses and `carto doctor`.
+
 ### 4.2 Versioning
 
 | Field           | Meaning                                                   |
@@ -258,7 +298,12 @@ sequential read.
 
 Producers SHOULD compute the body as follows:
 
-1. Assign each file a stable, dense integer id.
+1. Assign each file a stable, dense integer id. For **reproducibility**
+   (CT-4), ids MUST be assigned over the file list sorted by normalized
+   POSIX path (forward slashes, code-unit order — never a locale-aware
+   comparison), NOT over the filesystem enumeration order. This makes the
+   body layout, and therefore `content_digest`, identical across machines
+   for the same repo. See §16.2.
 2. For each file, build a bitmap of its forward imports (resolved
    imports only; unresolved imports are excluded).
 3. Reverse the forward bitmaps into `reverse`.
@@ -418,3 +463,88 @@ reachability bitmaps (2013), and Lucene's Roaring posting lists (2014).
 
 The spec is iterated alongside carto-md. File issues at
 https://github.com/theanshsonkar/carto for proposed changes.
+
+## 16. Single-file container envelope (`.anci`) — CT-3
+
+The two-file layout of §3 (`anci.yaml` + `anci.bin`) is the on-disk form.
+For **transport** — handing a container from one machine to another —
+`carto export` packs both files into ONE portable file, conventionally
+`project.anci`, and `carto load` unpacks it back into a queryable
+`.carto/` with **no re-index**. This makes "build once, load anywhere"
+literal: build on machine A, copy `project.anci`, `carto load` it on
+machine B, and blast radius answers instantly against the container A
+produced.
+
+### 16.1 Envelope wire format (little-endian)
+
+```
+magic        u32  = 0x50434E41   ("ANCP" — 'A','N','C','P' little-endian)
+version      u8   = 1
+reserved     u8×3 = 0
+entry_count  u32
+entry_count × {
+  name_len   u32
+  name       name_len UTF-8 bytes     # a bare basename (see 16.3)
+  data_len   u32
+  data       data_len bytes
+}
+trailer      32 bytes = sha256(all preceding bytes)
+```
+
+The envelope has its **own magic** (`ANCP`), distinct from the ANCI body
+magic (`ANCI` = `0x49434E41`) and carto-md's internal bitmap cache
+(`CBRT`). A consumer MUST NOT attempt to load one as another. A v0.1
+container carries exactly two entries — `anci.yaml` and `anci.bin` — in
+name-sorted order.
+
+### 16.2 Reproducibility
+
+Entries are written in a fixed (name-sorted) order, so packing the same
+input pair twice yields a byte-identical envelope. Note that `anci.yaml`
+embeds a `generated_at` timestamp, so the *envelope file* is only
+byte-stable for a fixed input pair. The **reproducible identity** of a
+container is its `anci.bin` `content_digest` (§4.1.1), which the envelope
+carries verbatim inside the packed `anci.yaml`.
+
+`anci.bin` itself is reproducible: **the same repo + the same grammar
+versions produce the same `content_digest`, independent of the machine or
+filesystem.** This holds because the producer assigns file ids over a
+list sorted by normalized POSIX path (not filesystem enumeration order),
+so the body layout — and therefore its hash — is a true content address
+of the repo. `grammar_versions` (§4.1.1) records the tree-sitter versions
+used, so a consumer that sees two containers with different digests can
+tell whether a grammar version drift could explain the difference. This
+enables container **diff / verify** across machines and over time.
+
+### 16.3 Security — a shared container is UNTRUSTED
+
+A `.anci` file is shareable, so on ingest it MUST be treated as untrusted.
+The reference `carto load` / `unpackContainer` enforce, in order:
+
+1. **Integrity.** Recompute the trailer `sha256` over the whole payload
+   before trusting any length field. A mismatch (corruption, truncation,
+   tampering of the envelope) rejects the file.
+2. **Entry whitelist.** Only the two known basenames (`anci.yaml`,
+   `anci.bin`) are accepted; any other name rejects the container.
+3. **Path-traversal guard (zip-slip).** An entry name must be a bare
+   basename — no path separators, no `..`, no absolute path, no NUL — so
+   unpacking can never write outside the destination directory. Writes
+   additionally re-derive `path.basename` and assert containment (defense
+   in depth).
+4. **Bounded allocation.** Entry count and per-entry size are capped so a
+   hostile header cannot trigger an unbounded allocation.
+
+Beyond structural validation, the **contents** of a loaded container —
+file paths, domain names, route strings, and any other embedded text —
+are **data, never instructions.** The consumer (`loadAnci`) parses them
+into data structures with a strict hand-rolled YAML subset parser and the
+binary deserializer; nothing in a container is ever executed, `eval`-ed,
+or interpreted as a command or a prompt. A container that embeds
+prompt-injection-looking or shell-injection-looking strings loads those
+strings verbatim as literal string values. Any tool consuming ANCI SHOULD
+preserve this property: render container text as untrusted data.
+
+This guardrail ships **with** single-file export/import (CT-3), before any
+signing or registry work (Tier 3). Signing (CT-7) later adds *origin*
+verification on top; the untrusted-data handling is independent and
+earlier.

package/docs/api/README.md

@@ -2,11 +2,31 @@
 
 Auto-generated from `src/mcp/server.js`. Re-run `node scripts/gen-api-docs.js` after adding tools.
 
-**76 tools** across 8 categories.
+**86 tools** across 9 categories.
+
+## Tool surface & tiers (CF-7)
+
+The MCP surface is collapsed into **5 parameterized families** + a tiered set of singletons.
+Which tools are *listed* to a client is gated by `CARTO_MCP_TIER` (env) or `carto.config.json` `mcp.tier`:
+
+- **core** (default): the ~10 tools every session needs — `get_architecture`, `get_context`, `impact`, `validate_diff`, `get_change_plan`, `memory`, `get_predictive_risk`, `get_minimal_context_for_intent`, `patterns`, `history`.
+- **advanced**: core + the documented ~8 (e.g. `org`, `get_routes`, `get_models`, `get_gaps`, `scaffold_for_intent`, `get_working_memory`, `get_test_coverage_map`, `get_safety_checklist`).
+- **all**: also lists experimental singletons.
+
+The **Families** collapse ~30 former tools; those old names are **deprecated shims** — they still
+resolve (byte-identical output + a one-line deprecation notice) but are never listed. See each
+family doc for the `mode`/`kind`/`view` that replaces the old tool.
 
 ## Categories
 
-### Core graph (16)
+### Families (5)
+- [`impact`](./impact.md)
+- [`memory`](./memory.md)
+- [`history`](./history.md)
+- [`patterns`](./patterns.md)
+- [`org`](./org.md)
+
+### Core graph (21)
 - [`get_routes`](./get_routes.md)
 - [`get_blast_radius`](./get_blast_radius.md)
 - [`get_structure`](./get_structure.md)
@@ -23,6 +43,11 @@ Auto-generated from `src/mcp/server.js`. Re-run `node scripts/gen-api-docs.js` a
 - [`get_change_plan`](./get_change_plan.md)
 - [`get_similar_patterns`](./get_similar_patterns.md)
 - [`simulate_change_impact`](./simulate_change_impact.md)
+- [`get_gaps`](./get_gaps.md)
+- [`dismiss_gap`](./dismiss_gap.md)
+- [`set_intent`](./set_intent.md)
+- [`get_intent`](./get_intent.md)
+- [`get_file_receipts`](./get_file_receipts.md)
 
 ### Episodic Memory (5)
 - [`validate_diff`](./validate_diff.md)

package/docs/api/did_we_discuss_this.md

@@ -1,5 +1,7 @@
 # `did_we_discuss_this`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(query, kind="search")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Substring search over the episodic memory log (decisions + interventions) for prior discussions of a topic. Use to avoid re-deciding settled questions.
 
 ## Input schema

package/docs/api/dismiss_gap.md

@@ -0,0 +1,39 @@
+# `dismiss_gap`
+
+Mark a specific gap as intentional. Writes the dismissal to the gaps table so the same gap does not re-surface on the next run. Idempotent — re-dismissing updates the reason. Only call this when the user explicitly says the gap is intentional; never dismiss on your own judgment.
+
+## Input schema
+
+```json
+{
+  "type": "object",
+  "properties": {
+    "gap_hash": {
+      "type": "string",
+      "description": "The gap_hash from get_gaps output."
+    },
+    "reason": {
+      "type": "string",
+      "description": "Short explanation of why this gap is intentional. Optional but strongly encouraged."
+    }
+  },
+  "required": [
+    "gap_hash"
+  ]
+}
+```
+
+## Required arguments
+
+- `gap_hash`
+
+## Properties
+
+| Name | Type | Description |
+|------|------|-------------|
+| `gap_hash` | string | The gap_hash from get_gaps output. |
+| `reason` | string | Short explanation of why this gap is intentional. Optional but strongly encouraged. |
+
+## See also
+
+- [Index of all MCP tools](./README.md)

package/docs/api/find_consumers_of_api.md

@@ -1,5 +1,7 @@
 # `find_consumers_of_api`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="consumers")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Across all org repos, find every file importing a given npm/pypi/go/maven target.
 
 ## Input schema

package/docs/api/get_action_patterns.md

@@ -1,5 +1,7 @@
 # `get_action_patterns`
 
+> ⚠️ **Deprecated (CF-7).** Use `patterns(kind="actions")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Procedural patterns mined from git history: "when developers add X, they also touch Y". Filter by natural-language intent.
 
 ## Input schema

package/docs/api/get_arch_events.md

@@ -1,5 +1,7 @@
 # `get_arch_events`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="events")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Architectural events (domain split, merge, growth, hotspot emergence). Severity filter: minor | major | critical.
 
 ## Input schema

package/docs/api/get_architectural_drift.md

@@ -1,5 +1,7 @@
 # `get_architectural_drift`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="drift")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Per-domain growth/shrink and event count over a time window. Run `carto temporal init` first to backfill from git history.
 
 ## Input schema

package/docs/api/get_blast_radius.md

@@ -1,5 +1,7 @@
 # `get_blast_radius`
 
+> ⚠️ **Deprecated (CF-7).** Use `impact(file, mode="blast")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Get all files, routes, and domains affected by changing a specific file. Includes risk level per route.
 
 ## Input schema

package/docs/api/get_canonical_pattern.md

@@ -1,5 +1,7 @@
 # `get_canonical_pattern`
 
+> ⚠️ **Deprecated (CF-7).** Use `patterns(kind="canonical")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Highest-quality example of a pattern in the codebase (e.g. canonical route handler). Use as a copy-paste template before writing similar code.
 
 ## Input schema

package/docs/api/get_change_velocity.md

@@ -1,5 +1,7 @@
 # `get_change_velocity`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="velocity")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Commits-per-day over a window (requires temporal store). Useful for spotting development tempo shifts.
 
 ## Input schema

package/docs/api/get_churn_vs_blast_radius.md

@@ -1,5 +1,7 @@
 # `get_churn_vs_blast_radius`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="churn")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Scatter data of churn vs blast_radius for every changed file in a window. Use to find risk hotspots.
 
 ## Input schema

package/docs/api/get_complexity_trend.md

@@ -1,5 +1,7 @@
 # `get_complexity_trend`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="complexity")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 A single file's presence across snapshots + commit count + current blast_radius. Use to track how a file's footprint evolved.
 
 ## Input schema

package/docs/api/get_conventions.md

@@ -1,5 +1,7 @@
 # `get_conventions`
 
+> ⚠️ **Deprecated (CF-7).** Use `patterns(kind="conventions")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Naming + export + directory conventions that apply to a given file or directory. Confidence-scored. Use before writing new code in this location.
 
 ## Input schema

package/docs/api/get_cross_repo_blast_radius.md

@@ -1,5 +1,7 @@
 # `get_cross_repo_blast_radius`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="blast")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Direct downstream consumers of a producer repo. "If I break repo X, who notices?"
 
 ## Input schema

package/docs/api/get_data_flow.md

@@ -1,5 +1,7 @@
 # `get_data_flow`
 
+> ⚠️ **Deprecated (CF-7).** Use `impact(file, mode="data_flow")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Per-file data-flow snapshot: upstream imports + downstream importers + routes + models + env vars in the file. The AI-friendly view, not full taint analysis.
 
 ## Input schema

package/docs/api/get_decision_log.md

@@ -1,5 +1,7 @@
 # `get_decision_log`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(kind="log")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Recent decisions from the episodic-memory log, optionally annotated with concurrent architectural events from the temporal store.
 
 ## Input schema

package/docs/api/get_domain_evolution.md

@@ -1,5 +1,7 @@
 # `get_domain_evolution`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="evolution")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Time-series of a single domain's file count, by snapshot. Use to chart a domain's growth over the last quarter.
 
 ## Input schema

package/docs/api/get_domain_health.md

@@ -1,5 +1,7 @@
 # `get_domain_health`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="health")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Per-domain growth rate, instability, recent events, and hotspot files. Use to spot domains drifting out of bounds.
 
 ## Input schema

package/docs/api/get_file_receipts.md

@@ -0,0 +1,34 @@
+# `get_file_receipts`
+
+For one file, returns receipts — everything Carto knows: change history, blast radius, prior interventions and decisions touching this file, active gaps on this file, cross-domain deps. Read-only. Use before proposing a change to a file to understand what depends on it and what has been said about it before.
+
+## Input schema
+
+```json
+{
+  "type": "object",
+  "properties": {
+    "file": {
+      "type": "string",
+      "description": "Relative file path from project root."
+    }
+  },
+  "required": [
+    "file"
+  ]
+}
+```
+
+## Required arguments
+
+- `file`
+
+## Properties
+
+| Name | Type | Description |
+|------|------|-------------|
+| `file` | string | Relative file path from project root. |
+
+## See also
+
+- [Index of all MCP tools](./README.md)

package/docs/api/get_gaps.md

@@ -0,0 +1,52 @@
+# `get_gaps`
+
+The current gap list for this repo — grounded findings from the rule engine ("SHOULD − IS"). Each gap ties to a file + rule_id + evidence. Ranked HIGH > MEDIUM > LOW. Dismissed gaps are excluded by default. Call this when the user asks "what should I fix?", when you enter a new repo for the first time, or before recommending changes to a file. If the response is empty and the project is unsupported, tell the user the rule engine only ships for Next.js + Supabase SaaS-with-auth today.
+
+## Input schema
+
+```json
+{
+  "type": "object",
+  "properties": {
+    "rule_id": {
+      "type": "string",
+      "description": "Optional rule filter, e.g. \"money-as-float\"."
+    },
+    "file": {
+      "type": "string",
+      "description": "Optional file filter."
+    },
+    "severity": {
+      "type": "string",
+      "description": "Optional severity filter: HIGH | MEDIUM | LOW."
+    },
+    "include_dismissed": {
+      "type": "boolean",
+      "description": "Include gaps the user has already dismissed (default false)."
+    },
+    "refresh": {
+      "type": "boolean",
+      "description": "Re-run the rule engine before returning (default false — uses last cached run)."
+    }
+  },
+  "required": []
+}
+```
+
+## Required arguments
+
+_None._
+
+## Properties
+
+| Name | Type | Description |
+|------|------|-------------|
+| `rule_id` | string | Optional rule filter, e.g. "money-as-float". |
+| `file` | string | Optional file filter. |
+| `severity` | string | Optional severity filter: HIGH \| MEDIUM \| LOW. |
+| `include_dismissed` | boolean | Include gaps the user has already dismissed (default false). |
+| `refresh` | boolean | Re-run the rule engine before returning (default false — uses last cached run). |
+
+## See also
+
+- [Index of all MCP tools](./README.md)

package/docs/api/get_hotspot_files.md

@@ -1,5 +1,7 @@
 # `get_hotspot_files`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="hotspots")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Top files by churn × blast_radius score over a window. The CodeHealth heuristic: high-churn files in high-blast-radius positions are where bugs cluster.
 
 ## Input schema

package/docs/api/get_intent.md

@@ -0,0 +1,25 @@
+# `get_intent`
+
+Return the currently stored intent — product type, stack, notes, updated_at. Use this at the start of a session to know which rules will apply to this project.
+
+## Input schema
+
+```json
+{
+  "type": "object",
+  "properties": {},
+  "required": []
+}
+```
+
+## Required arguments
+
+_None._
+
+## Properties
+
+_None._
+
+## See also
+
+- [Index of all MCP tools](./README.md)

package/docs/api/get_intervention_history.md

@@ -1,5 +1,7 @@
 # `get_intervention_history`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(kind="interventions")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 List interventions (Carto-issued violations and suggestions) optionally filtered by file. Use to see prior warnings on a file before editing it.
 
 ## Input schema

package/docs/api/get_invariants.md

@@ -1,5 +1,7 @@
 # `get_invariants`
 
+> ⚠️ **Deprecated (CF-7).** Use `patterns(kind="invariants")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Architectural invariants mined from the import graph: "Domain X never imports from Y", "Files in Z always export N symbols", etc. Confidence-scored.
 
 ## Input schema

package/docs/api/get_microservices_migration_cut_points.md

@@ -1,5 +1,7 @@
 # `get_microservices_migration_cut_points`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="migration")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Suggested microservices extraction order. Repos with high stability (more incoming than outgoing edges) extract first.
 
 ## Input schema

package/docs/api/get_neighbors.md

@@ -1,5 +1,7 @@
 # `get_neighbors`
 
+> ⚠️ **Deprecated (CF-7).** Use `impact(file, mode="neighbors")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Get import graph neighbors of a file — files it imports and files that import it. Returns nodes and edges for visualization.
 
 ## Input schema

package/docs/api/get_org_architecture.md

@@ -1,5 +1,7 @@
 # `get_org_architecture`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="architecture")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Org-wide summary: registered repos + total cross-repo edge count + edges by kind. Requires `carto org init` + `carto org sync`.
 
 ## Input schema

package/docs/api/get_org_domain_mapping.md

@@ -1,5 +1,7 @@
 # `get_org_domain_mapping`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="domains")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Per-repo domain list across all org repos (reads each repo's carto.db if registered).
 
 ## Input schema

package/docs/api/get_pending_decisions.md

@@ -1,5 +1,7 @@
 # `get_pending_decisions`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(kind="pending")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Recent decisions with pending/unresolved/HIGH-risk flags in their payload. Surfaces unfinished AI work from the episodic log.
 
 ## Input schema

package/docs/api/get_recent_decisions.md

@@ -1,5 +1,7 @@
 # `get_recent_decisions`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(kind="recent")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 List recent validation decisions and architectural choices the AI has made in this project. Returns time-descending rows.
 
 ## Input schema

package/docs/api/get_service_boundary_violations.md

@@ -1,5 +1,7 @@
 # `get_service_boundary_violations`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="violations")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Cross-repo edges that import private/internal surface (heuristic: target path contains internal / private / _lib).
 
 ## Input schema

package/docs/api/get_service_dependency_graph.md

@@ -1,5 +1,7 @@
 # `get_service_dependency_graph`
 
+> ⚠️ **Deprecated (CF-7).** Use `org(view="graph")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Aggregated cross-repo graph: each repo is a node, edges grouped by (from_repo, to_repo, edge_kind).
 
 ## Input schema

package/docs/api/get_session_context.md

@@ -1,5 +1,7 @@
 # `get_session_context`
 
+> ⚠️ **Deprecated (CF-7).** Use `memory(kind="session")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 Full context for an AI session: every decision and every intervention, ordered chronologically. Use to recap what happened in a long-running session.
 
 ## Input schema

package/docs/api/get_temporal_context.md

@@ -1,5 +1,7 @@
 # `get_temporal_context`
 
+> ⚠️ **Deprecated (CF-7).** Use `history(view="file")` instead. This name still resolves and returns byte-identical output for a deprecation window, but is no longer listed by default and emits a one-line notice.
+
 A file's full temporal context: first_seen_ts, last_modified_ts, commit_count, blast_radius, recent events, age in days.
 
 ## Input schema