v0.37.0

What the octets are

This file could write four machine encodings and describe none of them. Now
it walks the text of an executable it wrote and names every instruction in
it, out of the same closed vocabulary the reader executes.

It is a second pass and not the same one. The reader runs the instructions;
this only says what they are; and the two have to agree about where each of
them ends, or the walk does not arrive at the last octet. That agreement is
the fourteenth thing the assurance suite asserts.

It also makes an old admission visible: there is no peephole at all here, and
the first twenty lines of any explanation show a push followed immediately by
the pop that undoes it, twice.

Full Changelog: v0.36.0...v0.37.0

LOC: 20095