fix(context-guard, rate-limit-guard): lead band rows with the plugin name and the deciding word #6321

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 4, 2026
2. github-actions commented on Oct 4, 2026

   

   github-actionsBot

   on Oct 4, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   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's short name. In context-guard the zone should also come before the figures, so truncation keeps it. Each plugin needs a version bump, a CHANGELOG line and updated band tests. The owner decision on the format is already recorded on the issue. It says this lands after #6445, which isn't in the open-issues list, so I've treated it as not blocking. No likely duplicates found.

   _{Automated triage, applied by the lanes App.}
3. github-actions

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 4, 2026
4. kyle-sexton commented on Oct 11, 2026

   

   kyle-sexton

   on Oct 11, 2026

   MemberAuthor

   More actions

   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.
5. kyle-sexton

   removed

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 11, 2026
6. kyle-sexton

   added the

   Task

   issue type on Oct 15, 2026
7. kyle-sexton

   added

   priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 15, 2026
8. github-actions commented on Oct 25, 2026

   

   github-actionsBot

   on Oct 25, 2026 – with GitHub Actions

   Contributor

   More actions

   The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
9. github-actions

   changed the issue type from

   Task

   to

   Bug

   on Oct 25, 2026
10. melodic-automation-lanes

    added

    status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

    status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

    and removed

    status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

    on Oct 25, 2026
11. melodic-automation-lanes commented on Oct 25, 2026

    

    melodic-automation-lanesBot

    on Oct 25, 2026

    Contributor

    More actions

    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).
12. melodic-automation-lanes commented on Oct 25, 2026

    

    melodic-automation-lanesBot

    on Oct 25, 2026

    Contributor

    More actions

    The latest triage verdict holds nothing: admission moved the issue to status: needs-decision; its comment says why.
13. melodic-automation-lanes commented on Oct 25, 2026

    

    melodic-automation-lanesBot

    on Oct 25, 2026

    Contributor

    More actions

    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

    • #​6445: the owner decision says this lands after it; it is open and touches rate-limit-guard

    Related work

    • rate-limit-guard: detect an account switch and tell the model the new account's limits #6445 (related): Owner decision sequences this issue after it; still open.
    • fix(guards): one command per guard, band rows off by default, toast on zone and window changes #6271 (related): Merged PR that made the band rows off by default and one command per guard.
    • feat(guards): follow-on improvements to the context-guard and rate-limit-guard mods deferred from #6152 #6156 (related): Open follow-on issue for the same two mods.

    Open questions

    1. What exact text should each band row use for the plugin's short name: the current ctx and 5h, or the plugin name (context-guard, rate-limit-guard), or a short form such as rlg?
       RECOMMENDED: Use the full plugin names, context-guard and rate-limit-guard, as in the existing transcript rows prefixed rate-limit-guard:. Basis: plugins/rate-limit-guard/hooks/rate-limit-guard.test.ts:830
    2. What is the exact context-guard row layout, and what does it show before a reading exists?
       RECOMMENDED: context-guard: smart 23%, then dumb, compacted 23% when degraded, and context-guard: - with no reading. Rate-limit-guard becomes rate-limit-guard: 5h 3% | 7d 73%. Basis: plugins/context-guard/hooks/register.tsx:582
    3. Should this wait for #​6445 to merge before any work starts?
       RECOMMENDED: Yes. Both change rate-limit-guard hooks and tests, so start after #​6445 merges to avoid conflicts. Basis: #​6445

    Sources read

    • plugins/context-guard/hooks/register.tsx:581: bandText builds ctx <n>% \(<zone>\), so the zone comes last and the row starts with ctx
    • plugins/rate-limit-guard/hooks/register.tsx:326: the band row is 5h <x>% | 7d <y>%
    • plugins/context-guard/hooks/context-guard.test.ts:1247: band tests expect ctx -, ctx 23% \(smart\) and ctx 23% \(dumb, compacted\)
    • plugins/rate-limit-guard/hooks/rate-limit-guard.test.ts:586: BAND_ROW is /^5h /; the rows are asserted at lines 605-617 and 1265
    • plugins/context-guard/README.md:142: documents ctx <n>% \(<zone>\)
    • plugins/rate-limit-guard/README.md:129: documents 5h <x>% | 7d <y>%
    • plugins/context-guard/.claude-plugin/plugin.json:3: version 1.0.7
    • plugins/rate-limit-guard/.claude-plugin/plugin.json:3: version 2.0.7

    _{Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.}