[information-architecture] Homepage Bug Hunting setup path conflicts with promised auto-fix behavior

## Information Architecture Findings

### 1. Homepage onboarding promises auto-fix PRs but installs detector-only workflow
**Area:** Empty states and onboarding
**Component(s):** `docs/index.md`, `docs/workflows/gh-agent-workflows/bugs.md`
**Problem:** The homepage positions Bug Hunting as a workflow that will "open PRs to fix" bugs, but the quick-install command directly below installs `bug-hunter/example.yml`, which is the detector-only configuration. Users following the primary onboarding path can reasonably expect automatic PR creation, then encounter a detector-only outcome (issue reports/noops) instead.

**Evidence:**
- `docs/index.md:94` describes Bug Hunting as "Find reproducible bugs and open PRs to fix them".
- `docs/index.md:106-107` quick install downloads `gh-agent-workflows/bug-hunter/example.yml`.
- `docs/workflows/gh-agent-workflows/bugs.md:9-12` explicitly defines that same example as **Detector only**.
- `docs/workflows/gh-agent-workflows/bugs.md:49-52` shows detector safe output is `create-issue` (no PR creation in detector mode).

**Suggested improvement:** Align the homepage onboarding with behavior by either:
1. Switching homepage quick install to the chained example (`example-chained.yml`) when claiming auto-fix PR behavior, or
2. Updating homepage copy to detector-only behavior and adding an immediate "enable auto-fix by chaining" step next to the install command.

## Suggested Actions
- [ ] Update `docs/index.md` Bug Hunting row text or install command so they describe the same behavior.
- [ ] Add an explicit detector-vs-chained note in the homepage quick-install block for Bug Hunting.
- [ ] Keep homepage wording consistent with `docs/workflows/gh-agent-workflows/bugs.md` mode labels (Detector only vs Chained).

> [!NOTE]
>
> 🔒 Integrity filter blocked 3 items
>
> The following items were blocked because they don't meet the GitHub integrity level.
>
> - [#234](https://github.com/elastic/ai-github-actions/issues/234) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#114](https://github.com/elastic/ai-github-actions/issues/114) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#593](https://github.com/elastic/ai-github-actions/issues/593) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
>
> To allow these resources, lower `min-integrity` in your GitHub frontmatter:
>
> ```yaml
> tools:
> github:
> min-integrity: approved # merged | approved | unapproved | none
> ```
>
>

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

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