v0.14.0 - MCP contract hardening, prompt reliability, and analytic metadata

[AnthonyPuggs]

Summary

This release hardens the MCP server contract and improves the economic reliability of returned data. It adds richer generated input schemas, wires retrieval tools to the checked-in response schema, preserves more ABS analytic metadata, fixes prompt templates that could previously suggest invalid tool calls, and improves multi-series filtering semantics.

Highlights

• Added stronger MCP input schemas using constrained argument types, including source/category enums, date and period patterns, and numeric bounds.
• Added retrieval output schemas for get_abs_data, get_rba_table, and get_economic_series, backed by schemas/response.schema.json.
• Expanded the response schema with clearer metadata requirements, field descriptions, ABS period/date validation, and optional ABS analytic fields.
• Fixed prompt templates so generated calls use source-appropriate dates and parameters, including ABS start_period, RBA ISO dates, and valid RBA categories.
• Changed last_n filtering for multi-series results to return the last N observations per series rather than N observations globally.
• Preserved ABS UNIT_MULT, DECIMALS, BASE_PERIOD, and OBS_COMMENT as structured series/observation metadata.
• Fixed ABS structure lookup for catalogue entries that use separate structure IDs, including LF_UNDER / DS_LF_UNDER.
• Improved discovery for common economist wording such as real GDP.
• Fixed integration-test cache isolation so local runs do not touch the user’s real platform cache.
• Removed tracked local Claude session metadata and updated public docs that had drifted from runtime behaviour.
• Updated smoke and maintenance scripts for the richer FastMCP structured-output behaviour.

Behaviour Notes

• last_n now applies per series. For broad ABS requests and multi-component concepts such as housing credit, clients will receive recent observations for each returned series instead of only the final rows of the flattened payload.
• The JSON response shape is intended to remain compatible, but clients that introspect MCP tool metadata will now see stricter input and output schemas.
• pydantic is now a direct runtime dependency because tool argument schemas use explicit field constraints.

Validation

• uv run pytest: 443 passed.
• uv run ruff check src tests integration_tests scripts: passed.
• uv run pytest integration_tests/ -q: 16 passed.
• uv run python scripts/audit_catalogue.py: no drifted or disappeared curated ABS/RBA entries.
• uv run python scripts/mcp_client_smoke.py: mcp-smoke-ok.
• uv build: source distribution and wheel built successfully.

---

This discussion was created from the release v0.14.0 - MCP contract hardening, prompt reliability, and analytic metadata.