v0.2.0: Ten output fields become optional, and Eurostat's silence stops being fabricated as zero
Ten output fields become optional, and Eurostat's silence stops being fabricated as zero
- Breaking: 10 fields move required → optional across 3 schemas — eurostat_get_dataset_info's timeRange.start/end, obsCount, lastUpdated; the eurostat://dataset/{dataset_code} resource's same 4 fields; eurostat_query_dataset's timeRange.start/end (#30, #33)
- get_dataset_info's time-dimension valuesCount now reflects the dataset's real period count instead of a single-period artifact, at the cost of one bounded extra request (#21)
- get_dataset_info's async_response error is no longer retryable — its recovery hint now points at eurostat_search_datasets/eurostat_browse_themes/eurostat_get_dimension_values (#31)
- get_dimension_values rejects geo_level paired with a non-geo dimension instead of silently ignoring it (#25)
- query_dataset drops zero-length filter arrays before building the request and echoes the filters actually applied via a new appliedFilters field (#22)
- docs: design.md and README.md corrected for stale error-code labels, single-request description, and mutual-exclusion wording