CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why does my Map keep two records whose cleaned text is identical?
Distinct object keys remain distinct even when both contain text AB.
What the test establishes
The two key objects carry identical text but have different identities. The map therefore retains two entries, and a third newly constructed object does not find either entry. A review index keyed by whole objects cannot be queried by constructing a lookalike record. Choose a documented primitive key when lookup should depend on the cleaned text itself. This example is separate from cleaning collisions between string keys: no key is replaced here, and both entries survive. The callback supplies AB once, after which the harness builds the objects. The ownership and lookup checks show exactly which part of the destination schema controls the outcome.
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.
{
"size": 2,
"lookupNew": false,
"first": 1,
"second": 2
}Capability boundary
Two plain object keys are measured. Primitive key collisions and deep equality libraries 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.