loupe-boardlisted

# Working a Loupe board Each project in Loupe has one board, and the board has four columns: Backlog, Next, In progress, and Done. A card carries a title, a Markdown body, a type, a priority, a status and an origin. The status is the column the card sits in. The tools spell the four columns `backlog`, `next`, `in-progress` and `done`. The tools act on the project your token is bound to. An instance can switch the board off, and every tool then answers "The board is switched off on this instance." ## The four tools | Tool | Use it to | |---|---| | `card_create` | Put a new card on the board. It lands in `backlog` unless you pass `status`. | | `card_list` | Read the board. Filter by `status`, `type` or `priority`. Done reads newest completion first, and every other column reads highest priority first. | | `card_get` | Read one card, with its full Markdown body, its pull request links, its linked documents and the site-review comments pointing at it. | | `card_update` | Change a card. A field you leave out keeps the value it has. A new status or priority puts the card at the end of the column it arrives in. | `card_get` and `card_update` take a `cardId`, which you read from `card_list` or `card_create`. `documentIds` links the documents the work is written up in, on `card_create` and `card_update`. It follows the same omit-versus-empty rule as `pullRequestUrls`. Unlike a pull request URL, an id naming no document of this project is **refused** rather than kept: a URL canno