Skip to content

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

Open

Description

@kyle-sexton

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

  1. 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.
  2. 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

Activity

  1. added
    needs-triageNot 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-actions
    Contributor

    Thanks for the report. Automated triage handed this issue to a maintainer.

    Automated triage. A maintainer reviews it.

  3. added
    needs-humanHuman-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
    MemberAuthor

    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. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 11, 2026
  6. added theissue type on Oct 15, 2026
  7. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions