1.0.1 — one route, one spelling

Fixed

• custom_fields.definition() requested .../{field_id}/ with a trailing slash. It was the only call in the client carrying one, and the only spelling of that route never driven against a live instance — the unslashed form has been. Nothing asserted the URL, which is how two spellings of one route coexisted unnoticed; there is now a test that fails on either one changing.

Changed

• The README and CHANGELOG now say which half of this client has actually met a Populi server. The core lifted out of the original application — people, tags, custom fields, leads, communication plans, notes — was exercised live through real webhook traffic. The surface added afterwards for parity with the .NET client — courses, files, data_slicer, academic_terms, PopuliFilter, and the definition and term-scoped helpers — was written from the documented contract and unit-tested, but never sent to a real server.

On an API that answers an unreadable request with 200, that distinction is the whole basis for how much to trust a route, so the coverage table now marks each group live, contract-only, or mixed. Reports of what the untested paths actually do are the most useful contribution available.