[alosec]

Targets main. Originally stacked on #404, which closed unmerged; its dashboard definitions reached main separately, so this is now the single commit rebased onto main.

Why

customer-v2 lfd-next-3-days ("Which containers have a last free day in the next 3 days?") answered 93 against a reference of 14. On Sodor staging:

Query (actively tracked)	Total
pickup_lfd today → +3 days, no status filter (what the agent did)	93
same, current_status=available,not_available,grounded	14 (reference)
past-due LFD at terminal (pickup_lfd <today)	694
arrival today → +10 days	34 (reference)

The query-guidance resource also contradicted #398's definitions: it described "discharged but not picked up" as pod_discharged_at @exists + picked_up_at @not_exists, and demurrage risk as LFD bounds instead of the Containers at Risk set.

What

• list_containers description: next-N-day LFD = still at the terminal + pickup_lfd [">=today", "<=N.days.from_now"]; past-due is separate; arrivals use arrival with the same bounds; "next N days" includes today and day N; today is the API server's UTC date (relative and absolute dates differ after midnight UTC: 11 vs 14 when I checked), so the agent states the dates it used.
• terminal49://docs/mcp-query-guidance: same definitions; drops the contradicting recipes.
• New guidance test pins the definitions.

Tests

MCP 445 passed on current main (2 new). vp run check and vp run build pass.

🤖 Generated with Claude Code

---

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

Confidence Score: 5/5

This PR appears safe to merge.

Summary

Aligns MCP query guidance with the dashboard definitions.

• Container status and demurrage guidance matches the dashboard.
• LFD and arrival windows use clear date bounds and scope.

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

_{Reviews (1) · Last reviewed commit: "chore: restore main's Postman collection" · 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

[dodeja]

Rebased the single commit onto main (signed, now 1bca2ee) and retargeted the base from feat/mcp-tracked-default (dead since #404 closed) to main. The net diff against main is the original three files. The contradicting discharged-not-picked-up recipe (pod_discharged_at @exists + picked_up_at @not_exists) stays removed, and the new guidance test asserts it is absent.

The force-push made the Postman workflow compare against the old base, so github-actions[bot] pushed b99d26d, which only reshuffled generated IDs and examples. c22b8a7 restores main's collection, so the PR does not touch it.

When merging: b99d26d's message contains [skip ci]. A squash merge copies it into the squash message, which would skip CI, Postman and release-please on main. Delete that line from the squash message before confirming.

Local on the rebased branch: vp run check, vp run build, MCP tests (445 passed, 2 new), MCP filter-schema drift (clean), eval:check and MCP lint all pass.

[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:28:08.000291Z	1271bc6	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:medium	Shadow only

Calibration result: disagreement (high vs medium).

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.