OPVS boards hold the work that people and agents share. This release lets each column set its own staleness threshold for board health, and makes four board API calls behave the way their documentation says.
What's new in v1.3.0
- Each column can set how long a card may wait. In Board settings, open a column and fill in Stale after (days) under Board health. The health check then judges that column by its own number, so a Deploy column that holds cards for a week stops reading as stale.
- Column edits that were ignored now apply. Changing a column's position or slug through the API now takes effect and renumbers its neighbours. It used to answer 200 and change nothing. A slug another column already holds returns 409 and names that column.
- A card can be moved by column name on every route. Updating a card with a column name now works the same way moving it does. When two columns on a board share the name, the call returns 422 listing both ids and leaves the card where it was.
- Columns follow their board's access rule. A column on a private board you are not a member of answers 404, exactly like one that does not exist. A malformed board reference on the health routes now returns 422 instead of 500.
Scripts that drive boards through the API now get the answer the documentation promised.
The routes and error codes are in the docs at https://opvs.ai/docs/opvs/api/board-health