mirror of
https://github.com/morluto/rea.git
synced 2026-10-28 02:15:44 +00:00
2e6b38cef0
* feat(environment): render more read tools from the state and describe responses Keep main's environment serving and fold in coverage for non-entity reads, response summaries, and MCP tool annotations. Squashed rebase of #5352 onto main. * fix(environment): keep rendered documents and quoted samples inside their budgets A recorded body of exponential numbers can render past 256 KiB and turn a working read into a state size error, so that document stays a recorded replay. Description samples are measured after JSON quoting, and the replay-fallback catalog check uses a tool count the longer response descriptions still separate. Co-authored-by: morluto <morluto@users.noreply.github.com> * test(environment): pin the replay card this branch serves The replay-only card test pinned main's 11,131-byte card. This branch's descriptions name each tool's recorded responses, so the card it serves is 12,818 bytes; the pin and its name follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: morluto <morluto@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
17 lines
909 B
Markdown
17 lines
909 B
Markdown
# Tasks
|
|
|
|
- [x] Record the coverage and description contract and its limits.
|
|
- [x] Extend pointers, item location and identity candidates.
|
|
- [x] Require two distinct items before a suffix-named field identifies a list.
|
|
- [x] Hold read-only non-entity reads as documents, retire `not-entity` and
|
|
separate `path-varies` from `query-varies`.
|
|
- [x] Order entities by earliest sighting and cite records in timeline order.
|
|
- [x] Classify retained bodies in one owner and describe tool responses,
|
|
preferring `2xx` records, with the manifest's statuses.
|
|
- [x] Advertise MCP tool annotations, charged to the catalog, without changing
|
|
the card.
|
|
- [x] Add domain, services, adapters and compiled-boundary coverage.
|
|
- [x] Document the rules, descriptions and hints; update the contract text.
|
|
- [x] Run static, formatting, duplication, documentation and test gates and the
|
|
real-capture measurement.
|