docs: document Re-Run (Replay and Reproduce) for Automation tests

[chaitanyas-maker]

Supersedes #3231 (rebased onto current stage, single clean commit, note reworked to match house style).

Closes TE-20754.

What

The Re-Run button on the Automation Test Detail Page, and its Replay and Reproduce options, had no documentation anywhere. Every existing hit for "rerun"/"replay" describes a different feature (HyperExecute retryOnFailure, LT Debug record-and-replay, Browser Cloud session replay), so users had nothing to land on.

Requested by @aditagrawal in #customer_issues.

Changes

• New page docs/rerun-automation-tests.md covering both options, the HAR prerequisite, and a comparison table.
• Sidebar registered under Manage Your Runs in sidebars.js, after change-individual-test-details.
• Cross-link from the Test Summary section of Explore the Automation Dashboard, which listed the test action buttons but omitted Re-Run.
• Generated artifacts (static/docs/*, llms.txt) included, since this repo commits them. Without these the page would be missing from the LLM-facing docs index.

Not GA

Re-Run is not GAed, confirmed by @akshayverma on 2026-07-14:

"Nope this not GAed."
"Yes add a note. There were phases planned which was never picked again."

The page carries a Limited Availability note using the existing house pattern (:::note + 24/7 chat support widget + support@testmuai.com), matching manual-app-profiling.md and kaneai-test-run-instance-view.md.

Open question for reviewers: should this merge now, or wait for GA? The customer-facing gap is real, which is why I lean toward merging with the note.

Verification

Reproduce's eligibility was verified against the live dashboard, not inferred. Without HAR logs the option is greyed out with:

No Network Logs found, use network.full.har:true to replicate the test states.

Cross-checked against PRD: Web Test Reproduce and Debug Tool, which confirms Reproduce replays network and DOM data and is limited to tests with pass/fail/completed status.

Rendering verified locally: note, table, code block, tooltip quote, sidebar entry, and all four internal links resolve.

Deliberately not documented

• Whether a re-run creates a new build or nests under the original. No source confirms this.
• Whether Replay reuses or allows modifying the original capabilities. The PRD's sibling feature ("Retry") allows modification, but those phases were "never picked again", so I state only what is confirmed.
• PRD-only features (playback speed, breakpoints, domain mapping) that may never have shipped.

Happy to add any of the above once someone confirms the shipped behavior.

Separate pre-existing bug (not fixed here)

src/theme/Admonition/index.js only handles info/danger/warning/tip/note and returns undefined otherwise, so :::caution (42 uses) and :::important (5 uses) render as nothing on the live site. Confirmed on /support/docs/authentication/, where the :::important block documenting auth precedence is invisible. Worth its own ticket.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TiHy6iYuY7mWJ51p5v6Wza