Edgar ArakelyanandClaude Opus 5.5 dc5e2aadff fix(environment): weigh an update's derived changes when a later write replaces it, and reset collection spellings ...

- An update's effect is now every field it sent or changed, derived ones included. A later write replaces it only by overwriting all of them, and an increment adds to its field rather than overwriting it. A PATCH that renames and bumps a version stays confirmed after a PUT that renames but keeps the version.
- The entity-level and collection-level records of what each write changed are kept apart, each forgotten when its own target is checked.
- A reset or load starts from the collection spellings of the state it installs, as a fresh store does, rather than keeping those of the state it replaced.

The verdicts over the 50 captures are unchanged plan by plan, and the smoke applies all 31 served write tools.

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

2026-10-20 22:18: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): weigh an update's derived changes when a later write replaces it, and reset collection spellings

2026-10-20 22:18:34 -07:00

solidity/cbor-metadata

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

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