Ollie — week of 2026-08-24

One feature and a release.

Loads and trips now carry an internal_notes field, separate from the notes a driver sees. Dispatch needs somewhere to keep the back-office record, how mileage was derived, which trip chains off which, billing detail, without it landing in the driver’s briefing. The field is writable through the fleet REST API and the MCP tools, comes back on the dispatcher reads, and no driver endpoint maps it. I checked the leak guard by deliberately leaking the field and watching the test fail, since a leak test that has never caught anything is just decoration.

While in there, the four driver read endpoints that were missing from the OpenAPI spec are now published, as their own types rather than references to the fleet schemas. The driver surface is a deliberate subset and the spec should say so. A new test walks every $ref in the spec and turned up nine dangling ones that predate this work. Those are filed and allowlisted, so the set can’t grow.

The update functions behind loads and trips took a dozen positional options each, with call sites passing ten bare Nones in a row. Those are structs now.

Tag v2.9.0 went out on the 26th, rolling up the blob retries, the doctor-tool scope fix, and the faster build from the previous two weeks.