The view menu used the pending reactive choice, but every content-layout helper independently read the previous profile value, leaving Swimlanes visible for Lists, Calendar, Gantt, Table and Statistics selections. Both now use one source. Card rendering and counts also resolve the containing swimlane explicitly instead of relying on relative Jade context that could become undefined and remove swimlane scoping. Finally, all favorite controls persist through the authenticated server method instead of rollback-prone direct client updates. Regression coverage checks all six layouts, positive card/count scope and the absence of direct favorite writes.

A view change can destroy a swimlane before its deferred sortable setup runs. The callback then tried to select elements from a removed Blaze DOM range and raised a page-level error even though the new view rendered successfully. Deferred swimlane and list-group setup now exits after destruction. Source coverage pins both guards, and the complete browser matrix verifies all board views without the removed-range exception.

Authenticated browser tests now navigate through the live Meteor application, wait for application readiness before inspecting verification state, and retry a card click when a subscription replaces its DOM after refresh. Database conformance routes Docker commands through the host when invoked from Flatpak. The complete sequential run passed all WeKan and FerretDB stages; SQLite, PostgreSQL, MySQL and MariaDB answered all 102 conformance cases identically.