CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why did the timezone offset disappear from my JSON text field?
The parsed Date serializes as 2026-01-01T00:00:00.000Z rather than retaining +08:00.
What the test establishes
A marker is deliberately placed inside a seconds field in an explicit offset timestamp. Cleanup restores the timestamp string. Constructing a Date changes the destination value type from source text to an instant, and JSON serialization emits the UTC representation of that instant. The changed spelling is therefore a typed serialization consequence. Preserve the cleaned string separately when the original offset notation is part of the record requirement; an instant alone does not retain that textual choice.
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": "2026-01-01T08:00:00+08:00",
"json": "{\"text\":\"2026-01-01T00:00:00.000Z\"}"
}Capability boundary
One valid explicit-offset date is tested. Local-time parsing, invalid dates and timezone database behavior are not inferred.
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.