[teeohhem]

Summary

Screenshots or video

Before	After

How to reproduce

Starting point:

On main:

On this branch:

How to test on Vercel preview

Preview routes:

Steps:

References

• Linear Issue:
• Related PRs:

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
clickstack-oss	Ready	Preview	Nov 6, 2026 10:53pm UTC
clickstack-storybook	Ready	Preview	Nov 6, 2026 10:53pm UTC
hyperdx-oss	Building	Preview	Nov 6, 2026 10:53pm UTC

[github-actions]

🟢 Tier 1 — Trivial

Docs, images, lock files, a dependency bump, or an automated release. No functional code changes detected.

Why this tier:

• All files are docs / images / lock files

Review process: Auto-merge once CI passes. No human review required.
SLA: Resolves automatically.

Stats

• Production files changed: 0
• Production lines changed: 0
• Branch: tom/vercel-preview-test
• Author: teeohhem

To override this classification, remove the review/tier-1 label and apply a different review/tier-* label. Manual overrides are preserved on subsequent pushes.

[github-actions]

PR Review

✅ No issues found.

[github-actions]

Duplicate code analysis

No new duplicate code introduced by this PR.

---

jscpd compared this branch against origin/main
across app, api and common-utils. Only new clones are listed; the codebase
currently holds 110 in total (1.21%).
Run yarn dupes locally to reproduce, or yarn dupes:all for the full picture.

[github-actions]

Deep Review

✅ No critical issues found.

This PR adds a single one-line throwaway markdown file with no executable code, logic, tests, or security/data surface. There is nothing that introduces a production failure mode.

🔵 P3 nitpicks (1)

• packages/app/VERCEL_PREVIEW_TEST.md:1 — The file declares itself a throwaway intended only to trigger a preview build, so merging this PR would commit an inert placeholder file into the repository.
  • Fix: Remove the file before merge, or close the PR once the preview build has been validated.

---

Reviewers (5): correctness, testing, maintainability, project-standards, previous-comments

Testing gaps: None — the change is a non-code markdown file and requires no test coverage.

_{No finding blocks merge automatically. A maintainer will expect P0/P1 findings in code this PR changes to be fixed; P2/P3 are your call -- fix or reply. Never fix findings about surrounding code here; reply instead. Do not widen the PR. How to respond}

[github-actions]

E2E Test Results

✅ All tests passed • 464 passed • 1 skipped • 1261s

Status	Count
✅ Passed	464
❌ Failed	0
⚠️ Flaky	0
⏭️ Skipped	1

Tests ran across 4 shards in parallel.

View full report →