CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why is the path missing after I export URL.origin?
origin returns only https://example.com; href still contains /AB?q=1#x.
What the test establishes
The callback removes a marker in the path while retaining the query and fragment in the resulting URL string. The destination then chooses the origin getter, which represents a security origin instead of the entire address. The href value demonstrates that the path was not removed by cleanup or lost in parsing. Export href when the schema expects the full serialized address, and use origin only when the receiving field explicitly represents an origin. Keeping the two roles separate prevents silent navigation changes.
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.
{
"origin": "https://example.com",
"href": "https://example.com/AB?q=1#x"
}Capability boundary
A conventional HTTPS URL is tested. Opaque origins and actual navigation are not measured.
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.