Omniscio

Mission Control — the table, the views and the board (part 2)

Part 2 of the Mission Control page: the Main Table and everything you can do to it — filters, grouping, the alternate views over the same items, the Kanban board's card actions, colouring and swimlanes, finding a teammate, and the per-board preferences you can set.

On this page

What it is

This is part 2 of the Mission Control page. It covers the board itself: the table, the views, and the controls around them.

Where to find it

Inside Mission Control, on any board — the view switcher and the filter toolbar sit at the top of it.

How it behaves

Main Table (Phase 2)

The board route (/board/:id) renders BoardView, which loads everything in one call — GET /boards/:id/full → { board, groups, columns, items, values } — and draws a custom grid (no heavy table lib): a column header (with a Column Center + to add any of the essential column types), then each group (colored strip, collapse) as item rows, an "+ Add item" row, and a group footer of per-column summaries. Each cell is driven by a frontend column registry (features/board/columns/) that maps a column type to a renderer/editor — the status cell is a colored pill with a label picker + Edit Labels; numbers/text/date/checkbox/timeline/people/dropdown have inline editors.

The backend's core primitive is the column-type registry (src/lib/column-types/ in the Mission Control service): one handler per type owning defaultSettings / validate / serialize / toText / summarize. columns rows store type + settings (JSONB); column_values rows store value (JSONB) + a denormalized text. Writing a cell (PUT /items/:id/columns/:colId) validates the value through the registry (HTTP 400 on a bad value), so a status value must match one of its column's labels. New backend modules — groups, columns (the Column Center), items + column-values — are account-scoped through the board's workspace via a shared ownedBoard helper.

Column headers — rename, menu, and resizing

  • Rename and menu. Clicking a column's name renames it. Hovering shows a "⋯" menu: Sort, Filter, Collapse, Move left, Move right, Add column to the right, Rename, Delete — the same set monday.com offers. Move left / Move right are the keyboard way to reorder columns. Only actions with a real backend are listed; Settings, Group-by, Change type and the AI actions are left off until they have one.
  • Sort is visible. The column the table is sorted by shows a small up or down chevron on its header (F0160 — before, the sort lived only in aria-sort, so a sighted user could not tell which column was sorting or which way).
  • Resizing a column. Hover the right edge of a column header and a thin accent line appears; drag it to make the column wider or narrower (mouse or touch). Double-click the edge to put the column back to its default width. From the keyboard, Tab to the edge and press Left / Right (5px a step, 20px with Shift). A column never shrinks below 60px. In right-to-left languages the edge sits on the left and dragging follows it. Widths travel in the page address (the cw parameter) with the board's other view controls.
  • Deleting and moving are instant. Delete removes the column on screen at once (F179) and puts it back exactly as it was if the server refuses; Move left / right swaps the two columns locally before the two server writes, restores and resyncs if only one write lands, and otherwise lets the realtime update reconcile without a blocking reload.

The resize edge is the shared ColumnResizeHandle (src/plugins/mission-control/web/components/ColumnResizeHandle.tsx), also used by My Work. It paints a 4px line inside a 24px grab area, and two style rules keep that line visible: it sets backgroundColor, never the background shorthand (the shorthand resets background-clip and once painted the whole 24px area as a solid block — F0565), and it sets box-sizing: content-box (the app's global border-box reset otherwise squeezes the 4px line to 0px, which made the board's handle invisible until 2026-10-29). Both are locked by tests/unit/mission-control/column-resize-handle.test.tsx and column-header-resize-handle.test.tsx.

Board view tabs — keyboard and screen readers

