The Offices report was inverted: each row represented an address and placed all people using it inside one cell. It now pages people and keeps every address for one person together. Each row has separate IPv4 and IPv6 columns, the latest country flag and city supplied by Cloudflare or another supported proxy, and that person’s successful-login count and first/last times for that address.

Location is recorded when a login succeeds; existing address tallies are not retroactively geolocated. With Cloudflare, the proxied hostname must enable the Add visitor location headers Managed Transform so CF-IPCountry, CF-IPCity, CF-Region, CF-IPLatitude and CF-IPLongitude reach WeKan. Caddy passes these request headers through by default; any header_up override belongs inside its reverse_proxy block.

People sharing one address remain separate groups with separate counts. Search still matches names, addresses and locations, while location metadata for a page is fetched in one batch. Positive and negative coverage checks both IP families, shared addresses, supported location headers and absent geography.

The server already computed initials for every person, but person grouping dropped that field and the shared table tried to find the user again in the client cache. When the full user document was not published there, the fallback had no letters to draw and rendered an empty grey circle.

Initials now travel with the person through the response, grouped rows and shared table cell. The existing avatar template uses them directly and retains its reactive user lookup as the fallback everywhere else. Regression coverage checks both the Offices path and the generic table conversion.

A Location column immediately before Status now shows each person’s country flags and successful-login counts. Selecting a counter opens that person’s location report: countries are the left menu, busiest first, and the selected country’s shared Table.md table lists city, IPv4, IPv6 and the person’s first and last login times for every address.

The detail view has the shared search, pagination and Back controls. Location data is fetched once per People page and restricted through the same site-admin or tenant-admin scope as the People list. Unknown locations are not guessed, stale page responses are discarded, and new logins retain the available proxy location on the person’s own address tally.

Positive and negative coverage checks country totals and ordering, both IP families, city rows, timestamps, menu and table wiring, authorization limits and absent geography.

Pagination events from specialized Problems panes bubbled into the containing shared report handler. Their pane ids intentionally have no shared report configuration, so clicking Next could try to read a count from undefined and stop the requested action with a browser exception.

Event-stream and Offices controls now keep their events inside their own pane. The shared Previous, Next and search handlers also safely ignore missing or transitional report state. Regression coverage exercises both specialized pagers and the defensive shared-handler path.

The board schema made opened-card custom fields visible by default, but the schema-upgrade list omitted that new flag. Boards created before the setting therefore retained no stored default when their other default-on feature flags were repaired. The upgrade now backfills allowsCustomFields: true while still preserving an administrator’s explicit false choice.

The complete 490-suite Node run also exposed guards that still described old custom-field, date-control, card-width, initials and publication layouts, plus a security scan entering a downloaded Go toolchain under .tools. Those guards now pin the current intended behavior and scan only maintained FerretDB source.

Content detection already identified a JFIF upload as JPEG, but the MIME database did not recognize the .jfif filename suffix. The generic correction therefore appended .jpeg and stored names such as photo.jfif.jpeg.

Detected JPEG content named with .jfif now replaces that suffix with .jpeg. Downloads consequently use a conventional filename that desktop file associations can open directly, while valid .jpg and .jpeg names remain unchanged. Positive and negative tests cover replacement, non-appending and the Security Report’s sanitization reason.

Visible Edit controls on cards now use the same Font Awesome pencil-square icon as Description instead of repeating the word. This covers custom fields, Requested By, Assigned By and comments; Add remains text where it is a distinct action. Every icon is decorative to assistive technology, while its control retains the localized Edit tooltip and accessible name.

Focused coverage rejects textual Edit controls, checks the icon and accessibility attributes, and keeps the separate Add state intact.

The desktop card already had a bottom-right resize handle, but its 520px opening width was also a hard maximum, so dragging could only make the card narrower. It still opens at the compact 520px width and can now grow up to the viewport’s eight-pixel margins. Mobile remains full-screen and non-resizable.

Placement and maximized-card regression coverage checks both resize directions, the initial width, viewport ceiling, mobile behavior and maximized geometry.

The toggle continued saving the user’s customFieldsGrid preference after the card-section refactor, but the rendered container no longer read it, so nothing visibly changed. The off state now produces a compact wrapping grid and the on state makes each custom field occupy a full row, preserving the toggle’s original behavior.

Focused positive and negative coverage checks both layout classes and the persisted method wiring. A browser regression switches the layout and reloads the card to verify that the selected mode remains active.

Selecting a custom field and changing a checkbox now use acknowledged server methods with board-write and field-definition checks. A rejected optimistic client write can therefore no longer make a checkbox appear inert or make a deselected field spring back. PDF and Excel export also omit an orphan field whose definition has been deleted instead of exposing its internal ID.

Unit tests cover successful writes, authorization and field-type failures, and the orphan export case. The browser test checks a checkbox and removes its field from an opened card.

The checkbox rendered as a card field borrowed the checklist item’s event class and derived its next state from the template context. It now has a dedicated control, reads the persisted field value, and saves its boolean without allowing the click to reach visibility or checklist handlers. The Custom Fields menu remains the separate place that shows or hides the field.

