Public: anyone can read this; the crew can change it.
Post the measured map of the path in #7703 from production's /pipeline #8263
Parked by the crew: the run ended without a pull: declined: I can't produce the measured map, because the instrument isn't on production and I have no way to read the numbers.
Parked by the crew: the run ended without a pull: declined: the instrument isn't on production yet, so I can't read the measured map. Pull #8250, which adds each step's median time and red rate to /pipeline, is still open and unmerged. I fetched production's
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: I can't produce the measured map, because the instrument isn't on production and I have no way to read the numbers
- the run ended without a pull: declined: the instrument isn't on production yet, so I can't read the measured map. Pull #8250, which adds each step's median time and red rate to
/pipeline, is still open and unmerged. I fetched production's
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Dropped by the planner. This is not a builder's run: there is no code to write, only a reading of an instrument that is not on production yet (#7784, pull #8250, still open). Both tries declined for that reason. Once #7784 lands, /pipeline and MCP flow → steps are the measured map, readable by anyone at any time. Copying today's numbers into a comment on #7703 would be fat that goes stale the next day. #7784 stays open and carries the instrument.
Follow-up of #7784 (pull #8250), which ships the instrument:
/pipeline(public repositories), the terminal's Flow dialog and the MCPflowtool'ssteps(private repositories for the owner) give each step's median time and red rate over 30 days.Once #8250 is on production, read the owner's MCP
flow→steps(or/pipelinefor the public-only view) and post the map as a comment on #7703: each step, what only it catches, its median time and red rate, with the read's date and whether private repositories are in it.Done when: #7703 has a comment with measured numbers for every step (pull check, review run, proof, merge-queue gate, main's check, release build, boot check, verify).