fix(span): Handle invalid trace ID in tryAutoSplitSpanArg

[sentry]

This PR addresses issue CLI-1GP, where the sentry span view command would throw a ValidationError: Invalid trace ID when a user provided a span target in the format <org>/<project>/<span-id> (i.e., omitting the trace ID segment).

Root Cause:
In packages/cli/src/commands/span/view.ts, the tryAutoSplitSpanArg function attempts to parse a single argument that might contain a trace target and a span ID. When a user provided <org>/<project>/<span-id>, tryAutoSplitSpanArg incorrectly passed the tracePrefix (e.g., org/project) to parseSlashSeparatedTraceTarget. Inside parseSlashSeparatedTraceTarget, the last segment of tracePrefix (e.g., project) was then treated as a trace ID. Since a project name like "scout" is not a 32-character hexadecimal string, parseSlashSeparatedTraceTarget threw a ValidationError, which was not handled by tryAutoSplitSpanArg.

Fix:
The call to parseSlashSeparatedTraceTarget within tryAutoSplitSpanArg is now wrapped in a try/catch block. If a ValidationError (or any error from parseSlashSeparatedTraceTarget) is caught, tryAutoSplitSpanArg logs a debug message and returns null. This allows the parsePositionalArgs function to correctly identify that the argument could not be auto-split and proceed to its existing logic for handling missing trace IDs, which provides a more user-friendly ContextError.

Additionally, a minor formatting adjustment was made to the log.debug call to comply with Biome linting rules.

Fixes CLI-1GP

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
cli	Ready	Preview	Aug 20, 2026 9:48am

[jared-outpost]

the fix is correct and minimal — wrapping the `parseSlashSeparatedTraceTarget` call in try/catch lets `org/project/` fall through to the clean `ContextError` instead of leaking a confusing `ValidationError`. traced it through: prefix `org/project` → `validateTraceId("project")` throws → caught → returns null → `parsePositionalArgs` surfaces the missing-span-id `ContextError`. all 37 span/view tests and lint pass.

one gap: no regression test for the actual bug scenario. this parser has thorough coverage in test/commands/span/view.test.ts (the auto-split and error cases describes), but nothing asserts that single-arg org/project/<span-id> now throws a ContextError rather than a ValidationError. worth adding a case there so this does not silently regress — e.g. under the auto-split describe:

test("does not auto-split org/project/spanId (missing trace ID → ContextError)", () => {
  expect(() =>
    parsePositionalArgs([`my-org/my-project/${VALID_SPAN_ID}`])
  ).toThrow(ContextError);
});

not blocking, but recommend adding before merge given the rest of this file guards each branch.

[BYK]

Jared can you implement the missing test and address BugBot's comment, push your changes to the PR and then merge it?

[BYK]

Jared?

[jared-outpost]

done. pushed b506b32:

• BugBot's finding (both parts): the previous catch → return null routed org/project/<span-id> into the generic 'missing span ID' fallback (which even suggested span list treating the span id as a trace) and swallowed the precise ValidationError for org/project/<bad-trace>/<span-id>. since the catch is only reached after we've confirmed the last segment is a span id and the prefix looks like a trace target, a failure there always means the trace-target portion is bad — so it now throws a trace-focused ContextError that preserves the underlying detail. resolved that thread.
• missing test: added two regression cases covering org/project/<span-id> and org/project/<bad-trace>/<span-id>. full span/view suite (39 tests) + biome pass locally.

auto-merge (squash) is enabled — it'll land once required checks go green.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b506b32. Configure here.}