0.82.0

Binding scenarios that check event identities, refusals that probe the record, and validation that names the file.
3 fixed.

Changed

• Synthesized binding scenarios (flow, mapping, delivery, on-failure, a bounded retry's attempts and final failure, an unbounded retry selected per refusal, and a condition's negative witnesses) compare the identity fields of the trigger's event with the instances its invocation was sent or the row it acts on holds, also where the binding arranges a row before it, as command scenarios do since #273, so a target that publishes another identity in the event fails them; they passed it. A model whose binding triggers carry no captured instance into their event keeps its suite bytes.
• The arranged half of an input refusal on a command that addresses an existing record, where no identity view shows the arranged row, sends after the refused send a valid input for that record of the first branch that addresses it from the state it was arranged in, and requires that branch, so a target that moves the record on refusal out of every state that branch runs from, or otherwise changes what it answers, and publishes nothing fails it; it required only the error and no event, and such a target passed. A move between two states that branch runs from is still not seen. Where no such branch has a valid send, the scenario is withdrawn and refused as ESS-SYNTH-001 naming the branches tried (#209). A model with an identity view keeps its suite bytes.
• ess specify validate on a specification of several files names the file a refusal was read from, where it named <document> whenever the refused declaration's name was written in more than one file, as a name declared in two files is: a refusal made while a file is read is cited in that file, and one checked after assembly in the file of the copy assembly kept, which is the second when the first does not convert; a name written twice in that one file names the file and no line. The library's Specification::assemble_traced and resolve::diagnose_traced return and read that record; diagnose_locating is unchanged.

Every change: CHANGELOG.md § 0.82.0