## Description
This PR implements several policy and workflow updates to address the growing issue backlog and improve triage efficiency.
### Changes:
1. **Reduce Stale Issue Threshold**: Updated `.github/scripts/gemini-lifecycle-manager.cjs` to reduce `STALE_DAYS` from 60 to 30.
* **Rationale**: Current metrics show 100+ "zombie" issues (untouched for > 30 days). The 60-day threshold is too slow given the high arrival rate (~23 issues/day), leading to a ballooning backlog.
* **Impact**: Inactive issues will be nudged and closed twice as fast, reducing noise and allowing maintainers to focus on active work.
2. **Increase Triage Capacity**: Updated `.github/workflows/gemini-scheduled-issue-triage.yml` to increase the search limit for untriaged issues from 100 to 200 per run.
* **Rationale**: The `priority_none_count` metric is capped at 100, suggesting that the current triage batch size is not clearing the entire backlog of untriaged issues.
* **Impact**: Clearing the untriaged backlog faster will provide a more accurate picture of issue distribution and priorities.
## Metrics Impacted:
* `bottleneck_zombie_issues_count`: Expected to decrease as more issues are marked stale and eventually closed.
* `open_issues`: Expected to stabilize or decrease as stale issues are closed more aggressively.
* `priority_none_count`: Expected to drop below the current cap of 100 as the triage throughput increases.
## Evidence:
* `throughput_issue_arrival_rate_per_day`: 23.16.
* `throughput_issue_overall_per_day`: 6.22.
* `bottleneck_zombie_issues_count`: 100 (capped).
Fixes the throughput metrics script and introduces new visibility into backlog bottlenecks and priority distribution.
### Changes
- **Throughput Fixes**: Resolved a `ReferenceError` where `isMaintainer` was not correctly scoped, fixed a malformed license header, and added a new metric for `issue_arrival_rate_per_day` to enable growth-vs-closure analysis.
- **Backlog Bottlenecks**: Introduced `bottlenecks.ts` to identify "Zombie" issues (no activity > 30 days) and "Hot" issues (high activity).
- **Priority Distribution**: Introduced `priority_distribution.ts` to track the count of open issues by priority level (P0-P3).
### Impact
These metrics will provide the necessary data to confirm if the repository is experiencing systemic backlog growth (Arrival Rate > Throughput) and help identify which segments of the backlog require urgent triage.
gemini-cli[bot]