Features

Board, list and calendar

Three readings of the same cards, with the same filters underneath.

The three views read the same payload and apply the same filters. Switching view does not change what is being shown, only how.

View	What for	What it allows
Board	the daily work: which stage each thing is at	dragging between columns and reordering
List	scanning many cards and editing in bulk	multiple selection, ordering by column
Calendar	who is due when	reading due dates across the month; optional and can be turned off

There is one search box

Search works the same across all four surfaces, and it has one rule worth knowing: `#42` asks for ONE card. It is equality, not a prefix (#4 does not bring #42 back), it does not match text and it does not reach epics.

Dragging with a filter on

Position arrives as an anchor, never as an index

When a card is dropped, the client sends afterCardId, the card it goes after. With a filter on, the visible index does not match the column's real index, and sending a number would move the card to the wrong place.

Board route

The single payload, scoped on the server.