Polishing the way to integrate that in a real world app.

- triggering a new and unique `editable.construct` because the `editing` state is not necessarily the first state of editable (especially with manual construct)
- history sets edit state in case the edit is directly triggered from the history list
- added an overwrite option to avoid overwriting a default form value (not yet documented)
- added a convenient basic filter for some htmlentities