CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does lastIndex force a non-global regex to start later?
No. The measured non-global expression matches A at zero despite lastIndex being one, and keeps that stored value.
What the test establishes
The expression has neither global nor sticky flags. Setting its cursor-looking property does not change where this execution searches. A destination scanner that relies on a moving offset must choose an API and flags that actually honor that offset. The recorded result distinguishes the inactive stored property from a failed cleanup or a marker still occupying the first position.
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",
"index": 0,
"lastIndex": 1
}Capability boundary
This contrasts with the existing global cursor guide. Only one non-global execution is measured; no performance or concurrent-regex behavior is claimed.
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.