v0.6.1

Tell them what the pre-release audit turned up

Six ways to get a wrong answer silently, and one of them was in the check
promised last time: the dimension guard read only the first vector, so a
response that changed partway through passed and dot() then compared
prefixes. That one can reorder results in a lesson already vendored, so
the note says which single finding is worth pulling forward and which are
only about refusing bad input.

Also records the lock mistake as mine — reusing the generation lock would
have parked embed() on the event loop behind a running generation — and
lists what was checked and found clean, so the absence of an HTML path
for host data is on the record rather than assumed.