stale-bot-implementation

[indurireddy-TF]

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

1. Link to an existing issue (if applicable):

• Closes: #issue_number
• Related: #issue_number

2. Or, if no issue exists, describe the change:

If applicable, please follow the issue templates to provide as much detail as
possible.

Problem:
Maintaining inactive issues manually is time-consuming and inconsistent.
There was no automated mechanism to:

Identify stale issues based on inactivity
Handle maintainer–user interaction intelligently
Detect silent updates (description edits without comments)
Automatically close issues after a defined threshold

This leads to:

Accumulation of outdated issues
Reduced repository hygiene
Increased manual effort for maintainers
Solution:
Implemented an AI-driven stale bot that:

Analyzes issue activity using GitHub GraphQL + timeline events
Differentiates between:
Author activity
Maintainer activity
Internal maintainer discussions
Detects silent edits and alerts maintainers
Applies intelligent decision logic:
Marks issues as stale after inactivity
Removes stale label when user responds
Closes issues after stale threshold is exceeded
Uses an LLM agent with a structured decision tree for consistent behavior

Testing Plan

Please describe the tests that you ran to verify your changes. This is required
for all PRs that are not small documentation or typo fixes.

Unit Tests:

• I have added or updated unit tests for my change.
• All unit tests pass locally.

Please include a summary of passed go test results.

Manual End-to-End (E2E) Tests:

Please provide instructions on how to manually test your changes, including any
necessary setup or configuration. Please provide logs or screenshots to help
reviewers better understand the fix.

Checklist

• I have read the CONTRIBUTING.md document.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have manually tested my changes end-to-end.
• Any dependent changes have been merged and published in downstream modules.

Additional context

Add any other context or screenshots about the feature request here.