CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why does my byte array sort differently from an ordinary array?
Uint8Array sorts 2 before 10 by default; an ordinary array sorts 10 before 2.
What the test establishes
Both containers begin with the same two numeric values parsed from the cleaned field. The difference comes from their default sorting contracts. An ordinary array compares string representations when no comparator is supplied, while this numeric typed array orders its values numerically. A destination must select its sort behavior rather than infer it from the displayed numbers. Keep a copy if the unsorted review order is needed later because the sort operations used here mutate their own containers. The callback only removes the synthetic separator marker; it does not parse the comma-separated values or decide how exported rows should be ordered.
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.
{
"plain": [
10,
2
],
"typed": [
2,
10
]
}Capability boundary
Two positive integers in the Uint8 range are measured. Floating point, NaN and custom comparators 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.