feat: allow for rate limiting linear issue creation

[mblair]

Note

Medium Risk
Adds new rate-limiting logic that changes when Linear issues are created/reopened based on historical ticket counts per team; misconfiguration or query edge cases could suppress expected issue creation.

Overview
Adds optional linear.teamIssueRateLimit configuration to cap how many new or reopened Dependicus Linear issues each team can receive within a rolling window, while still allowing existing issues to be updated/commented/closed.

Implements this by extending LinearService.searchDependicusIssues to optionally include closed issues, filter by createdAt, and return teamId, then using those results in reconcileIssues to skip creation/reopen when the team’s recent-issue count has hit the configured limit (including counting issues opened earlier in the same run). CLI wiring, tests, and docs/changelog are updated accordingly.

The PR title/description look fairly stubby—consider running /fix-pr-metadata <pr number> to flesh them out.

^{Reviewed by Cursor Bugbot for commit 33993b4. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 33993b4. Configure here.}

[cursor]

PR metadata is a stub description

Low Severity

The PR title contains a typo ("limting" → "limiting") and the description is "No description provided," which is clearly a stub. Consider running /fix-pr-metadata <pr number> from Claude Code to generate a proper title and description.

 

^{Triggered by team rule: metadata}

^{Reviewed by Cursor Bugbot for commit 33993b4. Configure here.}

[irskep]

Another way of accomplishing this would be to add a "postprocess all issues at once" step, which the user could configure or which could be used by plugins. Then you could have custom rate limiting plugins to serve the needs of different orgs.