v0.13.1

What a project does is declared, not guessed

Before 0.13.1 the app decided what a project was by looking at its data. A project with a sprint
row "did Scrum", so it got a sprint board. A project with a version row "did releases", so it got
a releases tab. Four such heuristics existed, and each was wrong the moment someone created one
row to try something out.

Delivery capabilities are now columns on the project — board, releases, estimation —
set by a person and changed by a person. The preset name you see (Kanban, Scrum, Releases) is
derived from those columns server-side and cannot be written directly.

Creating a project asks you to choose, and says the choice is reversible, because it is.
Project settings gained a Delivery tab where the three capabilities are turned on and off.

A capability that is off still has a way in. Every one of them has an affordance visible while
it is off, so a feature you have never used is reachable rather than invisible.

Capabilities never change a status code. They narrow what the interface offers you, never what
the server answers. A project with releases turned off still accepts and returns version data, so
a saved link keeps working.

If you use saved filters or search

Two field keys were retired in this change. Searches and saved filters that use the old names keep
working through aliases, and the suggestion list is now capability-aware: it offers you the keys
that mean something for the project you are looking at.

---

Full Changelog: v0.13.0...v0.13.1