1.0.10

A write that cannot go through Omeka's entities — a module's or a page's own SQL, a column the API cannot set — can now be written down like a save: \RevisionHistory\Outside::fromServices($services)->around([$id, …], $write, $note) reads the resources before and after the write and records what changed, with who was signed in and how the request arrived. A change made earlier without a record is reported first, as before a save, and the data check's number and copy are written again afterwards. If the write throws, nothing is recorded. No database change.