Static coverage keeps the value and visibility event paths distinct. The browser regression saves both true and false from the opened card and verifies that the field remains visible after each change.

Saving the checkbox already changed the card’s boolean and its minicard badge, but the opened-card square read a nested template path that did not react to that change. It now reads the custom field’s direct persisted value, so the opened card and minicard show the same checked state immediately.

The regression test requires every opened-card checkbox checkmark to bind to value and rejects the stale data.value path.

The checkbox editor calculated its second click from the Card object captured when the template was created, so it could keep saving true instead of unchecking. It now reads the reactive field context and saves either boolean.

Custom-field values also no longer appear automatically on minicards. Card menu / Show on Card gains a Custom Fields setting that defaults to enabled; Minicard menu / Show on Minicard gains its independent Custom Fields setting that defaults to disabled. Enabling the minicard option shows assigned fields without changing their values or the opened-card setting.

Positive and negative tests cover both defaults, both menu handlers, both rendering gates and repeated checkbox toggles. Existing browser coverage that expects minicard custom fields explicitly enables the opt-in setting.

The currency editor issued an unacknowledged direct card update and closed without knowing whether the value was accepted. It now parses dot or comma decimals, rejects non-finite input, and awaits a server method that verifies card-edit permission, the board’s currency-field definition and the assigned field before storing the number. Linked cards use the same source-card route.

Its input reads the direct current value, and the standard X close control now sits immediately after Save. Static tests cover authorization, field type, finite-number validation and control order; the browser regression enters a comma-decimal amount and verifies the stored numeric value.

Text fields retain the copy button supplied by their rich-text editor. Number, checkbox, currency, date, dropdown and string-template fields now use a shared copy control beside their editable value. Date values are copied in ISO format and multi-part values are separated by newlines.

Focused interaction coverage verifies that every field type exposes a copy control and that the shared handler normalizes scalar, date and array values.

Clicking a custom field’s title or displayed value now opens its value editor. Checkbox fields keep their square as an immediate on/off control, while their title and the empty area beside the square open a staged editor with Save and Close.

Copy is hidden while a field is only being viewed. Every field editor provides the action while editing, and it copies the currently edited input rather than the previously saved value. Focused positive and negative coverage checks the view/edit boundary; the browser regression checks its editing-only visibility.

Their Blaze helpers run inside each customFieldsWD, where the current context is already a custom-field row. They tried to call the Card method customFieldsWD() on that row, throwing on every render and interrupting the surrounding card UI. Both helpers now format the row’s resolved trueValue directly, preserve numeric zero, leave empty values empty and use safe fallbacks for invalid definitions or values.

Focused regression coverage rejects the invalid Card call and checks the value, empty, numeric and String Template paths.

A linked card displayed the source fields but several editors still wrote its empty placement placeholder, while server methods required write access on the source board. A member who may edit the current board can now edit the shared source content through a visible, active link. Revoking source visibility, archiving the link, or assigning a read-only current-board role removes that delegation. Moving and archiving still affect only the linked representation.

The same source route covers titles, descriptions, dates, colors, people, labels, stickers, locations, dependencies, custom fields, checklists, subtasks, attachments, covers, watchers, minicard settings, votes and estimates. Label and custom-field definitions come from the source board, while permission to edit the card comes from the board on which the linked card is visible.

Positive and negative tests inventory the content mutators, method arguments and active-link authorization boundary. The browser regression edits the opened linked card, verifies both stored representations, then edits the source card from its own board.

Desktop PDF and text previews were fixed at 560 pixels wide, while a misplaced media query changed them to 840 pixels only on narrower screens. The overlay is now a viewport-filling flex layout: document viewers take the space between the navigation controls, images retain their aspect ratio, and mobile controls keep their compact layout. Static positive and negative tests reject another fixed desktop document width, and a browser test measures the rendered preview.

The Link dialog directly inserted its pointer card from the client, so a server rejection could undo the optimistic insert and leave the dialog open without an explanation. It now awaits one server-authoritative operation and closes only after success. The server verifies read access to the source, write access to the destination, the selected list and swimlane, and rejects archived, same-board, template and link-pointer targets.

Method tests cover the acknowledged path and invalid targets. The browser test follows the reported board, swimlane, list, card and position selection, then checks both the closed dialog and the stored linked card.

The linked-board confirmation asked Blaze for the popup’s top or bottom position after awaiting the next card number. By then its event view was no longer current, so Blaze threw There is no current view before inserting the link. The popup now captures its position when it is created and its sort calculation uses only that stored value after asynchronous work. The board selector is scoped to the same popup as well.

The regression test rejects any later Template.currentData() call inside the sort calculation and covers both placement choices.

Detect location already recognized provider URLs such as Google Maps @latitude,longitude,zoom, but a coordinate pair copied directly from a map or GPS application produced no result. The same field now accepts a complete latitude, longitude pair with optional surrounding whitespace and retains its range checks. The match is anchored to the entire input so prose that happens to contain two numbers is not mistaken for a location.

