[dodeja]

Why

Handled tracking validation errors currently create generic upstream exceptions in Sentry. This produces alerts when the tool correctly asks for a valid container number or missing tracking input.

What changed

• Skip exception capture and flush for concrete ContainerCheckDigitError and TrackContainerError instances returned by track_container.
• Preserve actionable tool text, isError, and operator logs.
• Keep authentication, timeout, unknown validation, upstream, lookup, and name-spoofed errors captured.

Scope

Addresses the reporting behavior in DEV-13655 and DEV-12452. The existing duplicate-tracking fix in #440 and protocol support in #333 are unchanged. Credential/header scrubbing from #389 is unchanged.

Blast radius

Only the tracking tool's two explicit domain error classes change reporting behavior. This does not alter upstream requests, retries, authorization, or tool schemas.

Verification

• Real MCP/SDK protocol regressions: 12 failures before the fix; all 42 tracking tests pass after it.
• Formatting, lint, TypeScript, builds, generation checks, offline protocol smoke, and all offline workspace tests pass, including the Sentry credential-scrubbing pipeline.
• Full agent-verify remains blocked by the existing main inventory-scanner failure covered by fix(ci): compare advertised MCP tools with the feature map #446: 21 expected tools versus 14 discovered. Reproduced on untouched main; other verifier phases pass separately.

Draft pending resolution of the existing aggregate verification gate. No deployment or issue closure is included.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Confidence Score: 5/5

The PR appears safe to merge.

Summary

Stops reporting two expected tracking error classes to Sentry.

• Two expected tracking errors no longer go to Sentry.

No actionable issues were found. Tests were not run during this review.

_{Reviews (1) · Last reviewed commit: "fix(mcp): keep tracking validation out o..." · Reviewed by Greptile}

[vercel]

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

Project	Deployment	Actions	Updated
api	Ready	Preview	Oct 19, 2026 5:26am UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T05:27:32.974714Z	236f94a	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

Shadow risk calibration

Signal	Result	Authority
Path classifier	risk:high	Deterministic advisory policy
heuristic fallback	risk-shadow:high	Shadow only

Calibration result: agreement.

Shadow risk never blocks or enables merge. Keep it in observation mode until roughly 50 pull requests have human-reviewed labels, then calibrate before considering any policy use.