v0.1.3

Bug Fixes

• E-commerce revenue metrics — the catalog shipped revenue metric ids without the required <currency> token, so every e-commerce revenue query failed with "incorrectly specified metric" (4002). They now use ym:s:ecommerce<currency>ConvertedRevenue (and the per-purchase/per-visit variants), verified against the live API.

Features

• Time-series date axis — run_timeseries now returns time_axis.dates, one calendar-aligned date per value (plus interval_count), so you no longer reconstruct the axis with error-prone date1 + index math. Labels are bucket starts matching how Metrica buckets /bytime (week = Monday; month/quarter/year = period start), correct even for a mid-period start date.
• Actionable tool errors — errors now carry structuredContent (status and error types) plus a recovery hint: re-authenticate on an expired/invalid token, back off when throttled, with distinct timeout and network messages. Request timeouts and network failures map to a typed, retryable error instead of an opaque one.

Improvements

• Pagination awareness — report responses warn when rows remain after the returned page (offset-aware, so the final page stays quiet) and expose meta.total_rows_approximate.
• Clearer comparisons — run_comparison documents its delta convention (delta = B − A, segment A is the baseline) in the tool description and a delta_convention field.
• Metadata guidance — get_metadata now flags the <currency> token for revenue metrics and recommends pulling ym:s:robotPercentage when analyzing raw traffic.

Housekeeping

• Release notes now live in GitHub Releases; dropped CHANGELOG.md and the inert .dxt manifest.json.

Full Changelog: v0.1.2...v0.1.3