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

I2474

The drain draws its merge throughput: each day's merges over the fortnight its trail ends on

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
4
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
2 of 2
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2474

majordomus plan verify I2474

majordomus plan done I2474

What it is

Objective
Draw on the PR Drain how many pull requests the executor merged on each of the fourteen days that end on the day of its trail's newest event, as a chart whose counts are written in its label and in a table beside it.
Why
The owner asked on 2026-10-11 to implement every view of the UI screenshots (reference 03-pr-drain shows a merge throughput chart; pack v3 M04-03, measured time series). The executor's trail records every merge_succeeded with its time, and the queue already folds a seven-day merge count, but nothing showed the series.
Now
The drain shows merges in seven days and merges per day as two numbers.
Wanted
The drain panel, which asks integration.events, draws 'Merge throughput': the fourteen days ending on the trail's newest event's day (the record's end, not the reader's clock), each with its count of merge_succeeded events, as a server-side SVG chart labelled with every day's count and a table of the same numbers. An attempt is no merge, a merge outside the window is not drawn, and a trail with no merge in the window says so and draws no chart.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • the chart covers fourteen days ending on the trail's newest event's day
  • each day counts merge_succeeded events only, and the counts are in the chart's label and a table
  • a trail with no merge in the window draws no chart and says so
Validation
cargo test --lib ui::prstest/run.sh 1079_the_drain_draws_its_throughput
Evidence required
ui_throughput_unit_testui_throughput_case_1079
Evidence present
ui_throughput_unit_testui_throughput_case_1079

Scope

Touches
apps/majordomus-cli/src/ui/prs.rs.ai/repo/project/issues/I2474.yamldocs/MAJORDOMUS_UI.mdtest/cases/1079_the_drain_draws_its_throughput.sh
Not
unknown: the record declares no `non_scope`
Depends on
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-11
Updated
2026-10-12T11:04:08Z
Started
2026-10-12T11:03:47Z
Verified
2026-10-12T11:03:54Z
Completed
2026-10-12T11:04:08Z

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.