CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does sealing a cleaned record prevent edits to its existing text field?
No. A sealed record still accepts CD in its existing writable text property.
What the test establishes
Sealing is applied after cleanup and before a second assignment to the existing text property. The observed writable descriptor remains true, so the later value is retained. A sealed shape and an approved content snapshot are different requirements. Use the recorded descriptor to diagnose whether a review form can still change an existing field. If the product needs a locked approval state, enforce that state in the editing and export workflow instead of relying on seal to make values immutable. The cleaner has already completed its part before the record protection step.
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.
{
"sealed": true,
"text": "CD",
"writable": true
}Capability boundary
One existing writable own property is measured. Adding properties and strict-mode failures are outside this fixture.
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.