Add analytics-cli upload troubleshooting and update install path

[samgutentag]

Summary

• Add a Troubleshooting section to flaky-tests/reference/cli-reference.mdx covering the four most-repeated upload issues from customer Slack: "no tests found" (Playwright/Storybook aborts, Bazel BEP JSON, empty globs), 403 from SSH-alias repo-URL inference, validate "name too short"/"classname too short" warnings, and how to use upload when post-processing JUnit XML from an external runner.
• Add a Warning callout clarifying that the trunk-analytics-cli install path is github.com/trunk-io/analytics-cli/releases, not get.trunk.io / trunk.io/releases (which install the legacy launcher used by Code Quality).
• Add an upload vs test Info callout in the Running and Quarantining section so customers wrapping an external runner pick the right command on the first try.

Why

Sourced from customer feedback mining (cluster analytics-cli-upload-edge-cases, verdict partial, 9 pairs across 6 customers, first-class IA candidate). The CLI reference documents the happy path; customers hit recurring upload issues that have well-known workarounds but no documented troubleshooting surface.

Items flagged for review

• Bazel BEP JSON parser status. The workaround documented here is "use the binary BEP" based on the customer threads. Confirm whether the JSON ingestion bug has shipped a fix — if so, this section should be softened or removed.
• validate source attribution. The page says Trunk does not yet surface the originating file for "name too short" / "classname too short" warnings. Confirm whether better attribution has shipped before merge, and update if so.
• Install path messaging. The Warning callout treats get.trunk.io / trunk.io/releases as legacy for Flaky Tests purposes. Confirm this framing is accurate and doesn't conflict with Code Quality docs.
• Page placement (chose A). Added troubleshooting inline in the CLI reference rather than spinning up a new page. If the section grows, we can split it into flaky-tests/reference/cli-troubleshooting.mdx later.

Customer signal

• Cluster: analytics-cli-upload-edge-cases (verdict: partial, 9 pairs / 6 customers, first-class IA candidate)
• Channels: trunk-retool, trunk-most, trunk-healthie, trunk-brex
• Source threads (full list in findings/clusters/analytics-cli-upload-edge-cases.json):
  • BEP JSON parser bug
  • SSH host-alias 403
  • Playwright abort -> no-tests-found
  • validate classname-too-short warnings
  • validate name-too-short
  • trunk-launcher deprecation for Flaky Tests
  • upload vs test command

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
trunk	🟢 Ready	View Preview	May 20, 2026, 11:13 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.