CLAUDE WATERMARK REMOVER · DESTINATION TEST
What happens if every alternative review rejects?
Promise.any rejects with AggregateError containing the input rejection reasons.
What the test establishes
Both alternatives deliberately reject in this fixture. The result is an aggregate failure whose errors array preserves the reasons supplied by the input jobs. A destination should inspect this array when presenting why no alternative succeeded. Reading only the outer error name would hide the per-job information needed for review. Here AB is used as a synthetic reason to make preservation visible, not as an actual error classification. The cleanup callback succeeds before these alternatives are constructed. A rejected review therefore cannot by itself establish that the selected character was retained or that the output text is invalid.
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.
{
"name": "AggregateError",
"reasons": [
"first",
"AB"
]
}Capability boundary
All-rejected alternatives only; successful fallback selection and network behavior are excluded.
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.