CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why did my assembled cleaned rows appear in reverse order?
reduceRight visits CD before AB; the resulting accumulator is CD|AB|.
What the test establishes
The callback result still places the first record before the second record. Reverse traversal happens only when the destination assembles the output with reduceRight. The explicit empty initial accumulator avoids an additional implicit first-value rule and makes every visited record visible in the exported string. Compare the original array and the accumulated result to locate the change. If the intended export preserves source order, select a forward traversal rather than asking the cleaner to repair an already correct row sequence.
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.
{
"assembled": "CD|AB|",
"original": [
"AB",
"CD"
]
}Capability boundary
Two dense entries are used. Empty arrays, sparse positions and associative reductions are not measured.
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.