v0.13.0 - Coverage closure

[AnthonyPuggs]

Release v0.13.0 is focused on coverage-closure and surface-cleanup.

This release does not broaden the server to new sources or new MCP tools. Instead, it closes a small number of high-value ABS coverage gaps, removes misleading runtime placeholders, and tightens the release path ahead of the RC cycle.

Highlights

• Added a dedicated live ABS catalogue entry for building approvals: BUILDING_APPROVALS
• Added one new semantic shortcut: dwelling_approvals
• Re-activated RT after live validation confirmed the ABS retail trade dataflow is current again
• Removed unwired placeholder variants from the runtime catalogue and MCP resources
• Added maintainer release artefacts including docs/contributing.md, docs/migration-v0.13.0.md, and a checked-in FastMCP client smoke script

What Changed

Added

• BUILDING_APPROVALS, backed by live ABS dataflow BA_GCCSA
• dwelling_approvals, resolving to BUILDING_APPROVALS.headline_approvals
• docs/contributing.md
• docs/migration-v0.13.0.md
• scripts/mcp_client_smoke.py for pre-tag stdio client verification

Changed

• Runtime catalogue entries now expose only fully wired variants
• Placeholder ABS variants with no abs_key and placeholder RBA variants with no rba_series_ids are no longer public at runtime
• RT is live again and no longer suppressed from ordinary discovery
• BUILDING_ACTIVITY no longer carries building approvals aliasing now that approvals have a dedicated live entry

MCP Surface

There are no new MCP tools in v0.13.0, and the retrieval response schema is unchanged.

The public MCP tools remain:

• search_datasets
• list_catalogue
• get_abs_dataset_structure
• get_abs_data
• list_rba_tables
• get_rba_table
• get_economic_series

Compatibility Notes

This release includes one intentional discovery-surface cleanup:

• placeholder variant names that never had a live upstream binding are no longer exposed through runtime resources or accepted as valid semantic variants
• if you previously relied on one of those placeholder names, it will now be treated as an unknown variant until a real wired binding is added

This is a surface-cleanup change, not a retrieval-contract change.

Deferred

• RPPI remains ceased in v0.13.0
• a like-for-like live replacement was not cleanly auditable against the current time-series contract, so it was left out on purpose rather than replaced with an approximate substitute

Validation

This release was verified with:

• env UV_CACHE_DIR=.uv-cache RUFF_CACHE_DIR=/tmp/ausecon-ruff-cache uv run ruff check src tests integration_tests scripts
• env UV_CACHE_DIR=.uv-cache uv run pytest
• env UV_CACHE_DIR=.uv-cache uv run pytest integration_tests/ -v
• env UV_CACHE_DIR=.uv-cache uv run python scripts/audit_catalogue.py
• env UV_CACHE_DIR=.uv-cache uv run python scripts/mcp_client_smoke.py

Why This Release Matters

v0.12.0 froze the retrieval contract. v0.13.0 cleans up the remaining public discovery surface so users see live, intentional coverage rather than dead aliases or unwired placeholders.

This is intended to be the last pre-RC feature release before the move to v0.14.0-rc1.

---

This discussion was created from the release v0.13.0 - Coverage closure.