CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does writing cleaned text into a small buffer store the complete value?
No. A one-byte buffer stores A and reports one byte written from AB.
What the test establishes
The homepage produces the complete two-letter value before a fixed-capacity destination buffer is allocated. The write return value and the decoded destination expose a later truncation caused by capacity. A successful cleanup does not imply that a subsequent byte write stored the entire result. Check the number of bytes written and allocate from an explicit encoded size when full retention is necessary. The experiment uses an ASCII fixture so the capacity boundary can be inspected without ambiguity about multibyte character boundaries.
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",
"written": 1,
"stored": "A"
}Capability boundary
Node Buffer.write and a one-byte ASCII destination are measured. Stream backpressure and partial multibyte writes are not tested.
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.