docs(coverage): add changelog entry for Seaboard Marine public listing

[claude]

Requested by Namita Dodeja · Slack thread

Before: The coverage changelog has no entry for Seaboard Marine becoming a public carrier, even though #432 made the change. The only mention is the 2026-08-14 entry, which lists Seaboard Marine as account-enabled.

After: A 2026-10-14 entry announces only the new support: Seaboard Marine (SMLU) is now supported, trackable by bill of lading, booking number, or container number (enter the master bill of lading without the SMLU prefix). It does not describe changes to existing carrier support.

This adds the missing changelog entry for the Seaboard Marine public listing.

How: Docs-only edit to docs/coverage/changelog.mdx, placed newest-first above the October 9 entry and matching the existing <Update> format. Supersedes closed #429, which also carried data changes that are now on main via #432. npm run test:coverage and node tools/generate-coverage.mjs --check pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GvpwGFSoR7Ycun5PNufyGz

---

Generated by Claude Code

---

<source media="(prefers-color-scheme: dark)" srcset="https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg"><source media="(prefers-color-scheme: light)" srcset="https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-light-v3.svg"><img alt="View with [code]smith" src="https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg"> <a href="https://backend.blacksmith.sh/track/enable-autofix?expires=1794600031&installation_model_id=18852&pr_number=434&ref=codesmith_pr_footer&repository=Terminal49%2FAPI&return_to=https%3A%2F%2Fgithub.com%2FTerminal49%2FAPI%2Fpull%2F434&signature=61fe979e0e2a59981de96fa57be46b2715e2b0dd525bff2f9aae0a7affd3f940"><picture><source media="(prefers-color-scheme: dark)" srcset="https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-light.svg"><img alt="Autofix with [code]smith" src="https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg">
^{Need help on this PR? Tag @codesmith-bot with what you need.}

[mintlify]

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

Project	Status	Preview	Updated
terminal49	🟢 Ready	View Preview	Oct 14, 2026, 9:45 PM

[vercel]

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

Project	Deployment	Actions	Updated
api	Ready	Preview	Oct 14, 2026 9:46pm UTC

[claude]

"MCP preview 2026-07-28" is red here for the same reason as on main (run 38606174332) and #429: packages/mcp/eval/tools.eval.ts:138 finds no shipment or container fixtures on the account behind MCP_EVAL_TOKEN. This PR only edits docs/coverage/changelog.mdx, so it can't affect that job. Everything else on this head passes, including "Coverage generators and drift checks". I'm not changing anything here; the fix is to point that secret at an account with tracked data (or set MCP_EVAL_ALLOW_SPARSE=1).

---

Generated by Claude Code

[greptile-apps]

PR author is in the excluded authors list.

[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-17T06:55:42.800081Z	4a9a357	Draft marked ready

ℹ️ 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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4a9a357e3d

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Tell booking users to submit their booking number

When a user tracks by booking number, this instruction incorrectly tells them to enter a master bill of lading, even though the preceding bullet and the tracking-request guide treat booking numbers and master bills of lading as distinct request numbers. This can cause users following the changelog to submit the wrong identifier; either limit the prefix instruction to bill-of-lading lookups or explicitly say what booking users should enter.

Useful? React with 👍 / 👎.