Repository navigation
v0.7.5
Fixed
run_ledger.pynow treats lock/backpressure deferrals as neutral counter
events instead of consecutive product failures.outcome=deferredand known
lock/backpressurefailure_classlabels preserveconsecutive_failures; true
failures still increment and successes still reset. A new--counteroverride
lets a job forcesuccess,failure, orneutralwhen the automatic mapping
is not precise enough.run_ledger.pyno longer corrupts a blanklast_success:counter by parsing
the closing<!-- /ao:counters -->marker as the timestamp, and it repairs
orphan closing markers left by older bad parses.approval_digest.py --writenow refreshesFLEET-REPORT.mdwhen it can map
the Codex home to<home>/.codex, so the written morning digest does not copy
a stale fleet headline.fleet_report.pynow excludes the same neutral lock/backpressure events from
blocked_ratio_7dand theblocked-risingflag, mirroringrun_ledger.py's
counter treatment. Previously a job that deferred often for routine
concurrency reasons (shared workspace, colliding schedules) could still read
as "blocked" or tripblocked-risinginFLEET-REPORT.md, even though the
same event was already correctly neutral for its own escalation counter.
Full Changelog: v0.7.4...v0.7.5