CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does freezing my cleaned export record protect its nested text?
No. The nested text changes to CD while the outer record remains frozen.
What the test establishes
The cleaned field is stored inside a nested row object before the outer record is frozen. The subsequent assignment targets the nested object rather than the frozen container. Recording both freeze states explains why an export can change after a shallow freeze. A review application that promises an immutable approved snapshot needs to protect the nested data or store an independent serialized snapshot. The homepage callback does not apply an immutability policy to downstream objects. This distinction matters when reviewers approve one value and a later editor changes the nested record before export.
Reproduce the observation
Save tested-app.js and reproduce.cjs together, then run node reproduce.cjs. Compare its output with the recorded observation. The harness executes the actual homepage callback in a minimal DOM and records its resulting field values and method calls. Destination operations run in Node.js; the homepage DOM is a controlled substitute. Runtime: v24.22.1. No submitted text or genuine Claude output is used.
{
"frozen": true,
"nestedFrozen": false,
"text": "CD"
}Capability boundary
One nested plain object is measured. Recursive freezing, accessors and concurrent editing are not tested.
This Claude watermark remover edits a small selected character set. These callback observations do not establish authorship, detector scores, statistical-watermark removal or end-to-end browser behavior. For real work, keep the original and compare the exact result at its destination.
Primary material and next step
The tested first-party source snapshot and complete harness are the primary material for this page. For broader scope, read invisible Unicode versus AI watermarks, or return to the cleaner.