CLAUDE WATERMARK REMOVER · DESTINATION TEST
Will faster cleanup-review jobs move ahead in Promise.all?
No. Results retain input order even when jobs finish in reverse order.
What the test establishes
The fixture puts a pending promise first and an already resolved promise second. It then supplies the cleaned AB value to the first job. The returned array follows the supplied job list, so associating results with input rows by index is valid for this operation. This does not mean that jobs executed sequentially. A completion log and a result array answer different questions. Preserve the original job list when joining these results back to review records. The test deliberately uses manual resolution rather than a network delay, making the ordering contract reproducible without relying on a clock or a particular server response time.
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.
{
"results": [
"AB",
"second"
]
}Capability boundary
Two fulfilled jobs are measured; rejected jobs and cancellation 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.