CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does appending a cleaned query value replace the existing value?
No. getAll returns old and AB after append adds a second q field.
What the test establishes
The destination already has a query field before the cleaned value is appended. Recording the first-value lookup, the complete value list and the serialized query shows why a receiver can still read the old value. Appending is appropriate when repeated values are intended, but an update workflow must choose its replacement policy explicitly. Validate the receiving service contract rather than assuming it reads the newest repeated field. The experiment never sends the query to a server; it establishes local serialization and lookup behavior only. The callback result is AB before append runs.
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.
{
"first": "old",
"all": [
"old",
"AB"
],
"query": "q=old&q=AB"
}Capability boundary
One repeated query name is measured. Server-side duplicate interpretation and network requests are not tested.
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.