CLAUDE WATERMARK REMOVER · DESTINATION TEST
Must a successful text comparison return exactly negative one?
Use the sign: this observation records a negative result for AB compared with CD.
What the test establishes
The cleaned value is compared with a different ASCII record using an explicit locale. The experiment records both the raw runtime result and the sign check used for ordering. Destination sorting logic should express less-than, equal or greater-than through the sign rather than depending on a particular negative magnitude across implementations. The first-party record makes the observed number inspectable without elevating that one runtime number into a universal guarantee. Cleanup and ordering remain separate steps with separate contracts.
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.
{
"value": -1,
"negative": true
}Capability boundary
One locale and two distinct ASCII values are tested. Accent equivalence and runtime-wide collation conformance are not established.
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.