[tonytonycoder11]

The four packages go to 1.0.1: two fixes that are already on main, and a change to the release workflow. A call whose answer has no body, such as a 304, a 204 or the answer to a HEAD request, now ends when its head arrives instead of staying pending with a duration that grows. The recording dot, and the status and time of a running call, beat a few times and rest instead of pulsing for as long as they are on screen.

The second fix is the one that matters. With the inspector open and idle, 1.0.0 kept an Android emulator at 1.5 to 8.5 host cores, with the raster thread of the app at 46 to 59% of a core; this version keeps it at 0.3 to 0.7. With the inspector closed neither version costs anything measurable, and recording a call costs 0.3 to 2 ms of CPU. The emulator numbers are from a debug build and a page of 100 calls, 60 of them unread 304s, and the cost of a call is from the host VM.

This is a patch: it fixes two faults and adds nothing to the API. The release commit moves the four pubspecs, the three adapter constraints, flutwireVersion and the podspec, which version_test checks, and the entries that were under Unreleased now sit under [1.0.1]. The format check, the analyzer, the four test suites and the publish dry run of each package pass locally. The tag comes after the merge.