Skip to content

docs(coverage): remove Wilmington (NC) from the public terminal table (DEV-13448) - #474

Open
dodeja wants to merge 3 commits into
mainfrom
akshay/dev-13448-remove-wilmington-from-coverage
Open

dodeja wants to merge 3 commits into
mainfrom
akshay/dev-13448-remove-wilmington-from-coverage

Conversation

@dodeja

@dodeja dodeja commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

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 with credential_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

  • Removed L194 from docs/data/coverage/coverage.json, coverage-data.mdx, and tools/data/terminal-identifiers.json. Ran node tools/generate-coverage.mjs to 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.md is 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 --check shows no drift.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge.

Summary

Removes Wilmington (NC) from public terminal coverage until terminal data is available again.

  • Wilmington leaves the public direct-terminal coverage list.

Reviews (1) · Last reviewed commit: "docs(coverage): remove Wilmington (NC) f..." · Reviewed by Greptile

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>
@mintlify

mintlify Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
terminal49 🟢 Ready View Preview Nov 9, 2026, 12:59 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@vercel

vercel Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
api Ready Ready Preview Nov 9, 2026 12:59am UTC

Request Review

@linear-code

linear-code Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

DEV-13448

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T01:01:31.824878Z 18e4cc9 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 github-actions Bot added the risk-shadow:high Shadow-only risk signal: high label Oct 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Shadow risk calibration

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

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.

@github-actions github-actions Bot added the risk:unknown Advisory evidence unavailable or changed; no merge permission label Oct 19, 2026
@github-actions github-actions Bot added risk:medium Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Oct 19, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread docs/coverage/changelog.mdx Outdated

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">

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission risk:medium Advisory path risk; current-head human review needed and removed risk:medium Advisory path risk; current-head human review needed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Oct 19, 2026
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission risk:medium Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission risk:medium Advisory path risk; current-head human review needed labels Oct 31, 2026
@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:medium Advisory path risk; current-head human review needed labels Nov 9, 2026
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
@github-actions github-actions Bot removed the risk:unknown Advisory evidence unavailable or changed; no merge permission label Nov 9, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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">

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

This branch was successfully deployed

2 active deployments
Preview — 18e4cc99 Deployed Nov 9, 2026 by vercel[bot]
staging - docs — 18e4cc99 Deployed Nov 9, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:medium Advisory path risk; current-head human review needed risk-shadow:high Shadow-only risk signal: high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants