From 4e93547c846444e891e2a2267425c316e6ee5218 Mon Sep 17 00:00:00 2001 From: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> Date: Tue, 20 Oct 2026 02:12:25 +0000 Subject: [PATCH] docs(environment): scope item-shaped and deleted written paths out of documents State documents are held only for list-shaped paths a POST, PUT or PATCH tool writes. Reads of item-shaped written paths and of paths that are only deleted stay recorded views; the guide now says so and the spec defers them to a later increment of #4933. Co-Authored-By: Claude Opus 5.5 --- docs/specs/agent-environments/state-view/spec.md | 4 +++- docs/web-network-captures.md | 5 ++++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/specs/agent-environments/state-view/spec.md b/docs/specs/agent-environments/state-view/spec.md index 10328022a9..9954baef96 100644 --- a/docs/specs/agent-environments/state-view/spec.md +++ b/docs/specs/agent-environments/state-view/spec.md @@ -66,5 +66,7 @@ derived values and cross-type effects are not tied to the state. Serving tool calls from the state, `data/reset`, `data/add` and `data/get` on the environment data plane, exporting the state with a bundle, and write -effects are later increments of #4933. This PR must reference rather than +effects are later increments of #4933. So are documents for item-shaped +written paths (one per identity rather than per template) and for paths that +are only deleted; until then their reads stay recorded. This PR must reference rather than close the issue. diff --git a/docs/web-network-captures.md b/docs/web-network-captures.md index 25885e1a1e..15cc0f2045 100644 --- a/docs/web-network-captures.md +++ b/docs/web-network-captures.md @@ -497,7 +497,10 @@ plan lists the `checked_record_ordinals`. Otherwise the tool is a recorded view with reason `envelope-varies`, `fields-differ` or `list-differs`; the other reasons are `query-body` (a query `POST`), `no-init-recording`, `body-unusable`, `not-entity`, `no-identity` and `query-varies` (a document -read under several queries). A body is usable when its content type is +read under several queries). Documents are held only for list-shaped paths +that a `POST`, `PUT` or `PATCH` tool writes: a non-entity read of an item path +such as `/api/files/{id}`, or of a path that is only deleted, stays recorded +with `no-identity` or `not-entity`. A body is usable when its content type is JSON-like, it is UTF-8 text of at most 256 KiB, every number survives native conversion exactly, and no member is named `__proto__`.