[information-architecture] Stale Issues Remediator is grouped with issue detectors

## Information Architecture Findings

### 1. Stale Issues Remediator is presented as a detector even though it only performs remediation
**Area:** Grouping
**Component(s):** `gh-agent-workflows/README.md:25-35`, `gh-agent-workflows/stale-issues-remediator/README.md:1-11,40-47`, `docs/workflows/gh-agent-workflows.md:67-82`
**Problem:** The repository index places **Stale Issues Remediator** under the **Detectors (file issues)** section and describes it alongside issue-finding workflows. Its own README says it processes already-stale-labeled issues, removes the label for objections, and closes expired issues; it does not detect or file stale-issue reports. The docs-site catalog separately treats it as the remediation companion to **Stale Issues Investigator**. A user choosing a detector from the directory index can therefore select a workflow that does not perform detection, and may miss the required investigator/remediator pairing.
**Suggested improvement:** Move Stale Issues Remediator out of the Detectors section into a clearly named remediation/fixer or lifecycle-pairing section, and link it next to Stale Issues Investigator consistently in the directory README and docs catalog.

## Suggested Actions
- [ ] Reclassify `stale-issues-remediator` in `gh-agent-workflows/README.md` under remediation/fixer workflows rather than Detectors.
- [ ] Add a consistent investigator/remediator pairing entry or cross-link in the workflow directory and docs catalog.

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Trigger Information Architecture](https://github.com/elastic/ai-github-actions/actions/runs/29600091326)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.