Rovo Agent hallucinating runbook summaries — fabricates steps not present on source Confluence page

[Akash Jha]

I'm using a Rovo Agent automation rule to retrieve Runbook Summaries from child Confluence pages linked under a parent page.

The agent correctly identifies and navigates to the child runbook links. However, the generated summaries contain fabricated content — steps, commands, and details that do NOT appear on the actual Confluence page.

Observations

Case 1: Summary is 100% hallucinated (Critical)

For the "Astro DC Disconnects" runbook, NONE of the steps in the agent's summary exist on the page:

| Agent's summary step | On actual page? |
|---|---|
| HugePages / `grep HugePages /proc/meminfo` | ❌ Fabricated |
| JVM Metaspace / classloader leaks | ❌ Fabricated |
| Java Flight Recorder / heap dump | ❌ Fabricated |
| Restart astro-2 | ❌ Fabricated |

**What's actually on the page:**
- DC disconnect ratio < 0.96 threshold
- `service:astro AND msg:"socket connection closed"` Kibana query
- Dashboards grouped by Node/Pod/AccountID
- Contacts: David King (SRE), Sean Hagan (DE)

The agent appears to have read the page content (it dumps it below the summary), then ignored it and generated a generic memory troubleshooting guide instead.

Case 2: Mix of real content + hallucinated commands

For the Kafka partition depth runbook:

| Detail | On actual page? | In agent summary? |
|---|---|---|
| 100,000 queue depth threshold | ✅ Yes | ❌ Not mentioned |
| Kibana query `msg:"finished processing stimulus"` | ✅ Yes | ✅ Yes |
| Saved viz `sre_kafka_impact_customer_list` | ✅ Yes | ❌ Missing |
| `kubectl rollout restart sts dejavu` | ❌ NOT on page | ✅ Included |
| `kubectl scale sts dejavu --replicas=30` | ❌ NOT on page | ✅ Included |
| `kafka-consumer-groups.sh` command | ❌ NOT on page | ✅ Included |

Environment
- Atlassian Cloud (Jira + Confluence)
- Rovo Agent invoked via Jira Automation rule

Question
1. Is there a way to constrain the Rovo Agent to ONLY summarize content that exists on the page (no generation/inference)?
2. Are there known prompt patterns to prevent hallucination when summarizing Confluence pages?
3. Is this a known limitation of Rovo's current Confluence page reading capability?