Fixed 2026-10-15 for the Machine A accessibility run (A11Y-A053, the tab part of A11Y-A062). Locked by tests/unit/plugins/mission-control/view-switcher-a11y.test.tsx (axe-core in jsdom).

  • The "Board views" tablist holds only tabs — Main Table, the saved views (pinned first, then by position) and the personal views. The "+" Add view button, the "Deleted views" button and the delete confirmation sit right after it in the same strip, so nothing moves on screen.
  • View options from the keyboard. Every editable tab, selected or not, opens its own options menu with Shift+F10 or the Menu key, and announces that through its description ("Press Shift+F10 or the Menu key for view options."). The shortcut lives on each tab button because the tabs auto-activate on arrow keys. The Popover moves focus into the menu and returns it to the tab on close.
  • The ⋯ button is for the mouse only. It still looks and clicks the same, but it is aria-hidden with tabIndex={-1}, because a tablist may contain only tabs (axe aria-required-children). Dev Ops Overseer ruling, 2026-10-15: option A, no visible change.
  • Tab state is spoken. A pinned or locked tab reads "Pinned" / "Locked" after its name, from visually hidden text next to the icons. The "My Views" label is aria-hidden and describes each personal tab instead.
  • Not done yet: the tabs have no role="tabpanel" / aria-controls, because the view content renders in BoardView.tsx. That is a follow-up row.

How the strip is built (ViewSwitcher.tsx / ViewTab.tsx):

  • Main Table key. The implicit Main Table tab carries the sentinel key __main_table__, so the string-keyed tablist model (useTabKeyboard: Left/Right/Home/End with roving tabindex) can name it. The sentinel never reaches the view API.
  • Gantt is the timeline view type under a friendlier label; the tab name follows the label (BoardView.handleAddView).
  • Read-only boards. On a read-only board every mutating handler is undefined, so the add-view control, the per-tab options and the shortcut are all absent.
  • Stable tab order. The tie-break on position keeps tab order stable, because the server returns views in query order.
  • Deleted views (RT-F405) lists soft-deleted views for restore. A failed restore is already logged by authedFetch.
  • The add-view menu body mounts only once the Popover panel exists, so the shared menu model binds to a real node. The Popover owns the portal, the viewport flip, click-away and Escape, and focus returns to "+".
  • "Share board" in a tab's menu opens board sharing, because access is granted per board; there is no per-view share token. "Reorder (for you only)" expands inline to Move left / Move right.
  • Inline rename uses the shared useInlineRename machine (draft, no-op guard, Enter submits, Escape reverts). The board owns persistence and reports its own failures.

Board filter toolbar (post-Phase-4 fast-follow)

A pixel-near rebuild of monday's Main-Table toolbar, replacing the plain Phase-3c controls with monday's real filter surfaces (features/board/BoardControls.tsx + features/board/toolbar/). The row reads as one control set — New task · Search · Person · Filter · Sort · Hide — over the shared ToolbarButton shape (px-2.5 py-1 text-sm, 1px border, foreground text idle → accent when active). All logic is a pure module (features/board/boardQuickFilter.ts + codec), compiled to a predicate in BoardView and applied client-side over the loaded board data (no backend).

  • Board search — collapsed it's a plain toolbar button (search glyph + "Search"); clicking expands it in place into a ~240px "Search this board" input (accent border) that owns the query. Escape clears + collapses, an empty blur collapses, a non-empty value keeps it open.
  • Person filter — a toolbar button (accent-tint fill when active) opening a searchable list of teammates; multi-selecting members filters items by the people assigned to them. It originally rendered every member as a bare grid of avatars with no search box, which stopped being usable somewhere around a dozen people; it now uses the shared teammate picker, so it is searchable and keyboard-operable like every other place you pick a person.
  • Quick filters panel — the Filter split-button (funnel + "Filter", showing "Filter / {n}" once selections exist; accent-tint fill when the panel is open or n > 0) opens a wide panel of per-column facet columns, each a scrollable list of multi-select chips. Chips are OR within a column, AND across columns. The panel stays open across chip clicks (only a click-away closes it); a header "Showing X of Y tasks" count and a Clear all reset are always present.
  • Save as new view — both the Person popover and the Quick filters panel offer "Save as new view" (enabled only when a real handler exists and something is filtered). It persists the current filter set as a new saved view tab (a views row) via the existing view system. Edits to filters while viewing an already-saved view are session-only — they don't mutate the saved view until you save again as a new one. The save is guarded against double-submit.

Pure filter/codec logic is unit-tested (tests/unit/plugins/mission-control/board-quick-filter.test.ts); the toolbar components have component coverage (search-board-button, person-filter-button, quick-filters-panel under tests/unit/plugins/mission-control/).

Finding a teammate — one search, everywhere

