fix(ai): warn first when an MCP call's argument was ignored - #1386

🟢 Confidence 9/10 · safe to merge
Both earlier findings are demonstrably fixed in the two files that changed, and the window-suggestion logic is pinned by tests I re-derived by hand.
_{quality 100/100 · no findings · tests covered · risk medium}

Ignored-argument reports move from Note: into a new ToolDoc.warnings rendered first under the title, and a window-shaped unknown key now suggests both bounds. The two earlier findings are fixed; safe to merge.

• argumentWarnings replaces argumentNotices and renders as Warning: above scope (tool-doc.ts:127)
• UnknownArgument.suggestions carries both window bounds for a time_range-like key
• A closer non-bound match now wins over the window guess (decode-issues.ts:105)

Fixed since the last review

• ✅ F1 · argumentNotices rename leaves pr-review-local.ts importing a missing export
• ✅ F2 · suggestParameters drops a closer match for any key containing a window word

Production impact

_{6b0f968 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.}