Repository navigation
ci(issues): enable shared inactive issue triage - #615
Conversation
CodeRabbit is currently unavailable under the included-review limit for this author identity in this organization: 16:28 UTC provider refusal, with a 59-minute recovery window from that event. Its documented author scope applies here. Fresh direct current-head review surfaces contain no substantive CodeRabbit review or unresolved finding. The no-gate guard admits progression; continuing to Codex. |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. 👍 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
The native Lint scripts job fails before observing any real pull request because its test stub calls the internal jq helper |
CodeRabbit is currently unavailable under the included-review limit for this author identity in this organization: 16:28 UTC provider refusal, with a 59-minute recovery window from that event. Its documented author scope applies here. Fresh direct current-head review surfaces contain no substantive CodeRabbit review or unresolved finding. The no-gate guard admits progression; continuing to Codex. |
@codex review |
The acknowledged current-head request has produced no substantive review beyond the generous 30-minute response envelope. Its running summary is unchanged since 16:48 UTC. Fresh complete review surfaces contain no finding and the no-gate guard admits progression. Recording this bounded stall and advancing to Bugbot; any later finding remains binding. |
|
|
@cursor review |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 0f45c0f4-30fe-4429-ac36-4b9fe1cdba69) |
devantler
left a comment
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: fa37545
- CodeRabbit: 16:28 UTC author-scoped OSS refusal, with its 59-minute included-review window still current.
- Codex: the current-head acknowledged stall exceeded the generous 30-minute response envelope without a substantive result; the fresh no-gate guard and complete surfaces confirm none has arrived. The older clean receipt names the previous head and is not used.
- Cursor Bugbot: 17:18 UTC current-PR refusal and the exact-head neutral Error check report the user/team usage limit. No paid continuation is authorized.
I reviewed the complete caller and the one-line fixture repair. The immutable source, owner guard, input expressions, permissions ceiling and non-cancelling concurrency agree with the published v17.1.0 interface: PRs force read-only preview, manual runs default to preview, and the daily path deliberately selects the approved 90/30 policy. Application/plugin resource contents and versions are unchanged. The fixture replacement uses public jq range and array slices to preserve ordered 100-item pages and the explicit empty-page case; it changes no production recheck logic, request or write boundary. All 40 local recheck regressions and ShellCheck pass. Fresh native CI, including the previously failing hosted fixture and actual remote preview, is entirely green. The preview writer was skipped. Complete current comments, reviews and threads contain no actionable finding.
Verdict: no P0/P1 findings
Ready at After protected merge, a main-branch preview and first live execution will provide the adoption receipt before the task closes. |
Why
Old, untouched issues make it harder to see which work still needs attention.
What
Apply the agreed reminder after 90 inactive days and closure after 30 more days. New activity and protected work keep issues open, and proposed triage can be previewed. Restore consistent validation across supported environments.
Part of #614