v0.28.1

A patch on 0.28.0.

Fixed

• An admin can add a page directly in the knowledge folder again. The deployment owner is an Admin for every purpose, not only for writing: every access rule that names the Admin role applies to them too, on top of whatever the rules give or deny them by their own name or other roles. And because writing implies reading, an admin who may change everything under the root may also see it, whether or not the root's rules name Admin — a subfolder that excludes Admin still does. Before this, an owner the roles file did not name could create a folder in the knowledge root but not a page: the write rules let them in and the read rules did not. (#421)
• The share dialog's "everyone can read" answer counts the deployment owner, so a folder that keeps them out is not called public. (#422)

CI

• A lint ratchet on pull requests: a change may not add lint findings to the files it touches. (#418)