Edgar ArakelyanandClaude Opus 5.5 2086da6cc7 fix(environment): make the write gate and serving agree on lines, rules, inserts and documents ...

Five places where the gate approved a write serving would answer
differently:
- list and document reads are matched to checked lines as serving
  matches calls (path and query values decoded, the query in any
  order), so a reordered query no longer hides a contradiction;
- an increment or slug applies to every call, so a plan is
  unexplained-change when one call changes such a field and another
  leaves it as it was, in either order;
- an item read confirming a create no longer stops a later list from
  choosing another insert candidate; only a list check fixes the rule;
- the gate runs serving's document body check (accepted members, JSON
  types from the held and initial document), so a recorded write that
  serving would refuse leaves the plan unserved;
- a served create decodes its path values from the collection the call
  names, as the gate decoded the recorded path, whichever spelling the
  call used.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-20 14:12:34 -07:00

..

2356-wasm-interface-comparison

feat(wasm): compare retained core-module interfaces (#2464)

2026-10-13 23:49:04 +08:00

agent-environments

fix(environment): make the write gate and serving agree on lines, rules, inserts and documents

2026-10-20 14:12:34 -07:00

solidity/cbor-metadata

feat(evm): inspect lossless Solidity terminal CBOR metadata (#2790)

2026-10-13 21:55:30 +08:00