CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why are null bytes appended to my concatenated cleaned export?
An explicit total length of four pads the two-byte AB content with two zero bytes.
What the test establishes
The source buffer contains the complete cleaned ASCII field. Two concatenations differ only in whether the destination length is supplied explicitly. The longer destination includes zero bytes after the source content, making the byte-level discrepancy visible without relying on a terminal rendering of null characters. Avoid using an unrelated character quota as the total byte length of an export. Derive the intended allocation from the encoded inputs when exact byte preservation is required. Cleanup removed the synthetic marker before encoding and did not append these destination bytes.
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.
{
"automatic": [
65,
66
],
"explicit": [
65,
66,
0,
0
]
}Capability boundary
One ASCII buffer and a larger explicit total length are measured. Multibyte boundaries and smaller total lengths 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.