The order of specialise categories is important.

For some base categories like specialise, the order of categories is important.
list.sort implements a stable sort so we can use it here.

Also, add Javascript and CSS linters.

fixup! do not care node_category when getting aggregated payment transaction lines from a payment transaction group.

Before, the preference state was tested first, which caused useless ZODB loads.

At this point, Data.fs is already updated, so not keeping this dump would just leave you with inconsistent ZODB and catalog.

bank reconciliation: support the case where the user run "select all non reconcile" and cancels just after.

do not set meaningless contributor category in web page

per default it useses indexeddb storage

Modify jIO API to keep user data not modified.
jIO.get({"_id": "foo"} -> jIO.get("foo")
jIO.remove({"_id": "foo"} -> jIO.remove("foo")
jIO.post({"title": "bar"}) -> jIO.post({"title": "bar"})
jIO.put({"_id": "foo", "title": "bar"}) -> jIO.put("foo", {"title": "bar"})
jIO.getAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.getAttachment("foo", "enclosure")
jIO.removeAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.removeAttachment("foo", "enclosure")
jIO.putAttachment({"_id": "foo", "_attachment": "enclosure", "_blob": blob} -> jIO.putAttachment("foo", "enclosure", blob)

Add jIO.allAttachments method.

jIO.get does not return an _id and _attachments attributes anymore.
jIO.get now really returns the document as saved by jIO.put/post.

and in any case, do not accept deleted ones