CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does basename remove a differently cased suffix after cleaning?
No. The measured .txt suffix leaves REPORT.TXT unchanged; the exact .TXT suffix removes it.
What the test establishes
Both destination calls receive the same cleaned uppercase name. Only the suffix argument changes, producing different names without any difference in character removal. A caller that wants case-insensitive extension routing must define that policy explicitly and preserve the original filename for display. Renaming based on an assumed lowercase match can otherwise leave an unexpected suffix in an exported label.
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": "REPORT.TXT",
"lower": "REPORT.TXT",
"exact": "REPORT"
}Capability boundary
No filesystem lookup or operating-system case folding is performed. This is a basename suffix operation, distinct from comparing a filename extension with a string.
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.