CLAUDE WATERMARK REMOVER · DESTINATION TEST
Will a cleaned .env filename have an env extension?
No. Node path.extname returns an empty string for .env, but returns .txt for report.txt.
What the test establishes
The marker sits inside a dotfile name and disappears during the actual cleanup callback. The resulting name begins with a period but contains no later period. The destination extension helper therefore reports no suffix. A file routing integration should explicitly recognize dotfiles rather than assume every leading dot introduces an extension. The ordinary report.txt control separates this rule from a broken cleaner.
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": ".env",
"extension": "",
"control": ".txt"
}Capability boundary
This uses POSIX lexical filename analysis. It neither opens a file nor detects its media type, and does not measure Windows hidden-file attributes.
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.