feat(upload): link to test collection pages when a collection id is passed

[TylerJang27]

Example run here:

and successful redirect

Summary

When --test-collection-id / TRUNK_TEST_COLLECTION_ID is passed, end-of-run failure links (the ⤷ table and the quarantine "Learn more" log lines) now use the collection short-link form:

https://app.trunk.io/{org}/flaky-tests/collections/{short_id}/t/{test_case_id}?repo={owner}/{name}

The webapp resolves the repo name to a repo id server-side and redirects to the canonical collection test detail page (/collections/{short_id}/tests/{repo_id}_{test_case_id}). No RPC or response changes — the short id is a client-side input, so the CLI already has everything it needs.

Companion webapp PR (must deploy first, it hosts the redirect page): trunk-io/trunk2#5342

Behavior

collection id passed	--hide-test-collection-links / TRUNK_HIDE_TEST_COLLECTION_LINKS=true	link
yes	no	/collections/{short_id}/t/{test_case_id}?repo=...
yes	yes	legacy /flaky-tests/test/{test_case_id}?repo=...
no	—	legacy (unchanged)

The hide flag follows the standard clap bool-flag pattern (same as --show-failure-messages) and is a rendering preference only — it's threaded to the two URL-generation sites and never alters upload behavior. Intended for orgs dual-writing repo + collection uploads that want the old link experience.

Test plan

• cargo test -p api — URL unit tests for both link forms
• cargo test -p trunk-analytics-cli — full suite green (96 tests), including 3 new integration tests covering the gate matrix above and the exported-but-blank TRUNK_TEST_COLLECTION_ID edge

[trunk-io]

😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details.

[trunk-staging-io]

   

Failed Test	Failure Summary	Logs
pending_quarantine_test should be quarantined when run with variant	A test marked as pending was expected to fail but unexpectedly passed.	Logs ↗︎
variant_quarantine_test should be quarantined when run with variant	A test expected the sum of 2 + 2 to be 5, but it was actually 4, indicating a failing assertion.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.41%. Comparing base (c1423be) to head (0a36b34).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1165      +/-   ##
==========================================
+ Coverage   83.13%   83.41%   +0.28%     
==========================================
  Files          72       72              
  Lines       16197    16241      +44     
==========================================
+ Hits        13465    13548      +83     
+ Misses       2732     2693      -39     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trunk-io]

   

View Full Report ↗︎ ⋅ Docs

[TylerJang27]

⚠️ DONOTLAND commit on this branch: 52d7ddd adds an intentionally failing test (api::urls::tests::donotland_intentional_failure_to_preview_collection_link) so the CI upload steps (built CLI + --test-collection-id) print the new collection short link in their end-of-run output. Check the "Upload results to staging using built CLI" step logs for a ⤷ https://app.trunk-staging.io/trunk-staging-org/flaky-tests/collections/2tYJWMu7/t/...?repo=trunk-io/analytics-cli line (and Gtnr7BWl / prod EWhNPVic in the sibling steps). Revert 52d7ddd before merging.

[TylerJang27]

✅ DONOTLAND commit reverted in 0a36b34 — the branch is back to only the real change. The link preview is visible in the CI runs from the 52d7ddd push.