Every place Mission Control asks you to pick a person — assigning an item, @-mentioning someone in an update, adding someone in Permissions, choosing an approver, and the toolbar's Person filter — now answers a query the same way.

They did not used to. Each of those five was written separately and they disagreed about what a search even searches: assigning matched a name, email or role; @-mentions matched the name only; Permissions matched the name only; the approver field matched name or email; and the Person filter had no search box at all. The visible consequence was that typing a teammate's email found them when you were assigning work and found nothing when you were mentioning them, and typing a role worked on exactly one screen.

All five now share one rule (matchTeammates in src/shared/teammate.ts): it searches display name, handle, email and role, and ranks exact matches above ones that start with what you typed, above ones that merely contain it. Every picker has a search box and responds to ↑ / ↓ / Enter / Escape. A picker whose member list failed to load now says so, instead of showing "No matching people" as though your search simply missed.

The same rule backs Team Chat's @-mention typeahead and a main-app picker (components/ui/TeammatePicker), so a feature that needs "let the user pick a teammate" has one to reach for rather than writing a sixth. Accent handling is passed in per surface rather than baked in, because the main app and the plugin fold accented characters differently on purpose.

The promises this locks in — and the one thing deliberately left out of it, the fact that Mission Control and Team Chat still identify the same human by two unreconciled ids — are written up in .claude/memory/contracts/teammate-primitive-contract.md.

Roadmap view (post-Phase-3 addition)

The Roadmap tracker view (RoadmapView.tsx) is a matrix of time-bucket columns (e.g. quarters/months) crossed with status rows. Each item lands in the cell where its date column's period meets its status value, giving a bird's-eye view of items across time horizons. Listed as { type: 'roadmap', fallback: 'Roadmap tracker' } in ADDABLE_VIEWS (features/board/views/ViewSwitcher.tsx). Like the other alternate views, it is a config-only view over the loaded board data — no backend change required.

Location column + Map view (Ollert Port WI-6)

The Location column type ('location' in PmColumnType) stores a geographic position as { lat, lng, label } (the LocationCellValue interface in columnValue.ts). Geocoding is powered by Nominatim/OpenStreetMap (free, no API key; User-Agent: Omniscio/1.0). The cell (LocationCell.tsx) shows a MapPin icon + truncated place name; clicking opens a search combobox (LocationForm.tsx) with debounced type-ahead, ARIA combobox pattern (arrow keys, Enter, Escape), and a "Remove location" action when a value is set. Listed in the Column Center's "Super useful" section.

The Map view (MapView.tsx, { type: 'map', fallback: 'Map' } in ADDABLE_VIEWS) plots items with location values as circle markers on an interactive Leaflet.js map with OpenStreetMap tiles. Finds the board's first location column and builds a LocatedItem[] from items+values. Markers use the board's accent color, show item title + place label as tooltips (XSS-safe via textContent), and clicking a marker opens the item detail. The viewport auto-fits to all markers on load (with signature-based dedup to avoid re-fitting on unrelated data changes). Two empty states: "no location column" (add one first) and "no items with locations" (overlay on the map). An SR-only item list provides keyboard/screen-reader access. CSP: connect-src includes nominatim.openstreetmap.org; img-src already covers https: for OSM tiles.

Feature catalog: col-location (column node) and view-map (view node, requires edge to col-location in the feature graph). PM feature catalog: view-map in the operations preset with dependencies: ['col-location'].

Workload view

