feat(guards): follow-on improvements to the context-guard and rate-limit-guard mods deferred from #6152 #6156

Activity

1. kyle-sexton

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

   added the

   Feature

   issue type on Oct 4, 2026
3. github-actions commented on Oct 4, 2026

   

   github-actionsbot

   on Oct 4, 2026 – with GitHub Actions

   Contributor

   More actions

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

   _{Automated triage. A maintainer reviews it.}
4. 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
5. kyle-sexton commented on Oct 4, 2026

   

   kyle-sexton

   on Oct 4, 2026

   ContributorAuthor

   More actions

   This was generated by AI during triage.

   Routing: human-gated, needs a decision, work class structural. This is a checklist of five deferred design questions, each with an open "to decide", and three of them change behavior or a cross-plugin contract (the reader contract's fixed pause edge and its drift-gated floor copies). None is delegable as written.

   Two gates sit in front of it:

   1. feat(mods)!: adopt Claude Code mods and move context-guard and rate-limit-guard onto them #6152 (the mods conversion this follows from) is an open draft. Every box describes behavior of the mod modules that exist only on that branch.
   2. ADR 0035 still defers mods on main. Whether mods are adopted is already carried by Pilot a mod producer for context-guard and rate-limit-guard #5777 (pilot a mod producer) and docs: re-run the mods go/no-go after Claude Code 2.1.287 shipped mods #5768 (re-run the go/no-go); this item adds no new carrier for that decision.

   Basis: verified, docs/adr/0035-defer-claude-code-mods-with-five-go-criteria.md on main; gh pr view 6152 reports isDraft: true; #5777 is status: needs-decision, work-class: structural.

   Open questions (one per box), with what settles each:

   1. Malformed zones.json notice: who is told (operator, Claude, or both) and how often. Settled by an owner choice; the resolver already computes notices.
   2. Bands following a lowered auto-compact window: can the mod read the effective window at all? Settled by the per-build session usage types and a probe of the settings and env reads on the machines in scope.
   3. Earlier lane warning before the fixed 90% pause edge: should lanes stop claiming work at an earlier mark, or only report it? A reader-contract change; it must reword the floor copies together with the drift gate (see docs(rate-limit-guard): reword the loop-lane floor's stale headless-tee sentence in the contract and its seven drift-gated copies #6155).
   4. Post-compaction blocking budget: is one grace budget per compaction then deny-until-/clear intended, or does it need its own budget or a way to lift?
   5. Configurable actions at rate-limit thresholds: what would an action be for a lane, given the pause edge stays fixed?

   Recommended next step: once #6152 merges, split each box into its own issue as the body suggests, so each decision is answered and routed on its own.

   Related cluster: #6155, #6156, #6157 and #6158 all wait on #6152; box 3 touches the same floor copies as #6155.
6. kyle-sexton

   added

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

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

   work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.Refactors, migrations, contract changes; cross-cutting and hard to reverse.

   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 4, 2026
7. kyle-sexton commented on Oct 13, 2026

   

   kyle-sexton

   on Oct 13, 2026

   ContributorAuthor

   More actions

   Decision recorded. The owner approved applying independently verified recommendations (high-risk set, reviewed) on 2026-10-13.

   • Box 4 (post-compaction blocking grace budget): what happens to it? → Strike it: the blocking gate was removed
     Basis: plugins/context-guard/CHANGELOG.md:28 (Remove usage throttles and make guard notices to Claude opt-in #7135); plugins/context-guard/hooks/register.tsx:140-141
   • Box 1: who learns that zones.json is malformed? → Operator only, via a toast once per change to the file
     Basis: plugins/context-guard/hooks/register.tsx:150-158 (parse failure swallowed); fix(guards): one command per guard, band rows off by default, toast on zone and window changes #6271 merged (toasts on zone changes); judgment for the channel
   • Box 3: should lanes act on an earlier rate-limit mark before the fixed 90% pause edge? → Report only; no reader-contract change
     Basis: feat(guards): follow-on improvements to the context-guard and rate-limit-guard mods deferred from #6152 #6156 body box 3 (rate_limit_approach_pct at 85%, floor fixed at 90%); docs(rate-limit-guard): reword the loop-lane floor's stale headless-tee sentence in the contract and its seven drift-gated copies #6155 closed 2026-10-07 (floor copies); judgment
   • Boxes 2 and 5 (bands that follow a lowered auto-compact window; configurable actions at rate-limit thresholds): keep here or split? → Split each into its own issue and close feat(guards): follow-on improvements to the context-guard and rate-limit-guard mods deferred from #6152 #6156
     Basis: feat(guards): follow-on improvements to the context-guard and rate-limit-guard mods deferred from #6152 #6156 body 'Each box can be split into its own issue'; triage comment 2026-10-04 'split each box into its own issue'; plugins/context-guard/reference/reader-contract.md:468 (autoCompactWindow row)

   A checklist of five deferred guard-mod improvements from #6152, each with a 'to decide'. #6152 merged 2026-10-04 and #7135 removed the blocking gate, so box 4 no longer applies; boxes 1, 2, 3 and 5 are still open on main.

   Verification notes:

   • Remove usage throttles and make guard notices to Claude opt-in #7135 is a closed issue, not a PR; the CHANGELOG cites it for the gate removal. Mods are hooks modules, so risk is high under the trust-surface rule.

   Verified by an independent fresh-context check (confirmed, risk high): gh issue view 6156 (body, 2 comments); plugins/context-guard/CHANGELOG.md:26-30; plugins/context-guard/hooks/register.tsx:138-160; plugins/context-guard/reference/reader-contract.md:466-469; PR 6271 MERGED, PR 6152 MERGED, issue 6155 CLOSED 2026-10-07, issue 7135 CLOSED; gh pr list search 'zones.json malformed' (none)

   Admission to an agent lane stays with the work-class rules and owner ratification.
8. kyle-sexton

   removed

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

   on Oct 13, 2026