merge-wave

Merge Wave Protocol

Triage every open PR that has finished sharded test262 CI, compute its real net delta, and execute a ranked merge order in one pass.

When to use

• Multiple PRs ready to merge after a morning of dev work
• After a sprint's worth of issues finished CI at roughly the same time
• When you want to cross a pass-rate milestone in one batch

Step 1: Gather candidate PRs

gh pr list --limit 20 --json number,title,headRefName,mergeable,mergeStateStatus

Filter to PRs with mergeStateStatus: UNSTABLE | CLEAN | BEHIND — skip DIRTY (conflict, ping dev to refresh) and DRAFT.

Step 2: Download every PR's merged-report artifact

The sharded workflow uploads test262-merged-report per run. Find each PR's run ID via the merge shard reports check:

mkdir -p output/pr-artifacts
for pr in <LIST>; do
  run_id=$(gh pr view $pr --json statusCheckRollup --jq '.statusCheckRollup[] | select(.name=="merge shard reports") | .detailsUrl' | grep -oE 'runs/[0-9]+' | head -1 | cut -d/ -f2)
  mkdir -p output/pr-artifacts/pr-$pr
  gh run download $run_id -n test262-merged-report -D output/pr-artifacts/pr-$pr >/dev/null 2>&1
done

Artifact filenames: test262-report-merged.json, test262-regressions.txt, test262-results-merged.jsonl.

Step 3: Compute and rank net deltas

BASELINE=$(python3 -c "import json; d=json.load(open('benchmarks/results/test262-current.json')); print(d['summary']['pass'])")

for pr in <LIST>; do
  rpt=output/pr-artifacts/pr-$pr/test262-report-merged.json
  [ -f "$rpt" ] && python3 -c "
import json
d=json.load(open('$rpt'))
s=d['summary']
delta=s['pass']-$BASELINE
print(f'PR #$pr  pass={s[\"pass\"]}  delta={delta:+d}  ce={s[\"compile_error\"]}')
"
done | sort -t= -k3 -n -r

Step 4: Classify each PR

Thresholds (tune per context):

Delta	Action
< −500	CATASTROPHIC → close immediately with diagnosis. Do NOT merge.
−500 to −20	Real regression → close, open follow-up issue, ask dev to investigate root cause
−20 to +20	MARGINAL → check if regressions are false positives; if yes merge, if no close
+20 to +100	GOOD → sample regressions, admin-merge if regressions are false positives or acceptable
+100+	STRONG → admin-merge, flag regressions in a follow-up issue