Repository navigation
Conversation
The L194 integration has had no successful scrapes in 30 days because no working NC Ports portal login is available. List Wilmington with the other terminals that are not currently supported until terminal data flows again. Refs DEV-13448 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Shadow risk calibration
Calibration result: disagreement (medium vs high). 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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6843b4e427
ℹ️ 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".
|
|
||
| For product and API changes, see the [API changelog](/updates/home). | ||
|
|
||
| <Update label="October 18, 2026" description="Wilmington (NC) removed from the public terminal table"> |
There was a problem hiding this comment.
Add an explicit degradation status
This entry documents an ongoing data-source degradation but never identifies its status as investigating, degraded, resolved, or monitoring, as required by the repository's changelog guidance. When readers audit Wilmington coverage later, the omission makes it harder to distinguish an active degradation from a historical removal; add the current status explicitly and update it when the integration recovers.
AGENTS.md reference: AGENTS.md:L60-L62
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
The entry already opens with "Status at this update: degraded." (added in e8f2a40, after this review). In 18e4cc9 I merged main and resolved the conflicts with the November 2 terminal expansion. The entry keeps the degraded status. It is now dated November 9 and says 160 terminals, down from 161, so it sits above the expansion entry.
Generated by Claude Code
Resolve conflicts with the November 2 terminal expansion (#501). Main's coverage data is kept, L194 is removed from it again, and the generated coverage files are rebuilt. The count becomes 160, down from 161, and the changelog entry is re-dated to November 9 so it follows the expansion. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V8cPhktNpguVMk39bAstza
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 18e4cc9978
ℹ️ 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".
|
|
||
| For product and API changes, see the [API changelog](/updates/home). | ||
|
|
||
| <Update label="November 9, 2026" description="Wilmington (NC) removed from the public terminal table"> |
There was a problem hiding this comment.
Advance the terminal snapshot date for the removal
Because this November 9 update changes the canonical terminal set, leaving coverage.json.updatedOnByType.terminals at 2026-11-02 causes every regenerated terminal export and the public page's “Last updated” text to claim the removed Wilmington entry is still part of a November 2 snapshot. Consumers using that timestamp for cache invalidation or freshness checks cannot detect this coverage change; advance the terminal date to November 9 and regenerate the outputs and date assertion.
AGENTS.md reference: AGENTS.md:L60-L62
Useful? React with 👍 / 👎.
Summary
Removes Port of Wilmington Container Terminal (
L194, Wilmington NC) from the public terminal coverage table. It's now listed with the other terminals that are not currently supported. This is the docs half of DEV-13448.Why
The Wilmington integration (
terminal.L194.web, NC Ports customer portal) has had 0 successful scrapes out of 7,675 in 30 days. There's no working portal login, so every scrape fails withcredential_required. The docs shouldn't claim coverage we aren't delivering.Companion code change: Terminal49/t49#4564 marks the integration as requiring a login, so the failing scrapes stop. Wilmington comes back into this table once someone adds a working NC Ports login and scrapes succeed.
Changes
docs/data/coverage/coverage.json,coverage-data.mdx, andtools/data/terminal-identifiers.json. Rannode tools/generate-coverage.mjsto regenerate the terminal JSON, CSV, MDX, and feature snippets.docs/coverage/terminals.mdx: added Wilmington (NC) to the "not currently supported" sentence.docs/coverage/home.mdx: changed the terminal count from 138 to 137.docs/coverage/changelog.mdx: added an October 18 entry recording the removal.tools/generate-coverage.test.mjs: updated the expected counts. Terminals go from 138 to 137, and terminals with unknown pickup availability go from 22 to 21.tools/data/terminal-identifiers.mdis left unchanged because it's the dated identifier verification from 2026-10-13.Test plan
npm run test:coverage: 45/45 pass, and the generator--checkshows no drift.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.

Confidence Score: 5/5
The PR appears safe to merge.Summary
Removes Wilmington (NC) from public terminal coverage until terminal data is available again.
Reviews (1) · Last reviewed commit: "docs(coverage): remove Wilmington (NC) f..." · Reviewed by Greptile