Parser tests cover both supplied formats, exact precision and the prose negative case. The browser regression enters each format through the location popup and verifies the detected latitude and longitude fields.

A linked card mixed a few source-aware getters with raw fields from its empty placement placeholder. Titles, dates and comments worked, while labels, stickers, custom fields, locations, dependencies, subtasks, colors, creator details and other direct fields could disappear. After reload, the source board’s label and custom-field definitions were also absent because only the source card document and children were published.

Linked cards now resolve displayed content through one live source-card path. The current-board publication supplies the authorized source metadata, definition records, relevant users, subtasks and dependency targets; all remain behind the existing source-board visibility check, and child-card queries are constrained to those authorized boards. Placement itself still belongs to the linked placeholder on the current board.

Parity tests cover every directly rendered collection and the negative publication boundaries. The browser regression adds a source label, sticker, custom field and location, then verifies them on both the linked minicard and its opened details.

Shared tabs now expose tablist, tab and tabpanel relationships, keep only the active tab in normal Tab order, and support arrow, Home, End, Enter and Space keys. Popups and modals move focus inside, contain forward and reverse Tab navigation, and return focus to their opener when closed. Password visibility is no longer skipped by Tab, card and minicard edit targets are focusable, and all template images explicitly provide meaningful or intentionally empty alternative text.

Application-wide static coverage rejects positive tabindex values and images without alt, while focused tests pin names, roles, relationships, keyboard handlers and focus restoration. The browser regression audits representative pages for natural order, unnamed controls and missing image alternatives, and exercises both directions of the popup focus loop.

Popup, modal and board-menu focus previously discovered controls independently, while shared tabs and Archive tabs separately implemented the same six-key navigation rule. Focusable-element discovery, initial focus, Tab trapping and tab-key calculation now live together in client/lib/accessibility.js; each consumer supplies only its own state transition. The board-only menu observer also disconnects with its template instead of remaining attached after leaving a board.

Regression coverage requires both tab implementations and every dialog consumer to delegate to the shared helpers, and rejects copies of the old key and focus selector branches.

The archived-board half of #6608 is handled by the new Global-Admin-only, explicitly enabled and confirmed multi-selection Delete action. For cards, the sidebar previously fired direct client updates and closed immediately, so a refused write looked successful while every card stayed in place. It now sends one ordered selection to an awaited server method. The server validates the board, write access and every live card before archiving the first; a failure reports its reason and keeps the selection open. Unit tests cover positive and negative client/server paths, and a browser test selects and archives two cards from one list.

The compact phone layout forced every board icon to exactly four rem, including an invitation that also contains its explanatory message and two touch-size buttons. The board tile clipped that overflow, leaving only the title visible. Invitation tiles now carry an explicit state class and retain the ordinary four-rem floor while growing naturally around the message, Accept and Decline. Ordinary board icons remain compact and equal-height.

Static coverage keeps the invitation exception attached to its template state. The phone browser regression creates a real pending invitation and verifies that its message and both buttons remain visible and inside the tile.

The all-browser run exposed interactions that narrower source tests could not: the minicard wrapper stopped its sibling inline-title handler, shared opened-card date badges lost the explicit edit-permission argument, popup Tab handling used Blaze’s inconsistent delegated event container, and the stock logo briefly lost its alternative text while settings loaded. Those paths now retain editing permission, focus containment and accessible loading states.

The shared table search has an accessible name and a phone’s board list grows inside the single page scroller. Browser coverage now opens the attachment viewer where that template exists, scopes the linked-card and custom-field controls to their real DOM owners, waits for reactive options and fields, and checks the icon-only Edit control by its accessible name. Focused positive and negative source tests pin the permission, focus, table and scroll contracts.

Linked-card creation now restarts the board subscription so source labels, stickers and custom fields are available with the new link. Date writes are awaited and refresh the same subscription, popup focus trapping uses the real dialog element, and the phone board grid leaves vertical scrolling to the page.

The browser tests now use stable card identities and the actual interactive DOM targets after titles change, distinguish visible and compact label markup, seed existing dates before subscribing, and measure scroll ownership instead of relying on a browser’s normalized overflow keyword. The complete Node suite and the modified Chromium browser group cover the positive and negative paths.

Rspack’s experimental persistent cache retained JavaScript-side serialization state while meteor run repeatedly rebuilt WeKan’s large Blaze graph. After a long development session that retained state could consume the full 16 GB V8 heap and abort the bundler.

Development client and server watchers now run without the persistent cache. Short-lived production builds keep caching, and unrelated Rspack experiments still merge normally. Focused coverage checks both watchers, the production negative case and the merge over Meteor’s cache defaults.

The ARM64 browser runner correctly selected Playwright’s official Docker image, but a VS Code Flatpak terminal could not see the host docker executable and reported that Docker was not installed. The build script now discovers Docker through flatpak-spawn --host and routes image pulls, browser containers and conformance cleanup through the same host-aware wrapper.

Regression coverage pins both direct and Flatpak-host discovery. The complete Firefox and WebKit matrices were run against a fresh production bundle; all 255 runnable tests passed in each engine, with the eight Chromium-only drag harness tests intentionally skipped.