`req r1`

The oracle process is the CONSUMER's own `rust-analyzer` binary — the stack never bundles, links, or vendors an analyzer.

Resolution order, run from the project root so `rust-toolchain.toml` pinning is honoured, each failure recipe-carrying and never silently skipped:

Installing this stack OBLIGES the machine to carry rust-analyzer (the same posture as node ≥ 22.6 for the TS stack): inside the stack's own test suite an absent analyzer is a recipe-carrying FAILURE, never a skip; outside the stack no obligation exists — a project without rust-ai-native gets the product's not-installed recipe and owes nothing.

The resolved path and the server's reported version land in the `init` result. *Specified, not built — half of it. The version half ships: `init_result` emits `ra_version` (`crates/rust-ai-native-tcg/src/serve.rs:76-86`), beside `position_encoding`, `pull_diagnostics` and `quiescent`. The path half does not: the path IS resolved — `resolve_rust_analyzer` (`crates/rust-ai-native-tcg-bridge/src/lib.rs:146`) returns it — but it is never put into the result, and `ra_path` occurs in this package only as the shape `TCG-PROTOCOL-RUST-v0.1.xml#OP-INIT` promises, never as a field the code emits.*

`req r2`

The bridge speaks LSP 3.17 over the child's stdio (Content-Length framing).

The `initialize` request declares:

Every downstream feature keys off the GRANTED set — a capability the server did not grant degrades per §6 into a well-formed error or a documented fallback, never a crash.

The bridge answers the server's own requests: `workspace/configuration` (with §3's config object), `window/workDoneProgress/create` and `client/registerCapability` (null results).

`req r3`

The spike's central finding: rust-analyzer's most valuable native diagnostics — type-mismatch (E0308), unresolved-name (E0425) — sit behind the DEFAULT-OFF `diagnostics.experimental.enable`.

A null-config oracle answers silence for the very classes the tool exists to catch.

The bridge therefore ships one config object — `{"diagnostics": {"experimental": {"enable": true}}}` — passed BOTH as `initializationOptions` and as every `workspace/configuration` answer.

This is a deliberate, documented posture: the enabled set is experimental by rust-analyzer's own naming, which is one more reason §5's approximation statement is spec, not fine print.

Future config needs (feature flags, cargo target selection) extend this object in one place.

`req r4`

An overlay is an LSP-owned text document: `didOpen {uri, version: 1, text}` claims the document (the server stops reading disk for it), `didChange` with full-text sync and a MONOTONICALLY increasing per-document version replaces it, `didClose` releases it back to disk.

The rules the TS campaign learned the hard way are LSP-native law here and the bridge enforces them structurally:

`req r5`

The TS oracle answers with tsc's own engine; THIS oracle answers with rust-analyzer's independent analysis, which is deliberately partial.

Consequences, all normative:

`req r6`

After `initialized`, the server loads the workspace (cargo metadata, cache priming).

The bridge waits for `experimental/serverStatus` with `quiescent: true`, bounded by a deadline — and that flag is the ONLY trusted signal.

Two live-chain findings harden this (2026-07-07, Phase 3):

A deadline pass degrades: answers carry `degraded: true`, so callers can distinguish warm truth from cold best-effort.

B5 extends to the whole session:

`req r7`

One long-lived child per (root, session).

Graceful exit is the LSP dance — `shutdown` request, `exit` notification — with kill-on-drop as the backstop; the no-zombie property is test-asserted (spike-proven: clean exit code 0, no surviving pid). *Built 2026-08-05 — the proof caught up to the mechanism, which had shipped long before it. The dance ships (`shutdown` at `crates/rust-ai-native-tcg-bridge/src/oracle.rs:356`) and so does the backstop (`Drop for ChildTransport` → `kill()` then `wait()`, `client.rs:346-350`). The assertion now ships too: `dropping_the_oracle_kills_the_child_process_no_zombie` (`tests/live_oracle.rs`) reads the child PID through `ChildTransport::child_pid()`, proves that process is alive, drops the wrapper — deliberately NOT the graceful path, so the kill-on-drop backstop is what is exercised — and polls the OS process table until the PID is gone, treating a recycled PID as dead by comparing `start_time`. Between 2026-08-04 and this build the sentence was a promise; it is now a description.*

Paths become URIs only after verbatim-prefix stripping (`\\?\` breaks child argv and URI builders — the standing lesson's fourth home).

stdout carries LSP frames only; rust-analyzer's own stderr chatter is drained and discarded by the reader (surfaced only in bridge debug logging), so protocol streams stay clean. *Specified, not built — the conclusion holds, the mechanism described does not. Protocol streams do stay clean, but not by draining: the child is spawned `.stderr(std::process::Stdio::null())` (`crates/rust-ai-native-tcg-bridge/src/client.rs:303`, and again at `lib.rs:163`), so the OS discards the chatter at the pipe and no reader ever sees it. There is no bridge debug logging to surface it in — the bridge crate has no logging facility at all.*

`req r8`

Targets are POSTED and MEASURED, never CI-gated (the standing split: gate what cannot flake, record what can).

Spike facts on a minimal crate, this box:

Posted targets for demo-class trees:

The bench harness records distributions per run; a target that moves, moves in a committed REPORT with a reason — and per the owner's resolution a miss CANCELS NOTHING: the campaign proceeds and the miss is reported prominently.

Large-workspace consumers are warned — the tcg brief's `##RISK-COLD-INIT-ON-LARGE-WORKSPACES` carries the spec-layer warning (14.7 s cache-cold on a minimal crate; a big consumer tree may exceed the first-request budget) — and the relay's eager init at `serve` start (before the host's first frame) spends the cold cost as early as possible. The shipped ceiling is the **45 s** quiescence budget (`QUIESCENCE_BUDGET`, `crates/rust-ai-native-tcg/src/lib.rs:33`, used by `spawn_oracle` and `serve`); this document's own `##TARGET-COLD-INIT-TO-QUIESCENT` posts < 15 s for demo-class trees.