CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does assigning a cleaned password preserve a literal at sign in href?
The password setter serializes the literal at sign as %40; its password getter also returns the encoded form.
What the test establishes
The fixture uses a synthetic credential and makes no network request. Cleanup removes the marker from its text, then URL serialization escapes the delimiter so it remains inside the password component. Seeing percent characters in the resulting URL does not mean the original invisible mark survived. Keep component assignment separate from URL-string concatenation and do not use this synthetic demonstration as a reason to put real secrets into shared URLs.
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": "p@ss",
"password": "p%40ss",
"href": "https://demo:p%40ss@example.com/"
}Capability boundary
Only serialization is measured. Authentication, password validation, server decoding and credential storage are outside this test.
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.