Replace every placeholder before requesting review. Keep the PR small enough to
review in one pass.

For the first contribution flow, use
CONTRIBUTING.md#first-pr-recipe; it keeps the first contribution small and reviewable.
Please also follow CODE_OF_CONDUCT.md in PR discussions and reviews.
For security-sensitive changes or private trace data, follow SECURITY.md before
sharing details publicly.

Relevant stack guides when changing an adapter, example, or stack-specific doc:

• Browser Use guide: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
• Stagehand guide: https://aaronlab.github.io/browsertrace/stagehand-debugging.html
• Skyvern guide: https://aaronlab.github.io/browsertrace/skyvern-debugging.html
• Playwright + LLM guide: https://aaronlab.github.io/browsertrace/playwright-llm-debugging.html
• Computer-use guide: https://aaronlab.github.io/browsertrace/computer-use-agent-debugging.html

When touching adapter docs, examples, exports, or troubleshooting copy, keep
the AOS mapping note research-only. BrowserTrace is not making an AOS
compliance claim yet. Current mapping research connects BrowserTrace fields to
tool request/result records, step correlation, URI-style screenshot/video
artifacts, URL metadata, model I/O summaries, and explicit redaction state.
Track the research in #237.

Summary

• What changed: Added a concise failure-patterns overview link to the stack-specific debugging guides in examples/README.md.
• Why it matters: Helps readers choose the matching example or debugging guide for common BrowserTrace agent failures.

Linked Issue

• Fixes Docs: link failure patterns from examples guide #340

Test Plan

• I ran uv run --python 3.11 --extra dev pytest -q
• I ran git diff --check
• I checked git diff --stat and git diff --summary for unexpected deleted or renamed files.
• I included the exact error/output for checks run below.

Additional targeted check run:

uv run --python 3.11 --extra dev pytest tests/test_metadata.py -q

Result: 351 passed in 0.73s.

Demo / Screenshots

Docs-only change; no UI screenshots or trace export needed.