Skip to content

v0.7.5

Choose a tag to compare

@shanemhamilton shanemhamilton released this 03 Jul 18:14
· 3 commits to main since this release
5cee0e9

Fixed

  • run_ledger.py now treats lock/backpressure deferrals as neutral counter
    events instead of consecutive product failures. outcome=deferred and known
    lock/backpressure failure_class labels preserve consecutive_failures; true
    failures still increment and successes still reset. A new --counter override
    lets a job force success, failure, or neutral when the automatic mapping
    is not precise enough.
  • run_ledger.py no longer corrupts a blank last_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 --write now refreshes FLEET-REPORT.md when it can map
    the Codex home to <home>/.codex, so the written morning digest does not copy
    a stale fleet headline.
  • fleet_report.py now excludes the same neutral lock/backpressure events from
    blocked_ratio_7d and the blocked-rising flag, mirroring run_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 trip blocked-rising in FLEET-REPORT.md, even though the
    same event was already correctly neutral for its own escalation counter.

Full Changelog: v0.7.4...v0.7.5