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
I2717
A release record pull request gets a verdict that can pass
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- Give the record pull request the release workflow opens a ci verdict it can earn, so that it lands on that verdict and not on a lander's local judgement.
- Why
- 2026-10-14: the record PR of v0.26.0 (#1147, opened by github-actions at 19:07Z) had no checks in its rollup: its pull_request validate 38620991504 ended action_required (a PR authored with GITHUB_TOKEN does not start workflows without approval), and the dispatched validate 38620987044 failed only in the `evidence` job, step gather, exit 12, \"evidence-collect: no report to record: the suite and the crate both left none\", because the record's light plan runs no suite or crate lane. v0.25.0's record runs 38576703346 and 38576698375 failed the same way; both records were landed on the lander's local judgement with --admin. A release path that cannot pass its own gate keeps the landing HOLD up for an hour and trains landers to override.
- Now
- The record PR's verdict comes from a dispatched validate; its light plan selects no evidence-producing lane while the evidence job still demands a report; the pull_request run waits for a human approval.
- Wanted
- On a plan that selects no suite or crate lane the evidence job records an explicit planned-empty report (naming the plan) instead of refusing, and the record PR receives a check that GitHub counts for the branch (the dispatched run reports its verdict onto the PR head, or the PR is opened with a token that triggers workflows); the record lands on that green verdict.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A record PR's validate concludes success when every gate its plan selects passes
- The evidence job on a plan without suite and crate lanes records a planned-empty report and passes
- The record PR shows that verdict as a check on its head without a person approving a run
- Validation
bin/majordomus plan validate- Evidence required
record_pr_verdict_can_pass_case- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.github/workflows/validate.ymlscripts/ci/evidence-collectscripts/ci/verdictdocs/RELEASE.mddocs/CI.mdtest/cases- Not
release.yml's build and publish jobs (another worker owns them)- Depends on
- none
- Priority
- p0
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-14
- Updated
- 2026-10-14
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
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
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares test/cases with I2718; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2720; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2723; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2731; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2734; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2740; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2742; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2747; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2760; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2786; they may not run concurrently | majordomus plan validate |