CLAUDE WATERMARK REMOVER · DESTINATION TEST
Can I remove a preview row without mutating stored rows?
Yes. toSpliced removes CD from the returned preview and keeps both original rows.
What the test establishes
The source contains two line-delimited records. The callback removes the synthetic marker in the first record and preserves the record separator. A destination preview then excludes the second record using toSpliced. Recording both arrays after the call establishes the separation between the stored list and the preview. This gives an export review screen a way to stage deletion before accepting it. The cleaner itself has no row approval policy; that decision belongs to the destination collection operation.
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.
{
"preview": [
"AB"
],
"original": [
"AB",
"CD"
]
}Capability boundary
Two primitive string rows and an in-range deletion are tested. Nested object sharing and older runtime availability are outside this fixture.
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.