Repository navigation
feat(harness-ops): observability rolls up usage per work item #11875
Description
Problem
Agent telemetry carries the work item URL (autonomy.work_item.url) and cloud sessions carry
ccr.session.id, but /harness-ops:observability reports no usage per item.
Origin: D68, Q58, Q560 (session-to-item map keyed on ccr.session.id).
Fix
Add a per-item rollup to /harness-ops:observability: tokens and turns grouped by
autonomy.work_item.url, with cloud sessions joined to items through a ccr.session.id map. It
never prices.
Done when
- The observability skill documents the rollup and the join; its query groups by the item URL and
ccr_session_id. - A test over a fixture store with two items and one cloud session checks the per-item totals; it passes under
scripts/run-test-file.sh. - No output carries a price (the repository's cost-claims rule);
bash plugins/skill-quality/scripts/check-skill.sh plugins/harness-ops/skills/observabilityexits 0 andbash scripts/check-changelog-fragments.shpasses with a harness-ops fragment.
Parent: #7578
Activity
github-actions commentedon Nov 1, 2026
melodic-automation-lanes commentedon Nov 1, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41281707718, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T07:31:35Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026