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

I0837

Timing report as JSON

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
1
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
1 of 1
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 I0837

majordomus plan verify I0837

majordomus plan done I0837

What it is

Objective
Under --json, print the timing report as one JSON object on stderr with phases and counters, so bench can carry a phase breakdown per sample.
Why
A breakdown that only humans can read cannot be compared by a check.
Now
The report is text.
Wanted
Same data, one line of JSON when --json is set, documented in docs/SCHEMAS.md.
Done when
unknown: the record declares no `completion`
Risk
stdout stays the command's; the report stays on stderr in both forms.

Acceptance

  • The JSON parses with jq and carries every phase and counter of the text form
Validation
MJ_TIMING=1 bin/majordomus --json doctor
Evidence required
phase_timing
Evidence present
phase_timing

Scope

Touches
lib/common.shdocs/SCHEMAS.mdlib/bench.sh
Not
none
Depends on
Priority
p0
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-09-05
Updated
2026-10-08T10:34:30Z
Started
2026-10-08T10:33:54Z
Verified
2026-10-08T10:34:25Z
Completed
2026-10-08T10:34:30Z

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.