Files
reverse-engineering-anything/docs/specs/agent-environments/state-coverage/tasks.md
T
Edgar ArakelyanandClaude Opus 5.5 35aee7c051 feat(environment): render more read tools from the state and describe responses
The environment-state view now holds every non-entity GET read with one
initial request line as a read-only document, infers identity from an
`...Id`/`..._id` field every listed item carries distinctly when no fixed
identity name does, and locates single entities wrapped in a one-element
array (`{"posts":[{...}]}`). Served tool descriptions say what each tool
returns, from its own recorded exchanges, and tools carry MCP annotations
(read-only, destructive, idempotent, closed world). On 44 recorded captures
the state renders 1,016 of 1,258 read tools, up from 710.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 20:54:52 -07:00

909 B

Tasks

  • Record the coverage and description contract and its limits.
  • Extend pointers, item location and identity candidates.
  • Require two distinct items before a suffix-named field identifies a list.
  • Hold read-only non-entity reads as documents, retire not-entity and separate path-varies from query-varies.
  • Order entities by earliest sighting and cite records in timeline order.
  • Classify retained bodies in one owner and describe tool responses, preferring 2xx records, with the manifest's statuses.
  • Advertise MCP tool annotations, charged to the catalog, without changing the card.
  • Add domain, services, adapters and compiled-boundary coverage.
  • Document the rules, descriptions and hints; update the contract text.
  • Run static, formatting, duplication, documentation and test gates and the real-capture measurement.