Skip to content

Read at

A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live

PR Drain

Pull requests converging on master, one at a time.

Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.

  • Issues ready86plan.status /counts/by_status/READY
  • Issues active1plan.status /counts/by_status/ACTIVE
  • Issues blocked159plan.status /counts/by_status/BLOCKED
  • Issues done161plan.status /counts/by_status/DONE

Issue

One issue of the plan, as the plan records it.

I2654 · surfaces-never-disagree · p3 · wave 1

A chart is held to its table by a gate, and the tables that are measured series are drawn

blockedPull requests that name itClose

Give the chart component (site/charts.js, ADR 0152) the two checks it lacks, and declare the remaining tables whose content is a measured series as charts: the benchmark baselines, the economics pairs and segments, the claims by status.

Depends on
I2653
Blocked by
I2653
Unblocks
none
Serves
none
Scope
site/charts.jssite/templates/registry-benchmarks.htmlsite/templates/economics.htmlsite/templates/features-matrix.htmlscripts/site-checkscripts/lib/interaction-specs/chart.mjsand 2 more
Evidence
0 of 2
Started
not yet
Verified
not yet
Completed
not yet

plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view

Pull-request drain

The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.