CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why are cleaned digits exported as tiny numbers rather than ASCII bytes?
Uint8Array.from("12") produces 1 and 2; UTF-8 encoding produces 49 and 50.
What the test establishes
The two destinations receive the same cleaned string but perform different conversions. Iterating a string into a numeric typed array converts each yielded digit to a number. Encoding the text instead creates the bytes that represent those digits. A file writer needs the latter when its contract is textual UTF-8. Inspect the resulting bytes rather than relying on the original string preview to validate an export. The test keeps both digits nonzero so the conversion remains visible without ambiguity about empty or invalid numeric input. This operation occurs after the homepage has removed the synthetic marker.
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": "12",
"numeric": [
1,
2
],
"utf8": [
49,
50
]
}Capability boundary
Only two decimal digits are measured. Nonnumeric text, overflow and grapheme handling are excluded.
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.