CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does copyWithin insert a copied row without replacing anything?
No. The measured call overwrites the second row with the first and keeps the array length at three.
What the test establishes
Three LF-separated rows survive the callback. The destination copies the first row into an existing position instead of inserting a new position. The former second row disappears from the collection while the length stays unchanged. A preview or export pipeline should explicitly choose insertion if it needs to keep every row, rather than relying on a method whose contract overwrites selected positions.
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.
{
"cleaned": "ab\nc\nd",
"result": [
"ab",
"ab",
"d"
],
"length": 3
}Capability boundary
The copied values are strings. This does not model nested object cloning, CSV multiline records or file-buffer copying.
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.