Fleetbase PHP SDK 1.4.1
Tracks the inspection API's renamed submission answers, which shipped upstream after 1.4.0 was published.
A submission's answers were custom_field_values, each naming its field with custom_field. The API calls them answers and field now — that is what it documents and what it returns — and a field is named by a public id rather than a bare uuid. The earlier spellings remain accepted on submit, so this is additive and no existing integration breaks.
The SDK forwards a submission body verbatim, so no src/ file names any of these keys and none needed rewriting. What changed is the locked contract and everything generated from it, together with the README example, the submission test's payload and response fixtures, and this note. The generated submit example previously sent an empty custom_field_values beside a populated flat item_results block — the only worked example in the reference was the legacy shape; it now answers the way the API documents.
Pins: postman at 822b867 (the collection rename and its response examples, both merged) and fleetops at refs/pull/319/head @ 9f2ffe98. As in 1.4.0, the upstream implementation is still Fleet-Ops PR #319; release approval must confirm its API is available in the intended deployment. A passing overlay run proves the locked implementation, not availability in every published image.
Public methods, positional and direct call forms, legacy envelopes, resource helpers, PHP 7.4/8.x compatibility, and the AGPL-3.0-or-later license are unchanged from 1.4.0.