th-9e792d: reconcile parity docs — durable backend + telemetry + knowledge now in all five

[brentrager]

Problem

Epic th-9e792d merged, but the parity docs are stale and now understate what ships.

What this corrects (docs only — no code change)

1. Durable-execution BACKEND (Temporal) now in all five languages, not Rust-only. Rust = smooth-operator-temporal crate; new optional Go/TS/Python/.NET packages (core-repo PRs 🦋 New version release #170/🦋 New version release #168/th-0215f2: SEP — host extensions in the .NET operator server (gated on core 1.4.0) #169/Identity intake: channel-normalized lead capture (spec + Rust + TS client) #173), each with a client-side AgentExecutor (start workflow, durable approve/deny HITL signals, durable-wait timer, e2e-tested against a real Temporal server). Server-side selection seam (SMOOTH_AGENT_DURABLE_EXECUTOR, dependency-injected so the published server keeps no hard Temporal dep) in all five servers (this repo PRs th-137b91: Go server durable-executor selection seam (Q parity) #450/th-137b91: TS server durable-executor selection seam (Q parity) #451/th-137b91: Python server durable-executor selection seam (Q parity) #452/th-137b91: .NET server durable-executor selection seam (Q parity) #455).
   • Kept the honest ADR-030 shared follow-up — durable path yields only a terminal result (no token-delta streaming), costUsd=0 on the workflow result, executor seeds from agent config only. Reframed as one follow-up identical across all five incl. the Rust reference, not a Rust-vs-others gap.
2. Server gen_ai.* OTel spans now in all five servers (chat + tool spans, redacted tool args, env-gated OTLP) — added a PARITY §3 row.
3. Durable knowledge + ACL-knowledge Postgres stores now in Go/TS/Python too (PRs th-0814f6: Go server vector-knowledge Postgres store (L parity) #442/th-0814f6: TS server vector-knowledge Postgres store (L parity) #443/th-0814f6: Python server vector-knowledge Postgres store (L parity) #444), alongside Rust and .NET. Kept honest: persistent checkpoint store still pending in Go/TS/Py (so ◐, not ✅); TS/Python knowledge shipped + contract-tested but not yet wired into the live dispatcher; DynamoDB + S3-Vectors second backend remains Rust-only.
4. Engine now has one honest exception (extension sandbox / integrity hardening), not two — every "except two … durable backend ships only for Rust" claim corrected.

Files

• README.md — engine cell (except two → except one); servers cell (Go/TS/Py knowledge stores + all-five telemetry).
• PARITY-STATUS.md — §1 durable-backend row + footnote; §2 → one exception; §3 telemetry row + knowledge row/footnote; §4 known-remaining reframed; §5 re-verify greps updated.

Verification

git grep confirms no stale "durable backend ships only for Rust" / "except two" / telemetry-Rust-only claim remains; the only surviving Rust-first/Rust-only mentions are the genuinely-Rust-only surfaces (sandbox, DynamoDB+S3-Vectors, Redis/NATS backplane).

🤖 Generated with Claude Code

https://claude.ai/code/session_01YbN45JeWDbcjvFqGJvmVD3

[changeset-bot]

⚠️ No Changeset found

Latest commit: fcaaf9d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR