Slice detached element recovery encoding and audit progressive canvas
This commit is contained in:
+20
-2
@@ -1001,8 +1001,8 @@ is suspended; the old image still contains its captured state, and the next cut
|
||||
is saved after it. Request dispatch retains the durable-prefix barrier. Encoding
|
||||
or scheduling failures retain the pending Root for retry and produce no partial
|
||||
storage commit. Initial DTO membership copying, synchronous preparation, unknown
|
||||
subtrees, first-time immutable normalization and individual scalar operations
|
||||
remain synchronous. This is partial time slicing, not a strict whole-Root latency
|
||||
subtrees and individual scalar operations remain synchronous. First-time element
|
||||
normalization can defer only when its detached JSON provenance is established. This is partial time slicing, not a strict whole-Root latency
|
||||
bound. Grouped history entries now keep shape ownership for newly built changes and
|
||||
operation-ID arrays, including undo/redo lifecycle remaps. Import runners keep it
|
||||
for their own job envelopes, completed-key arrays, binding dictionaries and
|
||||
@@ -1136,3 +1136,21 @@ also rechecks its immutable fact cache when assembling a prepared container:
|
||||
when the same source occurs twice in one image, the second occurrence can reuse
|
||||
the first completed encoding. Preparation still captures unsafe occurrences
|
||||
independently; getters and mutable descendants never qualify for this reuse.
|
||||
|
||||
First-time element recovery encoding now uses the core's detached-JSON ownership
|
||||
proof instead of synchronously normalizing every field before the first yield.
|
||||
Only `detachElementData` results qualify: JSON-cloned, recursively frozen records
|
||||
with immutable JSON descendants. A shallow freeze, a document factory envelope,
|
||||
or an arbitrary host object does not qualify. Preparation requires the standard
|
||||
Object/Array prototype chain without inherited `toJSON`; otherwise it captures
|
||||
through the original normalizer. Every unknown normalization invalidates this
|
||||
prototype check because callbacks may change the environment. The cooperative
|
||||
walk reads the already detached own data and validates depth while building the
|
||||
same immutable JSON and byte facts. A callback later in capture cannot change an
|
||||
earlier record's meaning. Cold and cached subtrees both retain the depth limit.
|
||||
This moves the first full field/row walk into the shared budget; container-member
|
||||
capture and individual native/scalar operations still have synchronous work.
|
||||
|
||||
Step 4's current acceptance evidence, commands and explicit remaining checkpoint
|
||||
encoding work are recorded in [STEP4_ACCEPTANCE.md](STEP4_ACCEPTANCE.md). Passing
|
||||
functional fixtures is not a claim that all performance limits are resolved.
|
||||
|
||||
Reference in New Issue
Block a user