Record the implementation notes in the RFC

Marks the RFC implemented and documents where v0.1.0 departed from it: the
compact list_targets default, the per-entry path in probe_batch, the indent
threshold, error keying on error.code rather than exit status, and the
permissive outputSchema.

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

Author: Garfield-yin

docs/rfc.md

@@ -2,7 +2,7 @@
 
 | | |
 |---|---|
-| **Status** | Draft |
+| **Status** | Implemented in v0.1.0 — see [Implementation notes](#16-implementation-notes) |
 | **Author** | guangfei.me@gmail.com |
 | **Created** | 2026-08-22 |
 | **Repository** | `deckflow/deckprobe-mcp-server` (standalone; engine consumed from npm) |
@@ -223,9 +223,9 @@ name:
 
 - `list_formats` — no arguments → `deckprobe formats` (drivers, profiles,
   support boundaries).
-- `list_targets` — `{ format: z.string() }` → `deckprobe targets --format
-  <fmt>` (ids, aliases, value types, selector membership, `min_level`, cost
-  class, selector expansions).
+- `list_targets` — `{ format: z.string(), detail?: "compact" | "full" }` →
+  `deckprobe targets --format <fmt>` (ids, aliases, value types, selector
+  membership, `min_level`, cost class, selector expansions).
 
 Discovery output is static per engine binary, so results are **cached
 in-process** keyed by the resolved engine version; the first call per session
@@ -447,12 +447,47 @@ teach the same vocabulary).
 - **Exposing `--strict`**: meaningless over MCP; exit codes are not the
   signaling channel, `execution.unresolved_targets` is.
 
-## 15. Open questions
-
-1. Package name/scope confirmation: `@deckflow/deckprobe-mcp` vs.
-   `@deckflow/mcp-server`. This RFC assumes the former (searchable,
-   convention-matching).
-2. Should `probe_batch` accept glob patterns server-side, or stay
-   literal-paths-only (current proposal) and let the agent expand globs?
-3. Default for `DECKPROBE_MCP_ROOTS` in *registry-listed hosted* contexts —
-   revisit when the HTTP transport lands.
+## 15. Resolved questions
+
+1. **Package name** — confirmed as `@deckflow/deckprobe-mcp`, bin
+   `deckprobe-mcp`, registry name `io.github.deckflow/deckprobe`.
+2. **Globs in `probe_batch`** — not accepted. Literal paths only; the agent
+   expands globs, which keeps the server free of a second path grammar and of
+   filesystem traversal it would then have to bound.
+3. **`DECKPROBE_MCP_ROOTS` in hosted contexts** — still open, and deferred with
+   the HTTP transport it belongs to. The variable exists and is enforced; only
+   its default in a hosted deployment is undecided.
+
+## 16. Implementation notes
+
+Where v0.1.0 departs from the proposal above, and why.
+
+- **`list_targets` returns a compact catalogue by default.** The full engine
+  report is roughly 22 KB per format — about 6k tokens — most of it per-target
+  JSON Schema fragments and fully expanded selector member lists that an agent
+  choosing a target never reads. The compact projection keeps every field
+  needed to name a target correctly at roughly a third of the size, and
+  `detail: "full"` returns the engine report verbatim. This is the one place
+  besides the batch wrapper where output is reshaped, and it is opt-out.
+- **Each `probe_batch` entry carries its requested `path`.** The engine's error
+  envelope has no `input` field, so a failed record is otherwise
+  indistinguishable from any other and correlation would rest on array position
+  alone. Entries are `{ path, report }` with the report verbatim.
+- **Text blocks are indented only below 8 KB.** Indenting a long batch or a
+  full target catalogue roughly doubles it for no gain, and `structuredContent`
+  carries the same value for anything parsing it.
+- **Errors are keyed on `error.code`, not the exit status.** Status 4 covers
+  both `MALFORMED_INPUT` and `BUDGET_EXCEEDED`, which call for opposite
+  responses; the exit status is only the fallback.
+- **Pre-engine rejections inside a batch stay per-file.** A missing path or one
+  outside the allow-list becomes an error envelope in its own entry rather than
+  failing the call, matching how the engine's JSONL mode treats a bad record.
+- **The WebAssembly fallback derives the values view itself.** The SDK has no
+  `--view` equivalent and always resolves the full report. The projection is
+  asserted equal to the CLI's own values envelope in `engine.test.ts`, so the
+  two paths cannot drift silently.
+- **`outputSchema` is declared and deliberately permissive.** The SDK skips
+  output validation on `isError` results and does not strip fields from
+  `structuredContent`, so a loose envelope schema documents the shape without
+  ever rejecting a valid report. The authoritative contract remains the
+  `deckprobe://schema` resource.