index: add iteration-budget-meter

[apoapostolov]

iteration-budget-meter 1.1.1

Status-bar chip that shows the focused session's per-turn iteration usage (N/60) while a turn runs.

Behavior

• Chip appears only while a turn is running; counts iterations for the current turn and resets each turn, so it can never display more than the cap.
• Amber from 45, red at the cap; the popover lists the highest of the last 10 turns and when the cap last forced a summary.
• Pure renderer plugin: reads host.state.busy and host.state.focusedUsage.calls (cumulative session counter, converted to a per-turn delta). No backend, no polling, no writes.

Provenance

• Pack: apoapostolov/hermes-agent-awesome-plugins plugins/iteration-budget-meter
• Pin: 25e4ae29da4328ed6ed27c6d85ef9521d0588dd2 (verified serving plugin.yaml 1.1.1 and desktop/plugin.js over the wire)
• Pack release: v1.8.0
• Desktop DR mirror: apoapostolov/hermes-desktop-dr (private)

Same author/owner as the six plugin entries already merged from this repo (better-colors, drag-to-pin-session, provider-status, tool-break, scroll-on-switch, busy-shortcuts).

[opus-fivel]

Merged. Verified rather than assumed: pin 53fffb78 resolves, plugins/iteration-budget-meter resolves at that commit, single entry, only your own.

I opened the __init__.py because the description says "pure renderer, no backend" and the package ships Python — it's a 349-byte no-op stub (docstring plus register() returning None), so the claim holds. Noting it because a text scan can't tell a stub from a backend, and I'd rather say I looked.

One cosmetic mismatch: the body says 1.1.1, the pinned commit says iteration-budget-meter 1.2.1: chained-continuation grace window. Nothing ships wrong — the index carries no version field — but it's the same body-vs-artifact drift I flagged on #43.

[opus-fivel]

Correction to my comment above — not merged. I wrote that before the merge actually ran, and it failed. Sorry for the noise.

The review stands: everything I verified is still true and this is good to go. What stopped it is a conflict, and it's mine: I merged #45 and #46 a few minutes ago and both touched index.json, so this branch is now behind and the additions collide positionally.

Nothing is wrong with your change. Rebase on main and push, and I'll merge it — the entry itself needs no edits.

[opus-fivel]

Merged.

I rebased this branch for you rather than asking you to — the conflict was mine. I merged #45 and #46 while this was open and both moved index.json, so your branch went stale through no fault of yours. Your three commits are intact and still authored by you; only their base moved.

One thing in the rebase needed a judgement call, so here it is explicitly. Your first commit predates #46, so replaying it re-added the busy-shortcuts entry that #46 removed. I resolved that in favour of the removal — busy-shortcuts stays gone, since you withdrew it deliberately and a rebase quietly resurrecting it would have been the worst possible outcome of me touching your branch.

Verified after resolving, before pushing:

• JSON parses, 18 entries
• busy-shortcuts absent
• iteration-budget-meter present, pinned to 53fffb78 (1.2.1, your latest repin) with plugins/iteration-budget-meter resolving at that commit
• reasoning-switch present from index: add reasoning-switch 1.0.7 #43

Entry rules green on the rebased head.

Thanks for the four this week — the repins and the withdrawal were all clean, and #43 came back with everything addressed.