CLAUDE WATERMARK REMOVER · DESTINATION TEST
How can I remove only the leading margin after cleanup?
In this fixture trimStart removes the initial spaces and keeps the final two spaces.
What the test establishes
The two margins are intentional parts of the synthetic record. The actual cleaner removes the internal marker but preserves both margins. The destination trimStart call then changes only the beginning. A fixed-width export that needs a right margin can use that narrower transformation instead of trim, which removes both ends. Inspect the recorded strings with JSON quoting so that retained spaces remain visible during review.
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": " AB ",
"leadingOnly": "AB ",
"both": "AB"
}Capability boundary
Only ordinary spaces are used here. This does not inventory every Unicode whitespace character or establish a policy for indentation in source code.
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.