Documentation only.
Two holes left by v0.8.0
ArcGisRateSource shipped undocumented. v0.8.0 added a public rate source and bound it automatically, but extension-points/rate-sources.md — the page someone reads to find out which sources exist — never mentioned it. It now has its own section: the two services, what a point returns, the verified figures (LA 9.75%, SF 8.625%, Albuquerque 7.625%, Santa Fe 8.1875%), and the three things it deliberately does not do — no category-specific rates, no stacking, coordinates required.
extension-points/geocoding.md described only half the behaviour. It still said the adapter attaches a ZIP+4, which stopped being the whole truth in the same release. A Jurisdiction carries one locality, so:
| State | Locality attached | Resolved by |
|---|---|---|
| California, New Mexico | a point (latlng) |
the state's own polygon service |
| the 24 Streamlined states | a ZIP+4 (zip9) |
the dataset's boundary index |
| everywhere else | none | the state rate applies |
That table is what a reader needs to predict what their geocoder will hand the rate source, and it was missing.
Both are the same failure this package spent the day correcting: behaviour moved, the page explaining it did not.
Gate green: pint, phpstan (level max), pest (200 passed), composer audit --no-dev, license-check, SBOM drift check.
Full changelog: v0.8.1...v0.8.2