CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does JSON.stringify on a Buffer export a text string?
No. It produces a Buffer type record containing the UTF-8 bytes 65 and 66.
What the test establishes
The cleaned value is encoded into a Node Buffer before JSON serialization. Its serialization contract represents the byte collection, not a primitive text field. A receiver expecting a string therefore needs a deliberate decode before constructing its JSON object. The result separates two valid representations of the same tiny fixture: text for a textual schema and a typed byte record for a byte-oriented schema.
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.
{
"text": "AB",
"json": "{\"type\":\"Buffer\",\"data\":[65,66]}"
}Capability boundary
Node Buffer behavior is measured. No browser Blob, HTTP endpoint or receiver reconstruction is 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.