v4.3.1

Changelog - v4.3.1

All notable changes to the law-scrapper-mcp project for version v4.3.1 will be documented in this file.

The format is based on Keep a Changelog 1.1.0,
and this project adheres to Semantic Versioning 2.0.0.

[4.3.1] - 2026-09-06

Two error-message findings deferred from the v4.3.0 review (issues #60 and #61). Both
change what a caller reads on failure, neither changes a contract: the accepted range of
LAW_MCP_ERROR_MESSAGE_MAX_CHARS is unchanged, no error category was added or renamed, and
no tool schema moved.

Fixed

• A truncated content_too_large message no longer cuts the source PDF URL in half. Under a
  low LAW_MCP_ERROR_MESSAGE_MAX_CHARS the cut used to land inside the URL — the one token the
  caller can act on — while the appended guidance still said to fetch the content from "the
  given address". The cut now lands in the descriptive prefix and the trailing URL is kept whole
  whenever it fits within the cap; when even the URL plus the truncation announcement would
  exceed the cap, the plain cut still applies, so the cap always holds. That fallback is pinned
  by a regression test as a deliberate trade-off (#60).
• A transport failure toward api.sejm.gov.pl (connection refused, read timeout, protocol
  error) no longer copies the raw httpx text — host, URL, TLS or errno detail — into the tool
  error or the ERROR log. The message names the failure class and the endpoint
  (Błąd połączenia z API Sejmu (ConnectError) podczas żądania GET acts/DU/2024/1); the
  httpx exception is kept as the chained cause and logged at DEBUG only, the same ERROR/DEBUG
  split the validation and upstream categories already had. With this, every unavailable
  message is project-authored at its raise site (#61).
• law_scrapper_mcp.__version__ is read from the installed distribution instead of a hardcoded
  string that sat outside the release script's synced locations and had stayed at 3.0.0 since
  v3.0.0. A checkout that was never installed reports 0.0.0+unknown.