CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does a JSON indentation setting of twenty produce twenty spaces?
No. This measured export uses ten spaces before the text property.
What the test establishes
The result is placed in an explicit object so that pretty printing creates an indented member. A numeric spacing request larger than the supported maximum is clamped in the measured serialization. The output remains valid JSON, but its layout differs from the requested width. If downstream snapshots depend on formatting, define a supported indentation setting and compare serialized bytes independently from the cleaned text value.
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.
{
"json": "{\n \"text\": \"AB\"\n}",
"indent": 10
}Capability boundary
This tests a numeric indentation argument, not the separate arbitrary-string indentation contract or JSON parsing of malformed whitespace.
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.