CLAUDE WATERMARK REMOVER · DESTINATION TEST
Will cloning my review state preserve a global regex search position?
No. The source cursor is 1, but the cloned regex starts with lastIndex 0.
What the test establishes
The regex executes once against the callback result before it is cloned. Recording source, flags and both cursors shows which parts of the state survive. A review workflow that resumes a scan from a stored object needs to preserve the cursor separately if that position matters. A matching pattern alone does not establish that scanning resumes at the same place. The fixture never claims that the cleaner changes regular expression state: the cursor is produced by destination matching and reset during cloning. This distinction prevents a snapshot implementation detail from being diagnosed as a character-removal regression.
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.
{
"sourceCursor": 1,
"cloneCursor": 0,
"source": "A",
"flags": "g"
}Capability boundary
One successful global match is measured. Sticky matching and browser persistence APIs 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.