CLAUDE WATERMARK REMOVER · DESTINATION TEST
Can a cloned Map retain my cleaned text when JSON loses its entries?
Yes. structuredClone retains the Map entry AB; ordinary JSON serialization yields an empty object.
What the test establishes
The fixture compares a structured clone with JSON output from the same source Map. The cloned container remains a Map and supports the expected key lookup. Ordinary JSON does not represent those entries automatically. This gives a local storage workflow two distinct contracts to review: an in-memory snapshot and a textual interchange format. Do not assume success in one establishes success in the other. The test also records reference inequality to distinguish a new container from a second name for the original. The cleaned value is a primitive string, so nested object aliasing is outside this observation.
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.
{
"isMap": true,
"value": "AB",
"same": false,
"json": "{}"
}Capability boundary
One string-valued Map is measured. Nested object sharing and persistence across processes are excluded.
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.