CLAUDE WATERMARK REMOVER · DESTINATION TEST
In what order does a reviver inspect a cleaned nested document?
The measured reviver visits the child member, then its parent, then the root empty key.
What the test establishes
The document has one nested numeric leaf and a marker after the closing brace. Cleanup preserves the nested structure. The recorded callback order exposes a bottom-up traversal. A reviver that checks a parent object observes values returned by child callbacks, so validation or transformation should account for that ordering rather than expecting original child values at every level.
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": "{\"a\":{\"b\":1}}",
"order": [
"b",
"a",
""
]
}Capability boundary
The reviver returns each value unchanged. Deletion and integer-precision cases are covered elsewhere; this fixture isolates traversal order without either transformation.
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.