Repository navigation
fix(context-guard, rate-limit-guard): lead band rows with the plugin name and the deciding word #6321
Description
Summary
PR #6318 compared the #6222 guard displays against the new mod guidance (/user-interface:design, mods type). Each band row conforms on default-off, dim, truncation and single row, but two rows have gaps in their text.
Gaps
- context-guard band row (
ctx 24% (acceptable)): the row doesn't start with the plugin's short name, and the deciding word (the zone) comes last, so truncation cuts it first. - rate-limit-guard band row (
5h 3% | 7d 73%): the row doesn't start with the plugin's short name.
Proposed fix
- Start each band row with the plugin's short name.
- In context-guard, put the zone before the figures so a truncated row still shows it.
Each change needs a version bump and a CHANGELOG line in its plugin, plus updated band tests.
Related
- fix(guards): band rows and notice repeat the status line, and the documented /<guard>:band commands do not exist #6222: the guard displays.
- feat(user-interface): add the user-interface plugin #6318: the checklist that found these gaps ("fix(guards): band rows and notice repeat the status line, and the documented /<guard>:band commands do not exist #6222 guard displays against the mod guidance" table).
- feat(mods): terminal UI design conventions for mod displays #6224: mod authoring, which points at the user-interface mod guidance.
Activity
github-actions commentedon Oct 4, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: the context-guard and rate-limit-guard band rows should start with the plugin name. In context-guard the zone should come before the figure, so truncation keeps it. The refinement comment already gives the exact row text. Both plugins need band test updates, README updates, a version bump and a CHANGELOG line. The refinement's earlier dependency on #6445 has merged, so nothing blocks this. I found no likely duplicates. #6156 is related follow-on work for the same two plugins.
Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 11, 2026
Owner decision (2026-10-11): Band-row format: plugin name first; in context-guard the zone comes before the figures. Lands after #6445.
Recorded by the coordinating agent session with the owner's approval. Removing
needs-human; implementation is queued and will link its branch here.github-actions commentedon Oct 25, 2026
The triage sweep dispatched intake triage for this issue (attempt 2 of 2).
melodic-automation-lanes commentedon Oct 25, 2026
Not admitted to the issue lane: no trusted-human acceptance criteria: a listed human must put the confirmed
- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Oct 25, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.melodic-automation-lanes commentedon Oct 25, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Band rows lead with the plugin name, and context-guard shows the zone before the figure, with version bumps, CHANGELOG lines and updated band tests in both plugins.
Dependencies
Related work
Open questions
ctxand5h, or the plugin name (context-guard,rate-limit-guard), or a short form such asrlg?RECOMMENDED: Use the full plugin names,
context-guardandrate-limit-guard, as in the existing transcript rows prefixedrate-limit-guard:. Basis: plugins/rate-limit-guard/hooks/rate-limit-guard.test.ts:830RECOMMENDED:
context-guard: smart 23%, thendumb, compacted 23%when degraded, andcontext-guard: -with no reading. Rate-limit-guard becomesrate-limit-guard: 5h 3% | 7d 73%. Basis: plugins/context-guard/hooks/register.tsx:582RECOMMENDED: Yes. Both change rate-limit-guard hooks and tests, so start after #6445 merges to avoid conflicts. Basis: #6445
Sources read
ctx <n>% \(<zone>\), so the zone comes last and the row starts withctx5h <x>% | 7d <y>%ctx -,ctx 23% \(smart\)andctx 23% \(dumb, compacted\)ctx <n>% \(<zone>\)5h <x>% | 7d <y>%Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Oct 26, 2026
This was generated by AI.
Releasing the hold: no question is open. The latest
status: needs-decisioncame from admission ("no trusted-human acceptance criteria"), which ran before the refinement comment holding the criteria was posted. This issue was filed by a listed human, so the unedited refinement counts as its spec (owner Q78). The label comes off and intake triage is dispatched again so admission reads the refinement.The refinement's open detail, the exact short name, is trivial: use the full plugin name (
context-guard,rate-limit-guard), as the 2026-10-11 decision says "plugin name first". The #6445 dependency has merged (#9994). Criteria:context-guard: <zone> <n>%, orcontext-guard: -with no reading.rate-limit-guard: 5h <x>% | 7d <y>%.