2026 OpenClaw Frontend Practice:
Playwright HTML Reporter, Attachment Thresholds & stderr Fingerprint → One Remote Mac PR Summary

1) Each shard writes a full playwright-report tree with screenshots and videos, so naive merges balloon past artifact upload limits before reviewers open a single page.

2) Teams copy the JUnit flow verbatim, but HTML metadata references relative asset paths that break when folders move between runners, producing blank dashboards that look like flaky product bugs.

3) Stderr noise from Node twenty-four deprecation warnings differs per dependency graph, so comment spam repeats unless you hash normalized tails before templating Markdown.

Use the matrix when stakeholders ask why the JUnit HowTo is not enough. HTML answers clickable reproduction steps while traces answer deep engineering dives.

When you also shard workers, align with Playwright shard reporting notes so shard identifiers stay consistent inside HTML and Markdown.

Anchor every path under .openclaw/reports/$GIT_SHA/html/ so OpenClaw templates never guess. Store raw shards as shard-00/ through shard-07/, then emit merged/ for the combined reporter plus manifest.json listing byte sizes.

Keep stderr clips beside HTML as stderr.normalized.txt and stderr.sha256 so fingerprints survive even when HTML merges retry.

.openclaw/reports/$GIT_SHA/html/shard-02/playwright-report/
.openclaw/reports/$GIT_SHA/html/merged/index.html
.openclaw/reports/$GIT_SHA/html/manifest.json

Encode thresholds as environment variables consumed by your Node twenty-four script so remote Mac runners and local laptops share identical behavior.

• MAX_ATTACHMENT_MB rejects any single embed larger than eight megabytes by default.
• MAX_MERGED_ZIP_MB caps the zipped merged folder at roughly one hundred twenty megabytes for Git hosting compatibility.
• STDERR_TAIL_LINES keeps forty lines after stripping ANSI color codes and CI secret patterns.

Author a Markdown skeleton with placeholders for {{FAILED_TESTS}}, {{HTML_URI}}, {{STDERR_FINGERPRINT}}, and {{THRESHOLD_TABLE}}. Your gateway script loads the template, injects facts, then POSTs JSON to OpenClaw using the same route style as other automation gates.

Call the gateway with a tiny wrapper so CI only shells out once:

node scripts/openclaw-send-summary.mjs \
  --template .openclaw/templates/pw-html-summary.md \
  --report-root .openclaw/reports/$GIT_SHA/html/merged

The wrapper should validate manifests before network IO to avoid leaking partial paths into logs.

Grant the OpenClaw token only pull request comment and checks write scopes required for your provider. Rotate keys every fourteen days and load them from the secret store available on the leased Mac instead of echoing into process lists.

Bind each invocation to Idempotency-Key: $GIT_SHA:$PIPELINE:pwhtml so reruns replace the same digest instead of stacking spam.

Merge shows zero tests. You likely merged reports produced under different config hashes; wipe the folder and rerun shards with a shared PLAYWRIGHT_VERSION pin.

Zip still too large after trimming. Drop video retention on passing projects, keep screenshots only for failures, and gzip at level six before comparing to MAX_MERGED_ZIP_MB.

Gateway timeouts. Upload the merged zip to object storage first, then send only HTTPS links inside Markdown to keep payloads under two megabytes.

1. Install Node twenty-four on the remote Mac and verify process.version matches the container image used in production CI.
2. Collect shard folders into the contracted root, chmod read only for merged output to catch accidental overwrites.
3. Prune attachments using the threshold table, logging each skip with original path and byte length.
4. Run merge-reports into merged/, then compute stderr.sha256 after normalizing line endings to LF.
5. Invoke the OpenClaw gateway with the wrapper, exponential backoff on five xx errors, and stop after three attempts to protect branch protection latency.