The Workload view (WorkloadView.tsx, { type: 'workload' } in ViewSwitcher.tsx's ADDABLE_VIEWS) shows per-person capacity utilization across a board. It groups items by a People column (auto-detected or configurable via groupByColumnId), sums each person's effort from an optional numeric effort column (effortColumnId; a new Workload view seeds it from the board's first numbers column, and with no effort column set every item counts as 1). Effort follows the one shared recipe in src/shared/pm-effort.ts: the cell's number first, then its text; a blank effort counts as 0 and is marked "N not estimated" on the person and "Not estimated" on the item, an entered 0 stays 0, a negative adds no work, and an item with several owners splits its effort evenly between them (shown rounded to one decimal, and renders a horizontal bar per person against a configurable capacity (capacityHours, default 40h/week). Over-capacity bars turn red (--status-error-rgb) with a translucent overflow overlay. A tick mark on each bar shows where the capacity threshold sits relative to the widest bar. The WorkloadSummary header (sticky) shows the capacity input and which column drives effort. PersonAvatar renders initials in accent-colored circles. Unassigned items (no people-column value) are grouped in a collapsible section at the bottom. Each person row is expandable to list individual items (clicking an item opens its detail via onOpenItem). Empty states: "no people column" (add one first) and "no items" (generic). Read-only mode hides the capacity input.

Item ID column

Item ID column (unique_id): each item shows a short number, unique on its board and fixed for the life of the item (001, 002, …, in creation order). The backend assigns it when the item is created, and again if it moves to another board, so a deleted item's number is never reused; GET /boards/:id/full fills the cells from it.

Number formatting, Time Tracking, and Checklist columns

Three column additions to the Column Center catalog. (1) Number formatting — the existing numbers column gained per-column format settings: plain (locale-aware decimals), currency (configurable symbol + before/after position), or percent; configured from a hover-revealed number-format button that opens the NumberFormatForm popover in NumbersCell.tsx. The pure formatting function formatNumber() lives in web/lib/columnValue-format.ts (re-exported by columnValue.ts). (2) Time Tracking ('time_tracking' in PmColumnType) — reads elapsed time from the time_entries table via session-bridge-time.ts (the cell imports the bridge directly, not via CellProps). Shows compact duration (e.g. 2h 15m) with a green dot when a timer is running; the running row ticks via a 1s setInterval (no grid-wide re-render). Start/stop toggle with a pending latch to prevent double-fire. (3) Checklist ('checklist' in PmColumnType) stores { items: [{text, done}] } as JSON. The grid shows a progress pill (mini bar + done/total); clicking opens an inline popover editor with checkable items, text editing, remove buttons, and an Enter-to-add input. Auto-commits on every change. Checklist registers a checklistSummary (aggregate completion %) in the frontend registry; Time Tracking registers no summary. All three render in render/mc-cell-renderers.ts for HTML snapshots. The backend column-type registry carries every Column Center type: the value shapes above are validated server-side (shape only — a formula is never evaluated and a mirror never followed), and the computed types (Created Time/By, Last Edited Time/By, Unique ID, Formula, Mirror) refuse a client-written value rather than trusting it. Created Time/By and Last Edited Time/By are filled by GET /boards/:id/full itself (in Omniscio's cloud service): created from the item row, last edited from the item's newest activity-log entry (falling back to the created pair), and any stored value for those four types is ignored. Unique ID has no stable stored number yet, so it still shows blank. The two legacy ids the backend spells with a hyphen — long-text and world-clock — are translated at the edge by src/shared/pm-column-type-wire.ts, used by the board client, the CLI create route and the sync mirror.

Dependency column — linking one item to another

Clicking a Dependency cell opens an editor that lists the links the item already has and a box for adding one. Typing in the box lists this board's items whose name contains the text (accent- and case-insensitive, up to 10), and clicking one links it. Add (or Enter) links only an exact match: an item's id, or the one item whose whole name equals the text. A partial name, or a name two items share, has to be picked from the list. Text that matches no item saves nothing, keeps Add disabled and shows "No matching items". The item itself and items it already depends on are never offered. The saved value is always the real item id ({ dependencies: [{ itemId, type }] }), because the Timeline arrows, the critical path and the AI all join on that id; until 2026-10-22 the editor stored typed text as the id, so a link made by name pointed at nothing. Code: DependencyCell.tsx (linkableItems, resolveTypedItem, matchingItems), reading items from the board cache like the Connect Boards picker.

Kanban card actions + "⋯" menu (post-Phase-4 fast-follow)

Hovering a Kanban card reveals monday's two actions in the top-right: a pencil (opens the item card) and a ⋯ overflow menu (features/board/views/KanbanCardMenu.tsx, on the shared Popover). The menu mirrors monday's real order: Open task · Move to ▸ · Duplicate ▸ · Copy name · Copy task link · Add subitem · Customize cards ▸ · Archive · Delete (Delete confirms first). "Move to" and "Duplicate" open right-side flyout submenus (features/board/CardMenuFlyout.tsx — SubmenuRow/FlyoutItem, portaled out of the menu so they aren't clipped, flipping left near the screen edge): Move to → Move to group (lists the board's other groups → patchItem({groupId})) or Move to board (lists other boards from /nav/tree → a new POST /items/:id/move-to-board, which reassigns the board + a target group and drops the board-scoped column values); Duplicate → without / with updates (the existing POST /items/:id/duplicate, with ?includeUpdates=true also cloning the conversation thread). Copy name / Copy task link write to the clipboard (the link is an omniscio://mission-control/board/<id>?item=<id> deep link; BoardView opens an item from a ?item= param on load).

Subitems are real item rows tagged with parent_item_id (no migration — the column already existed). GET /boards/:id/full now returns top-level rows in items and child rows separately in subitems, so every other view is unchanged; the Kanban card renders its subitems as nested name-only mini-cards with a footer count badge and an inline "+ Add sub-task" composer (POST /items/:id/subitems), which the menu's Add subitem row opens and focuses. Backend behavior is the subitem grouping helper is unit-tested (groupSubitemsByParent in tests/unit/plugins/mission-control/kanban-data.test.ts).

Kanban card coloring by field value

Not wired in the app today. Cards render with no colour stripe. KanbanCard.tsx accepts an optional colorHex prop and, when it is set, draws a 4px left border from it — but nothing computes or passes that prop (KanbanBoard.tsx renders <KanbanCard> without it). The unmounted "Color by" picker (KanbanToolbar.tsx) was removed as dead code on 2026-10-28 (MC QA audit Tier 4 #10o), so building this feature starts from the colorHex prop alone. ViewConfig in web/lib/types-board.ts carries no colorByColumnId key, so a per-view colour choice could not be persisted either.

Kanban swimlanes (second grouping axis)

The Kanban view gained a swimlane feature — a second row-level grouping axis perpendicular to the status columns. A "Swimlane by" dropdown in the Kanban toolbar (SwimlanePicker → the Select component, persists as ViewConfig.swimlaneColumnId) lets users group items horizontally by any status, priority, people, dropdown, or checkbox column; "None" disables swimlanes. When active, items stack into collapsible KanbanSwimlaneRow sections — each a filtered KanbanBoard with its own DnD context (namespaced via id prop, no cross-swimlane drag in V1). Items with no value land in a "No value" lane at the bottom; multi-assignee items (people column) appear in each assignee's lane. Subitems follow their parent's lane. The swimlane column picker excludes the current groupByColumnId to prevent the useless same-column-both-axes case. A newly created Kanban view is seeded with groupByColumnId pointing at the board's first status or dropdown column (useBoardViewActions.ts). Data helpers: computeSwimlanes() + SWIMLANE_GROUPABLE_TYPES in kanbanData.ts; unit-tested in tests/unit/plugins/mission-control/kanbanData.test.ts.

Kanban keyboard and screen-reader behaviour

Fixed 2026-10-15 for the Machine A accessibility run (A11Y-A035, A11Y-A036, B068, the kanban half of B069). Locked by tests/unit/plugins/mission-control/kanban-a11y.test.tsx (axe-core in jsdom) and kanban-announcements.test.ts.

  • A card is a named article, not a button. dnd-kit's useSortable is given attributes: { role: 'article' }, so the live card is a focusable article named by the item (aria-label) with its place in the column (aria-posinset / aria-setsize). dnd-kit drops aria-pressed by itself for a non-button role. The old role=button around real buttons was axe nested-interactive.
  • Keys belong to the element that has focus. The card's key handler acts only when the key was pressed on the card itself (e.target === e.currentTarget): Enter opens the item, Space starts the keyboard drag. Enter or Space on the pencil, the ⋯ menu, the sub-task count or the vote badge works that button and never opens the card or starts a drag.
  • Arrow keys move between cards only from a focused card (Up/Down within a column, Left/Right across columns). Arrows pressed inside a card's editable chip stay with that control.
  • Drag instructions and announcements. The DndContext's screenReaderInstructions say Enter opens the card and Space moves it. kanban-announcements.ts names the column: "Card X is over Stuck", "Dropped card X into Done". It resolves the target from a column droppable id (colDroppableId) or from the card under the pointer.
  • Columns. Each column is a group named "Stuck, 3 cards" (ICU plural). Inside a swimlane the lane is named too: "Stuck in High, 3 cards". The visible count is aria-hidden because the name already carries it. Column titles are role=heading: level 2, or level 3 under a swimlane, whose header is a level-2 heading around a toggle that reports aria-expanded.
  • Sub-task cards open from a real button on the sub-task name (styled to look unchanged). A mouse click anywhere else on the sub-task card still opens it.

Kanban card internals (why the code is shaped this way)

  • KanbanCard is a memoized sortable wrapper. The live card stays in its column, dimmed to 40%, while its DragOverlay copy (rendered in KanbanBoard) moves. The memo stops the optimistic re-render fired on every onDragOver from re-rendering every sibling.
  • KanbanCardView takes data and callbacks. innerRef / style / handleProps carry the useSortable wiring. The DragOverlay copy omits them and every callback: it is a static, undraggable clone with no hover actions, 264px wide, with a raised shadow and a grabbing cursor.
  • Click versus drag-release. The pointer-down position is recorded in the capture phase, so dnd-kit's own onPointerDown still runs. A click that moved more than 5px (the sensor's activation distance) is a drag-release and is ignored. A click never opens the card while editing or on the overlay copy.
  • Elevation lives in classes so hover can raise the card. Only the drag copy sets an inline shadow (F0928).
  • Hover actions (pencil + ⋯) stop pointerdown so pressing them never starts a drag, and never render on the overlay copy or a read-only board. Menu clicks portal to body but React-bubble to the card, so CardHoverActions swallows them.
  • Optimistic cover (F178). A picked cover shows at once, and is dropped once the board data carries it (or rolled back by the menu on failure). The cover band is full-bleed, clipped by the card's overflow-hidden, and read from item.cover so the overlay copy keeps it.
  • A failed cover or icon upload says so (audit #69). CoverPicker and ItemIconPicker show "Could not upload that image." under the upload button and re-enable it, whether the upload threw (blocked type, too large, network) or came back empty. The raw error is never shown, and the same file can be picked again straight away.
  • computeCardCells is memoized on the item, columns and value map (F040), because it walks every board column. Editing swaps the read chips for editable ones, and pointerdown is stopped there too.
  • Stickers (WI-7) are decorative and display-only; editing happens in the item modal.
  • Sub-tasks start collapsed (monday.com's behaviour). The footer badge toggles them and stops click + pointerdown, and "Add sub-task" forces them open so the composer shows. A sub-task card shows the same cells as its parent, because /full returns sub-item column values.
  • The sub-task composer: Enter creates and keeps the field open for the next one. Escape or an empty blur closes it. A failed create shows an inline error and keeps the typed text, and the field stays open while there is text or a pending error.
  • KanbanView:
    • It keeps only the swimlane helpers, since PR #5019 moved card rendering and the mutation wiring into KanbanBoard.
    • It re-exports persistKanbanDrag so that import path stays stable (the RT-F030/F031 unit test imports it from there).
    • It uses the filtered/searched items from useBoardFilters via ViewRenderer when given, and shows a guided empty state instead of bare zero-count columns.
    • Its swimlane picker uses MC's own theme-aware --muted-rgb / --border-rgb / --foreground-rgb, because the host --surface-N-rgb tokens are not declared inside the plugin scope (F0030).

Grouped search (Phase 4a, extended)

Search Everything originally returned items only, grouped by board. A parity fast-follow broadened it to four result types — items, boards, dashboards, and people — grouped by type. Private boards you're not a member of are excluded (both the board results themselves and any items on them; dashboards and people are workspace/account-scoped and unaffected), consistent with the private-board enforcement above.

Archived items — where a filed item goes, and how to get it back

Archiving an item from the batch-action bar, a card menu or a subitem menu files it away rather than deleting it: the row keeps archived = true on the backend and is still on the board. Every board view renders only live rows, and the board header's Archived items button opens ArchivedItemsDialog (features/board/ArchivedItemsDialog.tsx), which lists the board's archived items — top-level and subitem — each with a Restore action that clears the flag and puts the row back where it was. There is no separate "deleted" state to restore from; that is what Delete is for.

Archiving an item files away its whole subitem tree with it, every level deep: PATCH /items/:id with archived sets the same flag on the item and every descendant in one transaction, and restoring the item brings the whole tree back. The desktop applies the same rule to its local copy (updateLocalItem / updateLocalItemAsync in pm-mutations-item.ts), so a read straight after the archive and the next sync agree. Before this (BUG-289) only the one row was flagged, so its subitems stayed live under an archived parent.

The archived rows reach that dialog in their own arrays on the GET /boards/:id/full aggregate — archivedItems and archivedSubitems — while items/subitems stay live-only, so no existing view needs a filter of its own. That split is not cosmetic: the desktop's PM sync reconciles its local mirror against that same payload and treats any row the payload omits as deleted, so a payload that simply hid archived rows made the sync soft-delete every one of them locally within a tick — the item vanished from the app and the dialog could never list it, with the cloud copy left untouched and therefore unreachable. pm-sync-part2-contract.md (the-keep-set-reconciles-against-a-payload-that-hides-nothing) locks the rule that followed: a payload a removal sweep reconciles against must not hide a row the database still holds.

Deleting an item — the whole subitem tree goes to Trash with it

Delete is a soft delete: the row keeps isDeleted = true and every board view stops returning it. Subitems carry parentItemId and the GET /boards/:id/full aggregate filters each one only by its OWN flag, never by its parent's, so deleting just the parent would leave its subitems on the board under a row that is gone. DELETE /items/:id therefore flags the item and every subitem below it, every level deep, in one transaction; the desktop's local copy does the same in deleteLocalItemAsync (pm-mutations-item.ts), including each subitem's comment, sticker and link rows and its search embedding. Before this fix the backend reached only direct subitems and the desktop reached none. Archive follows the same whole-tree rule (BUG-289, #11281).

Board customization features (desktop-only)

Six board-level customization features shipped as part of the Ollert Port work items. All are desktop-only — their IPC channels are not exposed as CLI routes and are blocked from the mobile/web WS bridge.

  • Celebrations (pm:celebrations:get/set) — confetti animation on status completion
  • Accent color (pm:accent-color:get/set) — per-board accent color override
  • Voting (pm:vote:toggle, pm:vote:data) — item-level voting/polling
  • Board background (pm:board-background:set) — custom board background image/color
  • Card aging (pm:card-aging:get/set) — visual aging indicator on stale cards
  • Stickers (pm:item-stickers:list/add/update/remove, pm:item-stickers:changed push) — decorative item stickers

IPC: 14 channels total (see src/shared/ipc-channels/pm.ts), all desktop-only. CLI-parity: classified as feature-scoped-surface exemptions (board-level visual settings with no external integration need).

Board favorites (parity fast-follow)

The star in the board-info popover is now wired to real favorites — starring a board persists it as a favorite (it was previously a dead control).

Stub cleanup (no dead buttons)

Every affordance that did nothing was either wired up or removed, so a control the user can see is a control that works. Wired: the view menu's Share item now opens the board share modal (access is per-board, not per-view, so it's labelled "Share board"); the board nav-row's Add to favorites now toggles the shared FavoritesProvider; and User management gained a real Filter menu (features/users/UserFilterMenu.tsx) — client-side status + role facets over the already-loaded member list, where an empty facet means "no constraint" and the two facets AND together. Removed (each needs a subsystem nobody has built): Save as template (board nav + workspace ⋯), My Work's Customize, the Gantt toolbar's Baseline/filter/⋯ affordances, the dashboard widget's Dock this widget, the workspace Feedback button (the plugin has no host bridge to Omniscio's intake), and the board-info popover's fake "🔔 Everything" notifications row. The Apps widget left the Add-widget menu, but 'apps' stays in the persisted WidgetType union and WidgetCard still renders a placeholder body for it, so a dashboard that already saved one keeps working — it just can't be added again.

Sub-pages

Last verified 2026-10-29