CLAUDE WATERMARK REMOVER · DESTINATION TEST
Can copying a cleaned byte buffer into a smaller target lose its suffix?
Yes. Copy reports one byte and the target contains A rather than AB.
What the test establishes
The cleaned text is first encoded into a complete source buffer. The next operation copies bytes into a separate destination whose capacity is smaller than the source. Comparing the source after copying with the target confirms that the source remains complete while the target receives only the fitting prefix. This is a byte-transfer boundary rather than a marker removal policy. Integration code should inspect copied length or preflight target capacity before claiming the exported record matches the cleaned field.
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.
{
"source": "AB",
"copied": 1,
"target": "A"
}Capability boundary
One nonoverlapping ASCII copy is tested. Shared storage, offsets and concurrent writes are outside scope.
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.