v0.3.1: Overpass load discipline and error classification
Overpass load discipline and error classification
- upstream_error surfaces any Overpass runtime remark that is not a timeout or OOM, instead of returning an empty success (#41)
- out-of-memory remarks reach result_too_large instead of being misclassified as a timeout (#42)
- HTML throttle pages fail fast as rate_limited instead of being resubmitted up to 4x (#44)
- OSM_OVERPASS_MAX_CONCURRENCY caps concurrent Overpass submissions (default 2), queuing past the cap instead of piling onto the endpoint
- framework skills, docs, and dependency-specifier checks synced to the current template
- deps:
@cyanheads/mcp-ts-core^0.10.17 -> ^0.11.0