Tighten comments across PR 5711 (no behaviour change)
Audited every comment added by this PR; condensed multi-paragraph
docstrings and inline blocks to 1-2 lines where the WHY survives.
Files touched: 6 backend + 7 frontend. Net -148 lines.
- external_provider.py: -80 (docstring + stop_sequences + compaction)
- chat-settings-sheet.tsx: -70 (InfoHint tooltips + section headers)
- routes/inference.py: -54 (parallel_tool_calls cap comments)
- provider-capabilities.ts: -108 (stop-cap table, gemini bucket,
service_tier resolver, max-output cap header)
- chat-adapter.ts: -27 (sampling forwarding stanza)
- providers.py: -24 (kimi reasoning class, deepseek aliases)
- llama_cpp.py: -24 (payload builder shared header)
- models/inference.py: -28 (Pydantic Field descriptions)
- chat-settings-storage.ts: -23 (nullable handling comments)
- stop-sequences-input.tsx: -23 (JSDoc + chip-key + draft-commit)
- anthropic_compat.py: -9 (serial tool-call gate)
- types/runtime.ts: -12 (DRY JSDoc, null convention header)
- types/api.ts: -6 (service_tier JSDoc)
Tightening rules applied:
- Removed em-dashes everywhere a comment was rewritten.
- Kept every external doc URL (Anthropic, OpenAI, vLLM, llama.cpp,
Ollama, OpenRouter, Mistral, DeepSeek, Gemini, Kimi).
- Collapsed "silently dropped on unsupported routes" prose since the
bucket-comment at the top of each capability table already states it.
- Removed restated rationale prose in comment blocks where the field
name plus the master rule already encodes the WHY.
393/393 backend tests pass (test_sampling_params_routing 65, plus
anthropic / openai / gemini / llama-server suites). Frontend tsc +
vite build clean.
1add4dbd0e