CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does an undefined find result prove no row matched?
No. Both a matching undefined entry and a missing match return undefined; findIndex distinguishes them here.
What the test establishes
The cleaned string is stored beside an intentionally undefined slot value. The two searches have different outcomes but return the same JavaScript value. A record-processing integration should retain an index or explicit found flag when undefined is a valid row value. Otherwise a fallback can silently treat a present row as absent even though text cleanup and collection construction both succeeded.
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": "AB",
"matchedType": "undefined",
"missingType": "undefined",
"matchedIndex": 0,
"missingIndex": -1
}Capability boundary
This is an explicit undefined entry, not a sparse array hole. It does not measure database null values or the homepage result type.
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.