CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does deleting an array entry in a JSON reviver compact the array?
No. The measured result keeps length two and has no own entry at index zero.
What the test establishes
The cleaner leaves both numbers in the JSON string. The reviver deliberately returns undefined for the first index, removing that property without moving the next value. The array remains two positions long, and serialization represents the hole as null. If a later table requires compact rows, apply an explicit compaction rule rather than assuming reviver deletion already shifted the positions.
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.
{
"cleaned": "[1,2]",
"length": 2,
"ownsZero": false,
"keys": [
"1"
],
"serialized": "[null,2]"
}Capability boundary
This isolates array deletion shape. The earlier reviver deletion guide concerns object membership; this example does not claim null was present in the source document.
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.