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
I2396
The CI critical path of 2026-10-10 is measured, recorded, and explained before anything is changed
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
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Record what a pull request's verdict costs today, from the forge's own runs, so that every change of the V4 delivery work is compared with a measurement rather than with a belief.
- Why
- The owner set a bound of five minutes at the 95th percentile for a pull request's required verdict and asked for the integration process to be diagnosed before it is changed. The last measurement on record (.ai/repo/ci/baseline.json) is from 2026-09-05, before the CI model existed.
- Now
- scripts/ci-baseline records runs, jobs and steps; nothing on master holds a measurement of the current CI, and docs/CI.md names no critical path.
- Wanted
- .ai/repo/ci/baseline-2026-10-10.json holds the last 60 validate runs; docs/CI.md states the verdict's percentiles, the share of runner time spent on runs that do not end green, the jobs that set the wall clock with their queue, and the causes of the failed runs, each reproducible from the file.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- .ai/repo/ci/baseline-2026-10-10.json is the output of scripts/ci-baseline over 60 validate runs
- docs/CI.md states p50 and p95 of a green pull request's verdict, the runs that did not end green and their share of runner time, the long jobs with their queue, and the causes of failure, each with a command that reproduces it from the file
- Validation
jq '.runs | length' .ai/repo/ci/baseline-2026-10-10.jsonbin/majordomus plan validate- Evidence required
ci_critical_path_recorded- Evidence present
ci_critical_path_recorded
Scope
- Touches
.ai/repo/ci/baseline-2026-10-10.jsondocs/CI.md.ai/repo/project/issues/I2396.yamldocs/generateddocs/PLAN_STATUS.mddocs/PAGES_STATUS.mdsite/contentsite/data- Not
Changing any workflow, gate or cache: the later V4 issues do that against this measurement.- Depends on
- unknown: the record declares no `depends_on`
- 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-10
- Updated
- 2026-10-14T08:00:44Z
- Started
- 2026-10-14T08:00:38Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T08:00:44Z
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.