Přeskočit na hlavní obsah

v9

UCS Operator - changelog

All notable changes to this project will be documented in this file.

[9.58.0] - 2026-11-18​

🚀 Features​

  • (ui) Let DataTable render long lists a page at a time
    • A blacklist can hold thousands of records, and rendering every row of such a list makes the admin page slow to open and to filter. DataTable gets an optional rowLimit: it sorts the whole data set as before, renders the first rowLimit rows, and offers "Show N more" with a "Showing x of y" line below the table. Select-all keeps covering the rows rendered.

Tables without rowLimit render every row, as before. This avoids adding @tanstack/react-virtual until a list needs to scroll through thousands of rows at once.

  • (admin) Port blacklists
    • Blacklists (lists of numbers that trunk incoming rules and outgoing filters check as a blacklist or a whitelist) move from the PHP admin to /admin/telephony/blacklists. The list page shows each list's group, record count and use, filters by name, group and use (including "empty whitelists", which hang up every call), and moves or deletes lists in bulk. A list's page holds its records: an inline box adds several caller numbers at once, each as its own record with the same called number, action and note; records are edited in a dialog, filtered by number, note and action, deleted in bulk, and rendered 200 at a time. "Used by" lists the trunk rules and filters checking the list, each as a blacklist or a whitelist.

The server stores a record as the Asterisk DB key | of its list, so numbers match exactly and two records with the same pair share one key: UCS keeps one action, and changing or deleting either drops both. The server refuses a duplicate only when the action matches too, so the admin refuses the pair itself and flags existing ones. A record without numbers never matches and is refused. The action is a choice instead of PHP's free text: the empty default (hang up on a blacklist, continue on a whitelist), PASS, or a number to forward to.

Deleting a list cascades its uses on trunk rules and filters without rebuilding the dial plan, so a whitelist use hangs up every call until the next rebuild; the delete confirms warn, and the issue is deferred server work Q. Usage and record counts come from structure.select and stay hidden for admins who are not superusers.

Design decisions (new design tokens, as for all admin work): warnings and the "same numbers" and "empty whitelist" chips use ds-warn-soft / ds-warn, the whitelist chip ds-tag-bg / ds-tag-fg; no new tokens, radii or font sizes.

  • (admin) Port telephone services
    • Telephone services (the menu items IP phones open from their services key) move from the PHP admin to /admin/telephony/phone-applications: a list with the URL, group and use, filters by name or URL, group and use, bulk change group and delete; an add page; and a detail page with the form and "Used by".

UCS assigns services only inside settings sets (settings.data JSON, applications[].application_id and url_append), with no foreign key. "Used by" parses that data and follows the sets to the groups and extensions taking them, linked to the number plan. A delete leaves the entries in the settings sets and provisioning skips them, which the delete confirmation says.

The PHP note listing UCS's built-in services moves into the form, each with "Use", and the form and the list say where phones load the URL from, the way provisioning builds it: as is for the phone's own service, from the UCS server over HTTP for a path, or from the server named in an address with //.

list returns the URL only when asked for columns, so the list passes [null, columns]. edit takes partial data, so a bulk group change sends only the id and the group.

Design decisions (new design tokens, as for all admin work): ds-muted for the address kind and help, the shared ghost button for "Use"; no new tokens.

  • (admin) Port recording storages
    • Recording storages move from the PHP admin to /admin/telephony/recording-storages: a list with path, type, format, retention ("30 days, then to Archive"), recording count and use, filtered by name or path, group and use, with bulk change group and delete; an add page; and a detail page with the form in sections and "Used by" (trunk incoming rules, outgoing filter patterns, settings sets, roles, and storages moving expired recordings here).

UCS finds each recording's file through its storage's current path pattern, so changing the path of a storage that holds recordings makes them unplayable and expiry later deletes their records as missing. Changing "keep" or the protection default rewrites the expiry and protection of every recording already in the storage. The form warns before saving either, previews today's directory, notes storages sharing the path, and flags a circle of "move expired to". A bulk group change sends only the id and group, so it rewrites no recording.

Deleting a storage deletes its recordings' records (CASCADE; files stay), leaves trunk rules, filter patterns, roles and other storages without it, and leaves settings sets pointing at it, which drops their recordings; storage #1 is UCS's fallback. The confirmations say all of this with counts, read with structure.select (hidden for admins who are not superusers). Empty speech-to-text limit and priority send UCS's defaults instead of PHP's 0, which is out of range for the priority. The server issues are deferred item R.

Design decisions (new design tokens, as for all admin work): ds-danger-soft / ds-danger for the path-change warning (data loss), ds-warn-soft / ds-warn for the retention and circle warnings, ds-muted for previews; no new tokens.

  • (admin) Add a last-updated line for live admin pages
    • Status pages refresh themselves by websocket events or polling, and an admin looking at them needs to know how fresh the data is and to be able to ask for it now. LastUpdated shows "Updated

It came out of the Status menu port, where every page had built the same control.

  • (admin) Port the telephones status page
    • Status › Telephones moves from the PHP admin to /admin/status/phones: one row per extension or hot-desk line with its device, SIP username, outgoing filter and state (online, offline, not monitored, unknown, in a call, ringing), with the address and round-trip time when known. It filters by text, state, desk or web phones and device group (with subgroups), and a summary counts the lines online and offers the offline desk phones as a filter (an offline web phone is not a problem).

peer.change fires on every ring and answer, so it patches the matching row in the cache instead of refetching the whole list; address and round-trip changes send no event, so the page also polls every 15 s, and device, line and extension events refetch it. Devices link to their pages; for superusers the extension links to the number plan and the signed-in or web-phone user to the user page, read with structure.select (relations/phone-lines.ts).

A line without a SIP username on a device without a MAC is looked up under a name provisioning never uses, so it can never show a state; it shows as Unknown with the reason. status.phones checks no permission or group. Both are deferred item S.

  • (admin) Port the registry status page
    • Status › Registry moves from the PHP admin to /admin/status/registry: one row per trunk registration (a number range has one per number) with trunk, user name, SIP proxy, state, last registration and refresh interval. States are Registered, Rejected, Authenticating and Not registered, the last three counted as failing; a trunk that is inactive, or registers with its own registrar, gets an explaining state instead of a blank (from config.trunks.list). It filters by text, state (with "Failing") and trunk, and the summary offers the failing ones as a filter.

UCS reads registration states from Asterisk only when it connects to the AMI and never subscribes to registry events, so the states date from the last UCS or Asterisk start. The page says so and counts the registrations due for renewal since then instead of claiming to be live; it still refetches on registry.change and trunk events and polls every 30 s. A registering trunk without a SIP proxy makes status.registrations fail as a whole (-1000); the page names that cause. These, a range without a dash and the missing permission check are deferred item S.

  • (admin) Port the remote clients status page
    • Status › Remote clients moves from the PHP admin to /admin/status/clients: the applications and integrations signed in to UCS with a session of their own, and the XMPP clients (DCom), one row per connection with the user (linked to the user page), presence, connection kind, address, last activity and version. It filters by text, connection and presence, and says how many users and connections there are. The web operator and this admin sign in through uAuth and never appear; the page says so.

status.clients returns {sessions, xmpp}, not the keys its method help describes, with last_seen as float seconds. Nothing is emitted when a session expires or a client disconnects, so the list polls every 10 s; user.login and user.status refetch it and the presence names. PHP had no action and the server has none to drop another user's session, so there is none here. status.clients checks nothing beyond a signed-in user: anyone can list every client's address and version (deferred item S).

  • (admin) Port the inbound queues status page
    • Status › Inbound queues moves from the PHP admin to /admin/status/queues: a list of queues with callers waiting and connected, the longest current wait, agents by status (warned when nobody is logged in), calls, abandoned share and service level, filtered by text, group (with subgroups) and "callers waiting" / "no agent logged in"; and a page per queue with its stat tiles, callers (state, wait and talk time ticking every second, agent) and member agents (status with AUX reason, paused in this queue, phone activity, calls, talk, ACW and AUX time), linked to the user pages.

One query reads status.queues and queues.agents together; queue.stats, agent.status and agent suspend/resume events refetch it, with a 10 s poll behind them. PHP had no actions on this page, so there are none; suspend, resume and resetting statistics exist on the server and are noted as a proposal.

Fixed while porting: soft-deleted queues, which status.queues returns after a server restart, are hidden; a caller's wait stops at the answer (the server keeps counting); an external number is no longer shown as a desk phone; an agent busy with a chat or e-mail is not counted as on a call. With no calls yet the shares show "–" instead of 0 %. status.queues checks no access, so any signed-in user sees every queue and its callers' numbers (deferred item S).

  • (admin) Port the voicemail messages page
    • Status › Voicemail messages moves from the PHP admin to /admin/status/voicemail: messages newest first with received time, caller, mailbox (linked to its extension), folder and length, filtered by caller or mailbox, mailbox, folder and date range. A message plays in the browser (voicemail.download, base64), downloads as a file, or plays on the admin's own phone (voicemail.playback, the only playback PHP had). It is deleted one at a time or in bulk, with the progress dialog and a typed count from 20 up. voicemail.new refetches the list, with a 60 s poll for deletions made elsewhere.

The page loads the newest 1000 messages for the chosen mailbox and dates (PHP paged 20 at a time) and says when older ones are cut off.

Worked around: voicemail.messages applies only the end date when given both, so the start is filtered in the browser; rows carry another mailbox's name, so the mailbox comes from the voicemails enum; no mailbox gives {} instead of an empty list. A message's folder is never updated once it is heard, so there is a folder filter, not a new/heard one. Superusers see only Voicemail extensions' mailboxes, as in PHP, and the page says so. Deferred item S.

  • (admin) Port the outgoing SMS status page
    • Status › Outgoing SMS moves from the PHP admin to /admin/status/sms: the SMS waiting for their gateway, in the order the server works through them (being sent first, then by next attempt), with recipient, queue, user, enqueued and next-attempt times and the last error; failed attempts are counted in red and a warning line appears when anything has failed. It filters by text, state ("failed at least once" included), queue and gateway.

PHP's "abort" is "Remove from queue", one at a time or in bulk. An SMS being sent cannot be removed: removing it would only lose its record while the gateway still sends it, so it gets no action and bulk skips it with a warning. sms.abort answers null when the SMS has already left the queue; the page reports that instead of a success. Nothing is emitted when an SMS is enqueued, retried or aborted, so the list polls every 10 s besides the sending/sent/error events.

The server retries 5 times 300 s apart and then drops the SMS without a record, which the page says. Queued SMS are stranded after a UCS restart and Gateway.cancel stops only the first SMS waiting at a gateway (deferred item S). The time formatting and the state chip live here and are reused by the FAX page.

  • (admin) Port the outgoing FAX status page
    • Status › Outgoing FAX moves from the PHP admin to /admin/status/fax: the FAX jobs waiting to be sent, in the order the server works through them, with recipient, FAX extension (names from config.extensions.list), enqueued and next-attempt times and the last error, filtered by text, state and FAX machine, with a warning line when anything has failed. Retries follow the FAX_RETRY_* parameters, which the page names.

PHP's "abort" is "Remove from queue", one at a time or in bulk. fax.abort is superuser-only, writes "Aborted by user" to the FAX journal and mails the sender. A job being sent can still be removed, with a warning that the call is not hung up: removal is the only way out of a job stuck in "Sending", which is what a job marked sending at a restart becomes. fax.queued and fax.aborted refetch the list, with a 10 s poll for retries, which send no event.

The last error of a live job stays empty because the server writes the retry note only to the database, and fax.status's filter compares a variable with itself (deferred item S). Reuses the time formatting and state chip of the SMS page.

  • (admin) Show INSOFT kiosks as their own kind on the telephones page
    • Kiosks were counted as desk phones. INSOFT kiosk runs the same app as INSOFT uPhone, but on Tipro BeFree tabletop devices, so it is neither a plain desk phone nor a softphone. It becomes a third kind beside desk phones and softphones (web phone, uPhone): the kind filter offers it, and since a kiosk stands on a desk and is expected to be online, an offline kiosk line counts as a problem with its own "kiosk lines offline" summary button, next to the desk phone one.

Kinds come from the device type (1000 uPhone → softphone, 1001 kiosk → kiosk), read from config.devices.list because status.phones gives only the type name. FEATURE.md explains the three kinds.

  • (supervisor) Add setting to hide agent state duration
    • The Agent overview shows a timer next to each agent's name with the time spent in the current state. Some teams find it distracting or do not want agents to see how long colleagues have been in a state, so a new "Hide duration in agent state" setting removes it.

The flag is passed down as a prop along the same path as skipSuspended (SupervisorView -> AgentStats -> AgentStatsRows -> AgentStatsRow -> AgentButton). AgentButton gets an optional hideDuration prop defaulting to false, so its other user is unchanged.

  • (admin) Add a date range filter and a pager for report lists

    • The report pages (call detail records, presence and login logs, statistics, the SMS and FAX journals, the audit log) all filter by a date range and most page on the server. These pieces keep that consistent before the pages are ported:
  • date-range.ts turns from/to days, picked in the user's timezone, into the UTC instants the server's DateTime validator accepts, so a day covers the user's hours rather than the server's (PHP sent Prague wall-clock times). pageOffset maps a 1-based page URL filter to the offset.

  • DateRangeFilter is the From/To pair of date inputs for a list toolbar.

  • ListPager shows "1–50 of N" with Previous/Next for methods that take limit and offset and return [rows, total].

foundations.md lists them with LastUpdated.

  • (admin) Port the call detail records report
    • Reports › Call detail records moves from the PHP admin to /admin/reports/cdr: finished calls newest first with date, caller and called (users and extensions linked), path, duration, price, account code and recording, filtered by exact number, date range (today by default, as in PHP), group or extension, all in the address, paged on the server 50 at a time, with an Excel export of everything the filters match. The number plan's "Call records" links for groups and extensions now open it instead of PHP.

Recordings play inline and download. When the recording audit asks for a reason the page asks first (downloads up front, as PHP did; playback after the server says so), checks access with a two-byte status.recording call that also writes the audit entry, and then streams the audio from the api service's existing /recording route, which the operator already uses, so a long recording does not travel as base64 through one RPC call. Superusers may remove a recording when DELETE_RECORDINGS allows it, with a reason.

Worth knowing: status.cdr without a start silently means the last 31 days, so the page always sends one; a group includes its subgroups; the cdr table keeps no trunk, so calls cannot link to trunks; all Excel reports share one server lock. Deferred item T.

  • (admin) Port the users presence report
    • Reports › Users presence moves from the PHP admin to /admin/reports/presence: how long each user spent in each presence state over a date range (today by default, as in PHP), with totals and per-user averages as tiles, filtered by name and group (with subgroups) in the address, an Excel export, and a history page per user (/admin/reports/presence/:userId) with each change, paged on the server.

Durations are filled in by the database when the next change arrives, so the newest change has none and the current state is never counted; the range selects changes by when they started without clipping them. When the LOG_PRESENCE parameter is off nothing is recorded, and superusers see a note saying so (config.parameters.get is superuser-only). The Excel export covers every user, whatever the filters. The summary helpers (dates, durations, user labels, export) live here and the agents logins report reuses them.

  • (admin) Port the agents logins report
    • Reports › Agents logins moves from the PHP admin to /admin/reports/agent-logins: how long each agent spent logged in to queues by state (ready, ACW, AUX, offline) over a date range, with a "logged in" total, tiles with totals and averages, filters by name and group in the address, an Excel export (of the agents shown when filtered, otherwise of everyone the admin may see), and a history page per agent with each change, including call and phone events and waiting callers, paged on the server. It reuses the presence report's helpers.

On ekancl the summary failed: status.agents keeps four slots per agent and raises "list assignment index out of range" as soon as the range holds an older agent_logins row of a later state with a duration, and PHP fails the same way. When that happens and the admin is a superuser, the page sums states 0–3 itself through structure.select (relations/agent-logins.ts, with a guard that lets only UTC instants into the SQL) and says where the totals came from. Deferred item T.

  • (admin) Port the agents statistics report
    • Reports › Agents statistics moves from the PHP admin to /admin/reports/agent-stats: each agent's queue work over a date range (answered, unanswered and transferred calls, talk, ready, ACW, AUX and break time), with total tiles, a legend that says what each figure means, filters by name and group in the address and an XLSX export; and a page per agent broken down by year, month, week, day, hour or statistics period, chosen in the address or by the length of the range. Unanswered, transferred and break time are new here; the server and the export had them, PHP's page did not.

status.agentsStats divides the ready, ACW, AUX and break sums by the agent's distinct queues over the whole group, so they come out too low when the agent's queues changed during the range; only the per-period breakdown and the export are exact. The page shows the server's figures as PHP did and says so above the legend (deferred item T). Figures are saved at the end of each statistics period, so the last minutes are missing, which the page says too. The period selection, labels, export button and legend live here and the queue statistics report reuses them.

  • (admin) Port the inbound queue statistics report
    • Reports › Inbound queue statistics moves from the PHP admin to /admin/reports/queue-stats: each inbound queue's calls over a date range (answered, abandoned, overflowed), service level, answer rate, waiting and talk times, with total tiles, a legend, filters by name and group in the address and an XLSX export; and a page per queue broken down by period, with a link to its live status. Totals add up the counts and derive the rates from the sums (PHP's totals row was misaligned).

PHP and the export call the answer rate "AR (Abandoned Ratio)" although it is answered / (answered + abandoned after the threshold); the page names it "Answer rate" and the legend says so. Service level here is answered in time out of answered, unlike the live queue page, which also counts calls abandoned within the threshold; the legend explains the difference. Calls dropped because the queue was full count as abandoned; overflowed calls are in neither. An export of an empty range crashes the server, so the button waits for data. Deferred item T.

  • (admin) Port the SMS messages journal
    • Reports › SMS messages moves from the PHP admin to /admin/reports/sms: SMS sent and received through the SMS queues, newest first, with direction, sender, recipient, the message text (PHP did not show it), queue, user and delivery report, filtered by exact number and queue and by date range (today by default, as in PHP), in the address and paged on the server. It refreshes on sms.sent, sms.received and sms.delivered and links to the Outgoing SMS queue, whose empty state now links here instead of to PHP.

Only SMS that a gateway actually sent are recorded; one that failed for good leaves no trace (the queue page says so), so PHP's red "FAIL" only ever meant "no delivery report", which is what the page shows. The number filter is an exact match on the stored +… form. sms.list checks no permission: any signed-in user can read every SMS with its text (deferred item T).

  • (admin) Port the FAX journal
    • Reports › FAX journal moves from the PHP admin to /admin/reports/fax: FAX documents received and sent by the FAX machines, newest first, with machine (linked to its extension), direction, caller, called, pages and outcome (Transmitted or Failed, with the note), filtered by machine, direction (the server supports it, PHP did not offer it) and date range, in the address and paged on the server. A kept document downloads as a PDF under PHP's file name; superusers and admins with billing access may delete documents, one at a time or in bulk (rows without a document are skipped). It refreshes on fax.received and fax.aborted and links to the Outgoing FAX queue, whose empty state now links here instead of to PHP.

fax.journal checks for the PDF at a hard-coded path while download and delete use FAX_ROOT, so the document flag can be wrong; a deleted FAX machine's entries disappear (inner join); fax.remove sends no event; fax.journal checks no permission. Deferred item T.

  • (admin) Port the audit log
    • Reports › Audit log moves from the PHP admin to /admin/reports/audit: who changed the configuration or looked at call details and recordings, newest first, with time, user (linked), group, action (section and operation with the raw code under it) and details, filtered by user, section, operation and date range (today by default) in the address, paged on the server and refreshed every minute on the first page (no event announces new entries). PHP could filter by none of these but the dates and user.

Details read the logged data: an update lists the changed fields as old → new, a creation or deletion the record's values, behind a disclosure past two fields; the record id and the reason of a recording access come first. UCS logs password hashes and trunk secrets as they are, so fields named like a password, secret, PIN or token show only that they changed (the server should mask them; deferred item T).

status.auditlog matches actions exactly from a list (an empty list returns nothing), so the section filter uses the page's own list of about 280 action codes; an action added to UCS later appears only while no section or operation is chosen. Reverting from the log is not built (a question for the team in the backlog).

  • (admin) Add an editor for queue metadata fields
    • E-mail, SMS and chat queues (and later task queues and teams) carry the same metadata struct: an ordered list of fields agents fill in, each with a key, a name and a type (text, number, checkbox, radio, select with options, or a button that opens a URL, an operator tab or a desktop application). The Messaging ports need one editor for it rather than three.

api/metadata-variables.ts parses what the server sends leniently (missing key, name or type), keeps the data of unknown types and sends it back unchanged, and checks a field before saving: key required and unique, name required, at least one complete option for radio and select, a URL or an application name for buttons. components/MetadataVariables lists the fields with add, edit, remove and reorder; MetadataVariableDialog and MetadataOptionsEditor edit one field and its options.

The button URL help names {ID}, {NOTE} and {key}: the operator still accepts the %ID% form PHP documented but converts it as deprecated (lib/expandTemplate). For an application button the field holds the name of an application set up in the Operator desktop app. foundations.md no longer says MetadataEditor (key/value pairs) is for queue metadata.

  • (admin) Port the e-mail queues
    • Messaging › Email queues moves from the PHP admin to /admin/messaging/email-queues: a list with languages, agents, e-mail sources, a setup column (no agent, no source or no sender) and the e-mail count, filtered by name, status, group and setup in the address, with bulk change group, activate, deactivate and delete; an add page; and a queue page with a Settings tab (every PHP field in sections, languages with default reply templates, ordered senders, metadata fields) and an Agents tab that saves at once (several users added together, priority, most e-mails at once, language skills, reorder). "Used by" lists the e-mail sources delivering into the queue and the source filters copying or moving e-mails into it.

Deleting a queue cascades to its sources, every e-mail in it, statistics, memberships, senders and templates, while the server keeps the deleted sources (and agents the queue) in memory until a restart; the confirm names the sources and counts the e-mails. Queue edits reach agents only after a restart or when their membership is saved again, so a changed Active warns. An empty priority or "most e-mails at once" now takes the user's team default (PHP always sent 100 and 0); removing an agent sends their open e-mails back to the queue, which the dialogs say. Deferred item U.

  • (admin) Port the e-mail sources
    • Messaging › Email sources moves from the PHP admin to /admin/messaging/email-sources: the mailboxes UCS fetches e-mail from, with server, queue (linked), group and filter count, filtered by status, queue, type and group; an add page; and a source page with every PHP field and a "Related" panel (the queue it delivers to, its filters, the other sources of that queue).

The UCS server does not fetch e-mail: each source is fetched by its own ucs-email-fetcher@ systemd unit (email-fetcher repo), which nothing enables when a source is added, reads its settings only at start and never checks Active. The page says so and labels Active as overview only. The server stores settings the fetcher cannot run with (no port connects to port 0, no fetch interval or no IMAP password crashes it), so the form requires queue, host, port, username, password and fetch interval, which PHP did not. POP3 fetching is broken in the fetcher (it refetches everything, or stops after one message), which the form warns about. Passwords stay write-only: get returns them in clear and the page drops them; one starting with http:// is an OAuth 2.0 token URL. A duplicate name, -6 in English without a field, lands on the name field. Deferred item U.

  • (admin) Port the e-mail senders
    • Messaging › Email senders moves from the PHP admin to /admin/messaging/email-senders: the SMTP accounts UCS sends e-mail through, with sender address, server, group and the queues using each, filtered by type, group and use; an add page; and a sender page with every PHP field, the queues sending through it in "Used by", and a new "Retry sending now" action (email.sender.flush), which wakes the sender and says how many e-mails were waiting. It reuses the e-mail sources' helpers for passwords, ports and names.

A queue sends through the sender whose address equals the e-mail's From, otherwise through its first sender; an empty port means 25 (465 for SSL/TLS); UCS signs in only with both username and password, and retries an unreachable server every 60 s without limit. The page says all of it. Deleting a sender stays in its queues' memory until a restart or queue save, and with an e-mail still waiting it can stop the e-mail module from loading after a restart; the confirm warns (deferred item U, with the other sender bugs found).

  • (admin) Port the chat queues
    • Messaging › Chat queues moves from the PHP admin to /admin/messaging/chat-queues: queues for the web chat and Facebook messages, with their id, type, time limits, metadata fields, group, message count and use, filtered by type, status and group, with bulk actions; an add page; and a queue page with every PHP field, the metadata fields agents fill in, and "Used by" (chat notifiers watching the queue).

UCS stores Active, SLA and the agent timeout but never acts on them: chat.message accepts messages for an inactive queue, which the help text says. PHP also sent languages, default templates and senders, which are not in the struct and were dropped by the validator. config.chat.edit needs name and group even for a partial edit, so bulk edits send them. Deleting a queue deletes its chat messages, and chat notifiers keep its id and never fire again; the confirm shows both. Deferred item U.

  • (admin) Port the SMS queues
    • Messaging › SMS queues moves from the PHP admin to /admin/messaging/sms-queues: queues with the gateways they send through and receive from, group and use (waiting SMS, notifiers), filtered by group, status and gateway; an add page; and a queue page with a Settings tab (every PHP field, metadata fields) and an "Outgoing gateways" tab that saves at once (add, edit, reorder; PHP's position field became up/down). The SMS queries and the part of a gateway the queue pages need live here; the gateway pages build on them.

A queue with two or more gateways uses them in turn, but the turn counter runs past the end of the list, so after each gateway has sent once every further SMS is refused until UCS restarts; removing a gateway can break a queue the same way, and removing the last one has no effect until restart. The gateways tab warns. UCS stores Active, SLA and timeout but never reads them; the form says so. editQueueGateway's duplicate check swaps gateway and queue. PHP's keys outside the struct were dropped by the server and are not sent. Deferred item U.

  • (admin) Port the SMS gateways
    • Messaging › SMS gateways moves from the PHP admin to /admin/messaging/sms-gateways: the modems and services UCS sends and receives SMS through, with type, the queues sending through each and the queue it receives into, filtered by group, type, state and use, with bulk enable, disable and delete; an add page; and a gateway page with the settings of its type (credentials write-only), the incoming queue, the queues sending through it, and "Used by".

The group is chosen when the gateway is added and shown read-only after, as PHP did on purpose ("dont allow group change"): the server checks rights on the old group only. PHP never saved the MEX GATE sender (wrong input name); the port does. getGateway returns the O2 client private key in clear; the form keeps it write-only. A disabled gateway stays in its queues' rotation and the SMS handed to it wait until it is enabled; 2N VoiceBlue has no driver, so its SMS are recorded as sent but never leave; a running gateway keeps its incoming queue until a restart; a receiving gateway without a queue drops what it receives. The form and confirms say so (deferred item U). Lists read each gateway with get, because the list method takes no column argument.

  • (admin) Port the message templates
    • Messaging › Message templates moves from the PHP admin to /admin/messaging/templates: the texts agents insert into e-mails, SMS and task notes, with where each can be used, type, variables, group and use, filtered by use, type and group; an add page; and a template page with every PHP field, the content in the operator's e-mail editor (Froala, no autosave; what Froala changes in the loaded HTML is not an edit), variables and attachments, which PHP left alone. "Used by" lists the e-mail queues using it as a reply template per language and the task queues using it for new task notes.

A new template is added first and its content written on its page, because pictures pasted into the editor upload as attachments of an existing template. The server takes empty content as "unchanged", so the form refuses to save it empty. Names are unique across groups; -6 lands on the name field. PHP's type had no default and an add without it failed; new templates start as inserted text. Deleting a template removes it from the queues using it, but e-mail and task queues keep its id in memory until saved again or UCS restarts, so new e-mails or task notes there can fail; the confirm warns (deferred item U).

The editor and the template checklist are the operator's components, reused unchanged; the attachment manager inside them reads the Redux store, so admin reaches the store indirectly here.

  • (admin) Edit a message template as HTML in the code editor
    • The template page only had the visual editor (Froala). The admin can now choose, above the content, between the visual editor and the HTML in Monaco (the bundled editor, loaded only when chosen); the choice is remembered in that browser, and the visual editor stays the default.

Both edit the same text, so switching keeps the changes. Froala rewrites the HTML it loads and reports that as a change, which the page ignores until the admin has used the editor; after the editor has been used, the rewrite that follows a switch from HTML counts as an edit, so the form stays unsaved instead of taking the rewritten text as the saved one. Pictures and attachments stay in the visual editor.

🐛 Bug Fixes​

  • (admin) Count INSOFT uPhone as a softphone on the telephones page
    • The telephones status page took only the operator's web phone (a PJSIP peer) for a softphone, so every closed INSOFT uPhone app counted as an offline desk phone: it was flagged in warning colours and raised "desk phone lines offline". uPhone is a softphone like the web phone, offline whenever its app is closed, so lines on devices of type 1000 now count as softphones. The kind filter offers desk phones and softphones (web phone, uPhone).

INSOFT kiosk (type 1001) stays a desk phone: it runs the same app, but on a Tipro BeFree tabletop device that stands on a desk and is expected to be online. FEATURE.md and the hidden semantics say so.

status.phones names the device type but not its id, so the ids come from config.devices.list, shared with the devices page's query.

  • (admin) Keep the SLA of chat and SMS queues when saving untouched
    • The chat and SMS queue forms showed the SLA and agent timeout rounded to two decimals of an hour or minute, so a 90 s SLA loaded as 0.03 h and was saved as 108 s without the field being touched; any value that is not a multiple of 36 s (or 0.6 s for minutes) changed on every save. They now use four decimals, as the e-mail queue form does, which round-trip to the same whole seconds.
  • (admin) Start a report at the end date when only the end is set
    • An empty "From" in the report filters means today, as in PHP. With only "To" set to an earlier day that gave an empty range (begin today, end in the past) and no hint why, in the call detail records, audit log, SMS and FAX journals, presence, agent logins and agent statistics. The default start is now never after the chosen end ("up to 1 November" starts that day), through one helper in date-range.ts that the pages' date inputs and the Excel exports use too.
  • (admin) Ignore a non-numeric queue, machine or direction in a report URL
    • The FAX journal and SMS journal turned ?fax=abc, ?direction=x or ?queue=abc into NaN, which JSON sends as null, so the filter was silently dropped while the filter box still showed the garbage. A shared filterNumber reads a whole number or means "no filter", as the call detail records and audit log already did for their ids.
  • (admin) Mask private keys in the audit log, not the pin switches
    • The audit log hides values of fields named like a password, secret, pin or token, because UCS logs them as they are. Private and API keys (ssl_key and the like) were still shown, while always_pin and require_pin, which are plain on/off settings, were masked although their change is worth reading.

🚜 Refactor​

  • (supervisor) Render agent overview columns with ternaries
    • AgentStats and AgentStatsRow rendered every optional column as cond && <X />, which the operator/jsx-ternary-not-and lint rule flags because a numeric condition would render a stray 0. Switch them to cond ? <X /> : null. No behaviour change.
  • (supervisor) Name the memoized agent stats rows component
    • oxlint's react/display-name flagged the anonymous arrow inside memo() in AgentStatsRows, which also shows up as Anonymous in React devtools. Set displayName so the component is identifiable.
  • (admin) Share the stat tile, percentage and today helpers
    • The report pages about to be ported show figures in the same tiles and percentages as the inbound queue status page, and default their date ranges to today. They would otherwise import them from the queue status section and the holidays model. StatTile and Percentage move to components/ and todayIso to date-range.ts, next to the other date filter helpers; the queue status and holiday pages import them from there. No behaviour changes.
  • (admin) Move the row id helper out of the metadata editor component
    • The admin API layer (metadata-variables.ts) imported newRowId from a React component file, which pulls component code into model and test imports and invites a circular import. It now lives in row-id.ts, and the editors, the template pages and the user metadata tab import it from there.

📚 Documentation​

  • (admin) Note the work planned after the rewrite
    • The rewrite keeps the PHP admin's sections and pages, each doing at least what it did, with enhancements within the pages. Radical changes wait until it is done: moving the user-facing reports (call detail records, presence, agents logins and statistics, queue statistics, SMS messages, FAX journal) out of admin into the user part of the operator, keeping only the audit log in admin; removing or merging pages; and the UX refactoring from the backlog.

[9.57.0] - 2026-11-16​

🚀 Features​

  • (chat) Replace docked chat boxes with a tabbed chat window (wip)
    • The old colleague chat was a row of docked boxes backed by an Immutable Redux reducer, with a "Sessions" overflow list and a blinking title as the only signal for a new message. It had no room for group conversations, which issue 452 needs.

Replace it with ChatWindow: one window docked in the bottom-right corner, one tab per conversation, up to three visible and the rest behind "+N". Sessions and messages move from the chat reducer to TanStack Query (chat-sessions-query, chat-messages-query) over the presence.* RPCs, so the reducer, its actions and the whole components/Chat directory go away. Group conversations the user already belongs to are listed and usable; creating or managing them from Operator is not there yet.

A new message shows as a preview above the window instead of blinking. It does not take focus and does not mark the conversation read. Conversations can be muted per browser, and the new "Hold chat previews during calls" setting collects previews into one summary when the call ends. It takes the place of the "Automatically open last session" checkbox in the settings form; the autoOpen value itself is still in the settings model.

The window is rendered only when "Show Chat" is on and is keyed by the user id so impersonation starts from a clean state.

Work in progress: pushed to share the state of the branch, not as a finished feature.

  • (chat) Show colleagues as active or offline and group the chat window files
    • Colleague status in the chat window mirrored the agent state (Ready, ACW, Not ready) with the colours configured in the UCS administration. Chat never asks for immediate attention, so a colleague's call-handling state says nothing about whether you can write to them. Presence is now just Active when the user is signed in to UCS and Offline otherwise, which also drops the dependency on the agents list and the agent colours. The "Online" msgid is gone from both catalogues because nothing uses it any more.

The ChatWindow directory had grown to almost fifty files in one level. Tests move to tests, as elsewhere in src, and the components that only make sense together move into list/, tabs/, conversation/ and peek/. The entry point, the state, the hooks and the pieces shared by several groups (CountBadge, PresenceDot, SessionMark) stay at the root, so the import from BottomMenu is unchanged. No behaviour changes with the move; the import blocks were re-sorted by oxfmt where paths changed.

HANDOFF.md carries the context of the session that started this work and is to be deleted before the branch is merged.

  • (chat) Move the chat window onto the teamchat service with groups
    • The window ran on the old presence.* chat calls, which only know integer sessions with an unread count. Groups could not be created or managed, there was no read position, and mutes and notification settings lived in the browser or in the application settings, so they did not follow the user to another computer or to the mobile app.

Switch to the teamchat.* RPCs and the teamchat. websocket topic. Conversations and messages are keyed by UUID, start() returns the conversation list together with the server's features, limits and the user's preferences, and websocket events patch the TanStack Query cache (chat-cache.ts) instead of refetching. Deliveries are batched to one call per conversation a second.

On top of that come group conversations (create, rename, add people with a choice of how much history they see, remove as creator, leave), system notices for those events, @mentions that get through a mute, attachments uploaded over tus, editing within the server's edit window, and delivered and read receipts. Groups, mentions and attachments each appear only when the server reports the feature.

Mutes and the notification preferences (previews, sound, hold during calls, quiet while Offline) are now stored on the server and set from a gear in the chat window, so the messageNotification and holdPreviewsDuringCalls application settings are dropped and the window no longer persists mutes or the recent list in localStorage.

The Storybook theme toolbar now wraps ElementRoot so the dark palette actually applies, and the new ds tokens (attention, icon background, offline status, avatar pin colours) are added for both themes.

  • (chat) Name who read a group message and follow the new teamchat events
    • The teamchat server no longer publishes on a per-user teamchat. topic. Events go out on the fixed topic teamchat and ucs-api delivers only the ones meant for the logged-in user, so the window now subscribes to teamchat and dispatches by payload.type as before.

Every member now sees the sender's client_msg_id, so a pending send is taken as confirmed only by a message we sent ourselves; a colleague's message carrying the same id no longer hides it. Our own messages sent from another window or the phone still arrive as ordinary new messages.

A message in the conversation that is open in the expanded window no longer pops a preview while the browser is unfocused: the preview would only cover the message it announces. The sound still plays, since with the browser in the background nothing else tells the agent it arrived, and the conversation stays unread until the browser is focused again.

In a group, hovering "Read by 2 of 3" (or "Delivered to ...") lists the people it counts, so the agent can see who is still behind. The receipt keeps the members it counted instead of only their number.

  • (chat) Play MP4 and MOV attachments in the conversation
    • A video sent in the chat was only a download link, so watching a short clip a colleague recorded meant saving it and opening it outside Operator. MP4 and MOV attachments now show as a video player in the message, loading only the metadata until played.

Browser support for MOV is uneven: Firefox does not play it, and the HEVC that iPhones record by default needs hardware decoding in Chrome and Edge. When the player reports an error the attachment falls back to the download link it was before, which also covers an MP4 the browser cannot decode. Other video types stay download links.

🐛 Bug Fixes​

  • (chat) Upload and download attachments under /teamchat
    • ucs-api serves the teamchat attachment endpoints at /teamchat/uploads and /teamchat/attachments/{id}, not under /api/v1.0, so uploads and downloads went to a path that does not exist. Point both at /teamchat and add it to the dev server proxy so they reach UCS during development too.
  • (chat) Drop react-textarea-autosize and title the group name field
    • master removed react-textarea-autosize in f345489e0, but the new chat composer still imported it and only built because the package lingered in node_modules; a clean install would break it. The composer now uses a plain textarea that grows through native field-sizing: content, capped at five lines by a max-height, as the other autosizing inputs already do. It stays a plain textarea rather than lib/ui's Textarea because the composer sets its own border, radius, padding and background, and cx does not merge classes.

The new group form labelled its title field with the bare "Name" message, which Czech renders as "Jméno", a person's name. It now carries a "title of a group" context, translated as "Název".

🚜 Refactor​

  • (chat) Format chat window dates with luxon instead of moment
    • The chat window was one of the remaining moment users while the rest of the app moves to luxon. Message times, day separators and the story fixtures now use luxon DateTime.

The server sends created as a string or a number. messageTime() reads the SQL form (YYYY-MM-DD HH:mm:ss) first, falls back to ISO, and treats a number as epoch milliseconds, which is what moment(created) did. Day labels map moment's LT, dddd and LL onto TIME_SIMPLE, cccc and DATE_FULL, which give the same output in Czech and English since luxon picks up the locale that MomentI18nControl already sets.

  • (chat) Address the review of the chat window

    • Follows the review of MR !760.
  • Search ignores diacritics, so "kristyna" finds Kristýna in the chat list, the group people search and @mentions. The chat has its own normalizeSearch in chat-list-model.ts: the admin one imports the admin navigation, and moving it to lib/ is a change of its own.

  • Presence is no longer a context helper. PresenceDot and the new PresenceLabel take a userId and select that one user's status, so a colleague logging in re-renders their dot instead of every component reading the chat context. Lists that sort by presence read the status map from the store.

  • Users come from the store's memoized selectUsersAsMap instead of a map ChatWindow built and passed through the context next to selectUsers, so there is one path to the user list.

  • useConversationSubline becomes and branches on conversation.kind, so a direct conversation can no longer be described as a group.

  • Errors are kept as the caught value and turned into text when they render (), so a language switch also changes a shown error. The group forms run through useMutation instead of hand-rolled busy/error state.

  • The composer takes onSend and onSaveEdit instead of one onSubmit that either fired and forgot or awaited. The edit is a useMutation in Conversation, next to its cache updates; starting or leaving an edit resets it, so a refused edit's reason does not linger.

  • Alt+C uses @tanstack/react-hotkeys, which matches by physical key (Option+C on a Mac) and rejects AltGr (Ctrl+Alt); it stays live in the message box except on a Mac, where Option+C types "ç".

  • ConversationTab gets onClose; ChatTabRow closes the tab and moves focus to the list tab through a ref instead of getElementById.

  • The chat reloads after a reconnect and after a sequence gap by listening to the connector, not by watching the websocket state flip in an effect, which misses a drop shorter than a render and counts the first connection as a reconnect. Connector gains add/ removeConnectListener, fired on open like the existing seq-fail listeners. A sequence gap used to reload only the Redux state, so the chat missed the lost event.

  • Text in JSX uses , like the rest of src. Message ids are unchanged, so the catalogues need no update.

  • The attachment test compares against attachmentUrl() instead of a raw query string, so it states "served inline" rather than how.

  • (chat) Inline the Alt+C shortcut into the chat window

    • After the move to @tanstack/react-hotkeys, useChatShortcut was a single useHotkey call with one caller, so it is inlined into ChatWindow.

Its tests move into ChatWindow.test.tsx and drive the real window: Alt+C opens the chat list, also from the message box on Windows; AltGr+C (Ctrl+Alt) does nothing; on a Mac Option+C is left to a focused text field and opens the list anywhere else. Forcing ignoreInputs either way fails one of them, so the platform rule stays pinned.

📚 Documentation​

  • Add React component guidelines from the chat review
    • The review of the chat window (MR !760) turned up the same handful of patterns in many files: hooks that hand back formatters, translated text kept in state, {t...} children where the rest of src uses , hand-rolled busy/error state around RPC calls, children dispatching into their parent's state, focus by element id, wide contexts carrying fast-changing values, and re-implementations of what an installed library already does. Writing them down once keeps the next feature from repeating them.

⚙️ Miscellaneous Tasks​

  • (chat) Add a busy group story with many people and messages
    • The existing stories hold at most 28 messages and eight people, which is too little to see how the window behaves in a real contact-centre group: long scroll-back through many pages, day separators over weeks, a sender name on most rows, and a people list long enough to scroll.

Busy Group opens "Contact centre – all shifts", a group of the user and 47 colleagues with 600 messages over the last 25 days. The 40 extra colleagues are generated from Czech name lists and spread over the three user groups, a quarter of them offline.

The playground takes a crowd flag for this, so the fake backend now gets its sessions and users as arguments and the store gets the users and their statuses, instead of both reading the module constants. The other stories pass nothing and keep their data.

The fake backend answers listSessions and provisionChat the way UCS does, so the story cannot show the group's members either; that needs members in listSessions on the server first.

  • Satisfy oxlint in the files this branch touches
    • StoreConfig declared smsChat, crm, email and emailFilter as Map<string, any>, but the type is intersected with ReturnType, which already types those slices; typecheck output is identical without them. Drop the four entries and the TODO that described them.

PeekToast reset its leaving flag from an effect when a new preview arrived. Reset it during render on a new peek key instead, the pattern MessageList already uses, and give the timer callback a name so the rule sees that the state is set from a timer rather than from the effect.

The index key in linkify is correct, since the pieces of a split string are identified by their position, but its suppression used the plugin's old @eslint-react name and sat on the wrong line, so it did nothing. Name the rule react-x/no-array-index-key and put it on the key attribute.

  • Remove HANDOFF

[9.56.2] - 2026-11-15​

🐛 Bug Fixes​

  • (supervisor) Swap the inbound answered and unanswered column labels
    • The SupervisorView widget settings offered the inboundAnswered column as "Incoming unanswered calls" and inboundUnanswered as "Incoming answered calls". The table itself was right -- the store, the row cells and the header icons and tooltips all agree -- so ticking one option added the other column, which looked like a flipped column or icon.

The swap is in the labels only, so saved widget settings keep the columns they show today; their checkboxes now carry the right names.

📚 Documentation​

  • (agents) Restructure the project rules for agents

    • Review of CLAUDE.md as guidance rather than as facts:
  • Say which rules are hard constraints that tooling depends on, so the invitation to disagree does not reopen them, and give one policy for legacy code: rules apply to new and rewritten code, untouched code stays so the diff stays about the task.

  • State the direction of the codebase (lib/ui over Semantic, TanStack Query over Redux/Immutable, TypeScript, named exports) so agents can decide cases no rule covers. Visual design stays with the design-decisions skill, which leaves that choice to the user.

  • Move the Semantic rem arithmetic to the design-decisions skill and the density styles behind a pointer to display-density; both were loaded into every session for styling work only.

  • Point at the new operator/* lint rules, add the ternary rule they enforce, and drop counts and file examples that had gone stale or broke other rules.

  • Say the comments rule once instead of three times.

⚙️ Miscellaneous Tasks​

  • (oxlint) Enforce project conventions with a local plugin

    • The mechanical conventions in CLAUDE.md only reached agents, and only when they remembered them; review keeps finding them broken. A local oxlint plugin checks them for everyone:
  • tailwind-prefix-first (error): hover:tw:x compiles to nothing. One existing hit, lg:tw:px-4 in widgets/Email/EmailTab.js, left as is since fixing it changes the layout.

  • trans-for-jsx-text (error): t as JSX children instead of . No existing hits.

  • tailwind-palette-colours (warn): Tailwind's fixed colour scale ignores the dark theme. 130 existing hits.

  • jsx-ternary-not-and (warn): cond && <X /> instead of a ternary. 236 existing hits.

Rules with legacy hits are warnings so lint:changed flags new code without pushing anyone to convert lines outside their task.

[9.56.1] - 2026-11-13​

🐛 Bug Fixes​

  • (email) Save the reply before using a template, sending or putting back
    • A customer whose queue applies a signature template to every new e-mail reported that a second, whole-body template sometimes arrived as its attachments only, with the old text, and worked when retried.

Clicking a template set the editor's active flag to false before the confirm modal opened. When the 3 s autosave fired while the modal was still open, handleSave marked the edited text as saved, so getDerivedStateFromProps saw the older server body as new and put it back into the editor. react-froala follows an external model change with undo.reset() and undo.saveStep(); reset keeps Froala's last-known HTML, so saveStep fires contentChanged and onModelChange armed a new autosave with the old text and set active again. On confirm the server swapped in the template's attachments and body, the editor ignored the email.body event, and the autosave wrote the old text over the template. Confirming within 3 s of opening the menu worked, hence "wrong once, fine right after".

Nothing ordered body saves against the actions that depend on them, so every body save and every such action now goes through one promise queue in EmailTab, and the server sees them in the agent's order:

  • using a template (body or inline) saves the reply first, then calls template.use; a body template then loads the new body with email.body.get and the editor takes exactly that, since responses and events on the socket are not strictly ordered (Connector parses Blob frames asynchronously)
  • send saves first, then calls email.send; send no longer sets the body
  • put back saves first; a second click on put back or send is ignored while they wait, and neither navigates if the tab is already gone
  • delete waits for queued saves and templates

The active flag is dropped only once a body template has loaded or a send went through, never on the click. While body templates are in flight (counted), edits do not schedule an autosave; if the template fails, they get one. A save is skipped when the text equals the last successful save; that marker is cleared when a template or send changes the server body. If a save fails, the follow-up action does not run and the tab keeps saving on close; a save of a reply deleted on the server counts as done so the follow-up reports its own error. Errors thrown inside the queue are logged, and a failed body reload now shows a notification.

Froala saves an undo step on blur, which fires contentChanged, so the reply state holds the agent's last keystrokes when they click a button.

📚 Documentation​

  • (agents) Add rules on disagreement, mutations and translations
    • Agents should weigh instructions, including CLAUDE.md, on their merits and say so when they disagree, rather than follow them blindly.

Review keeps turning up hand-rolled busy/error useState pairs around try/catch for user-triggered requests. useMutation already gives isPending, error and reset, and keeps the caught error itself rather than text.

Storing translated strings in state is wrong twice over: text is view, and it keeps the old language after the user switches. State should hold the error or a code with its data; msg descriptors are a last resort. JSX children use rather than t from useLingui, so a sentence with markup stays one message translators can reorder.

⚙️ Miscellaneous Tasks​

  • Add worktree-setup recipe for dev server prerequisites
    • A fresh git worktree lacks the untracked files the dev server needs: ucs.crt, ucs.key, .env.local and assets/config.local.js. Copying them by hand from the main checkout is easy to get wrong, so just worktree-setup <path> copies whichever exist here and skips any the worktree already has, never overwriting local changes.

[9.56.0] - 2026-11-12​

🚀 Features​

  • (call-recording) Pause and resume call recording
    • Agents pause recording while a customer dictates sensitive data. The square shown on recorded calls is active when the role allows pausing; clicking it calls call.record.pause and the square turns into a pause symbol, clicking that calls call.record.resume. Without the role permission the square is dimmed and inactive.

The dial-bar icon runs start, pause and resume through one TanStack mutation that only switches the RPC method, so whichever request is in flight, the icon stays inactive until it settles and a double click cannot send a second request. A failure shows a toast (lib/ui/toast) naming the action, with the UCS error as its description. Every state has a title, and a dimmed icon says why: no on-demand recording storage, or no pause permission.

  • (call-recording) Pulse the paused recording icon
    • A pause the agent forgets leaves the rest of the call unrecorded, and agents talking to a customer rarely look at the dial bar, so the amber pause icon pulses until the recording resumes. It uses motion-safe, so users who ask for reduced motion get the static amber icon.

Semantic forces the disabled icon's opacity with !important, which wins over the animation, so the icon stays still when the role cannot resume.

  • (operator-api) Notify integrations when call recording pauses
    • Integrations could read recording_paused on exported calls but were never told it changed: OperatorApi only diffed call state and mute, so an integration that called pauseRecording() had to poll state() to see it take effect, and could not notice the automatic resume after the role's timeout at all.

The same diff now compares recording_paused and fires onCallRecordingPause(call) / onCallRecordingResume(call), mirroring onCallMute / onCallUnmute. They fire for every change, whoever caused it. The names keep the onCall prefix of the other call callbacks and stay clear of onCallResume, which is about hold. The iframe bridge forwards both; the SDK passes events through by name, so it needs no change.

[9.55.0] - 2026-11-10​

🚀 Features​

  • (email) Give the email filter's automatic reply a real editor
    • The reply body of an "Automatically reply" filter action was an inline-toolbar Froala with no height, squeezed into the narrow value column of the action row, so writing a reply felt like typing into a one-line input.

The reply action now takes its own full-width row under the action selector, with a framed editor that has a fixed toolbar and grows from 200 to 400 px before it scrolls. Froala's sticky toolbar is off, as in the email editor, because its position: fixed escapes the Semantic Modal around the rule editor. The editor's colours now come from the palette instead of a fixed white.

Also replaces Object() with {} in RuleEditor's initial state to satisfy oxlint's no-object-constructor now that the file is touched.

  • (email) Give the auto-reply editor the email editor's formatting tools
    • The email filter's automatic reply is an e-mail like any other, but its editor lacked font family, highlight (background colour), clear formatting and unify formatting, grouped its buttons differently, and missed the paragraph-spacing fix for pasted HTML.

The formatting toolbar groups, the plugin list and the unifyFormatting command move from FroalaEmailEditor into froala-formatting.ts, which both editors use. Registering the command there also means it exists when the filter is opened without the e-mail widget having been loaded. The auto-reply editor gets the same paste.beforeCleanup handling behind the same feature flag.

Image insert stays e-mail only: it uploads to /email/, and a filter rule has no e-mail to attach the image to.

  • (ui) Let ConfirmDialog disable only its confirm button
    • pending disables both buttons, which is right while the confirmed action runs but wrong while the dialog is still learning what the action would affect: the admin must be able to cancel. confirmDisabled holds back only the confirm button. Optional and off by default, so existing callers are unchanged.
  • (ui) Add a textarea field to the form kit
    • TextareaField binds the shadcn Textarea to a TanStack form field like TextField does, with the label tied to it by id (a plain textarea is not a Base UI field control). It is registered in useAppForm. The admin notifier form uses it for lists entered one value per line and for message bodies; monospace suits numbers, URLs and templates.
  • (admin) Port event notifiers
    • System > Event notifiers moves to /admin/system/notifiers: a list in evaluation order (type, then position) with type, action and state filters, a target column and bulk enable / disable / delete; a page per notifier with the condition fields of its type, the fields of its action, a placeholder reference and a "Refers to" panel; an add page that takes the type from the list filter, and Duplicate.

The form fixes what PHP saved wrongly instead of porting it: empty lists go as [] rather than [null] (which broke event names, arguments and recipients), "all" selects as null, an HTTP rule's sign-in is either OAuth or Basic (PHP sent sso_id 0 with a password, which UCS refuses to load), passwords use a password field, and keys the form does not show are kept on save. Edit sends the stored type with the whole condition and data, as the server requires.

UCS bugs found while porting are not worked around but shown: queue notifiers never fire and presence notifiers with states never match, so those rules get a "will not run" warning, as do HTTP rules with both sign-ins, JSON-RPC / XML-RPC over https, SMS for events without a campaign, and rules without a URL or event names. They are deferred server work K-M. A queue, user, campaign, SMS queue or provider that was deleted shows as "Deleted (#id)", where PHP picked the first option and saving broadened the rule.

  • (admin) Add shared pieces for sub-lists and number rewrites

    • Trunks have six sub-lists edited in dialogs, three of them ordered, and the same dial-plan number rewrite in three places; outgoing filters will need all of it again. So these land as shared pieces rather than copies:
  • FormDialog: a dialog around a TanStack form (title, fields, error, Cancel, submit)

  • SubListHeader: the description and add button above a sub-list

  • OrderButtons + useMoveRecord: move a row up or down by editing its pos alone, which the server keeps contiguous

  • NumberTransformation: prefix / skip / keep / suffix with a live example, following the server's documented transform rules (a negative skip counts from the end, keep 0 plus a suffix dials a fixed number)

  • idOptions moves from notifiers to api/ now that trunks use it too

  • usage kinds can block a delete (onDelete: 'blocks'): the confirm says why and the caller holds back the button

  • (admin) Port trunks

    • Telephony > Trunks moves to /admin/telephony/trunks: a list with name, group, type and state filters, a "Used by" column and bulk activate / deactivate / change group / delete; a trunk page with tabs for its settings (next to what uses it), incoming rules, caller normalization, registrations and tariffs; and a page per incoming rule with its blacklists and caller name lookups (ordered) and its deprecated incoming periods. The PHP dialog-in-dialog editing becomes pages and dialogs.

Server behaviour the forms work around rather than port:

  • the trunk delete is not transactional: it removes incoming rules and outgoing filter destinations, then fails while phone lines use the trunk. The page blocks that delete (the list skips such trunks) and names what goes with the trunk.
  • a SIP edit refuses an empty host, so a trunk that registers to UCS leaves the key out; ISDN sends its channels on every edit
  • passwords come back in clear; the forms never show them and an empty field keeps the stored one
  • sub-records are added without a position (an explicit one shifts the whole list) and moved by editing the position alone
  • incoming periods no longer wipe the rule's variables, and keepalive can be turned off again (PHP made an empty field 60)
  • tariffs require all four numbers (a missing price can break the routing tree)

IAX is shown for existing trunks but not offered, as UCS no longer configures it. The remaining server issues are deferred server work N and O.

Also makes the shared Czech "nothing uses it" / "checking what uses it" strings gender-neutral, as they now cover trunks as well as periods.

  • (admin) Port devices
    • Telephony > Devices moves to /admin/telephony/devices: a list with name/MAC search, group, model and MAC filters, line and user columns and bulk change group / delete; a device page with a Keys tab and a Settings tab next to what uses it; and an add page that opens the new device.

The Keys tab lists every key of the phone and its expansion modules (line keys, BLF keys, module keys), filled or empty. An empty key asks which kind of line to add; each kind has its own fields in one dialog, and moving a line is choosing another key. The extension line picks its extension with a server-side search (config.extensions.find) instead of PHP's autocomplete. The tab warns when SIP lines outnumber the model's accounts, and shows lines whose settings are gone (their mobility user was deleted) as broken.

Not ported from PHP:

  • its extension line form always sent user_id: null, which signed the line's user-mobility user out on every save; the field is never sent
  • passwords (SIP, 802.1X) were shown in clear; they are write-only, and a new line's password is left to the server to generate
  • hidden 802.1X fields are still cleared on a method change, but the password is kept unless retyped

Settings group the device fields into device, expansion modules, network, VLAN, 802.1X and features; VLAN hints show the system values to superusers. Every save says the phone reloads, since UCS re-provisions it each time. Server issues found are deferred server work P.

  • (monaco) Add reusable Monaco editor integration
    • lib/monaco/MonacoEditor wraps @monaco-editor/react for the editors the admin needs (JSON values, Python plugins). monaco-editor-webpack-plugin bundles the json and python languages and their workers, and the dev Content-Security-Policy allows worker-src 'self' for them. The editor is loaded lazily, so it stays out of the main chunk.

It is a named export and follows the app root's dark / default class, switching between "vs-dark" and "vs" when it changes (useSyncExternalStore over a MutationObserver, no store access); a theme prop still wins.

  • (admin) Migrate plugin editor
    • Ports the PHP plugin administration to System › Plugins: a list, add and edit pages, and the Python source edited in the Monaco editor.

The form checks that the code defines the entry class and says so under the Entry field and as a warning marker in the editor, in one translated wording. The marker is also set when Monaco mounts, since it loads lazily and usually after the first check has run.

  • (admin) Add the NATS key-value storage editor

    • System > Key-value storage (/admin/system/buckets) shows the NATS key-value buckets UCS services keep shared settings and state in, and edits their JSON values in Monaco. It turns the prototype from the json-editor worktree, which ran on sample data in memory, into a page on the server's nats.* API (server commit d327615):
  • buckets list (records, size, history, TTL) with search

  • keys of a bucket, 1000 per page (the server's maximum), search within the page, delete and bulk delete, add key at /~new (~ is not allowed in NATS keys, so it cannot clash)

  • value page: JSON editor with the save bar, unsaved-changes guard and Mod+S; delete

The API is optimistic about concurrency: set and del take the revision get returned and refuse a key changed meanwhile (-3). The page keeps the revision, offers to load the current value when a save is refused, and listens to nats.bucket.update to warn while someone else's save makes the open value stale. A taken key on add (-6) lands on the key field and a value that is not JSON (-10) is explained instead of shown. Keys are checked against NATS's characters before sending.

Breadcrumb handles now get the route params too (from the prototype), so the crumbs read bucket and key names. Calls go through the admin rpc wrapper rather than api.call: same POST /JSON/, with response parsing and error codes, and no edit to the operator's shared method map.

The dev upstream did not have the nats.* API (and was down) when this was written, so it is verified with a faked store in the browser and unit tests; the e2e test fakes the answers too. Also fills the Czech strings of the plugin editor.

  • (email) Add a fix typography tool to the editor
    • Agents paste and type text with repeated spaces, stray line breaks and misplaced spaces around punctuation, and fixing them by hand is tedious. A new toolbar button next to Unify formatting fixes them in one undoable step, on the whole e-mail or on the selected paragraphs.

It collapses repeated spaces (also across tags), trims lines, removes the space before , . ; : ! ? at the end of a word, adds one after , ; ! ? before a letter, removes spaces just inside brackets, turns ... into an ellipsis, collapses three or more line breaks to two and repeated empty paragraphs to one.

The rules are limited to what is safe in any language. No space is ever added after a full stop or colon, which would break abbreviations (a.s., s.r.o.), domains and times; a space before punctuation is only removed when the mark ends a word, so smileys and .NET survive. Link text, code, URLs, e-mail addresses and template placeholders are locked, and quoted e-mails and pre are skipped. Leading line breaks stay, since the reply editor keeps them above the quote for the agent's text. Czech non-breaking spaces, quotes and dashes are left for later.

Text is processed per line, with an object marker for images so spaces around them do not collapse, and every change is mapped back to the text node it came from, so inline formatting stays where it was.

  • (email) Show the current paragraph format in the editor toolbar
    • To see whether the text under the cursor is a heading or normal text, the agent had to open the paragraph format dropdown. Froala's paragraphFormatSelection option shows the current block's format ("Normal", "Heading 2") on the button itself and follows the cursor; the dropdown still opens on click.

The option lives in a shared FORMATTING_OPTIONS next to the shared toolbar buttons, so the e-mail, template and auto-reply editors stay in step. The button becomes an 80px text button instead of an icon.

🐛 Bug Fixes​

  • (admin) Preselect the group when adding a holiday class

    • The add dialog started with no group, so the admin had to pick one even when there is only the root group, unlike time periods and limit groups. It now waits for the group list and starts in the first group, the same way the add pages do.
  • (admin) Address the wave A UX critique

    • The impeccable critique of time periods, parallel call limits and private numbers (28/40, snapshot in .impeccable/critique/) found four P1 issues:
  • Delete confirms said "Nothing uses it" while the usage counts were still loading or had failed, and the bulk confirms dropped their warning and typed count in the same case. Usage now has a state (loading, known, hidden, failed): confirms say "Checking what uses it..." with the confirm button held back, a failed load says so, and bulk deletes ask for the typed count unless usage is known. Applies to periods, limits and holiday classes. "Nothing uses it." no longer runs into the previous sentence.

  • A new time period started with every day closed but showed 8:00/16:00 placeholders, so it looked open and saved as a period that never matches. It now starts open Monday to Friday 8:00-16:00, closed days say "Closed", and the form warns when no day is open. Not refused: an all-closed period can be a deliberate manual switch.

  • Private numbers split on spaces, so "+420 777 123 456" became four numbers. Only line breaks, commas and semicolons separate now, and spaces inside a number are dropped; search ignores them too.

  • Numbers that failed to add went back into the one-line box joined by line breaks, which the input strips, gluing them into one wrong number. They are joined with ", " now.

The run and the fixes are recorded in each section's checklist, and the P2/P3 findings in the UX backlog.

  • (admin) Keep the admin scroll inside the admin area
    • Long admin forms (an event notifier, a trunk, device settings, a user) could be scrolled past their end into about 400px of empty space above the operator's bottom menu. Base UI selects and switches render a hidden 1px input with position: absolute to carry the form value; its containing block was an ancestor outside the admin's scrolling
      , so inputs low in a long form were placed below the operator content wrapper and gave it a second scroll.
      is now position: relative, so they stay inside the area that scrolls.
  • (email) Make unify formatting reset everything but the structure
    • Unify formatting only removed font family and size, so colours, spacing and other pasted styling survived. An Outlook paste typically sets the paragraph colour to white and every span back to black, so nothing looked unified after the button was pressed.

The command now keeps an allowlist instead of removing a blocklist: the structural tags (headings, lists, links, tables, images, b/strong, i/em, u, s, sub, sup) stay and fall back to the editor's default look, along with text alignment, inline highlight, table cell background, table and image sizes and Froala's own fr-* classes. Every other style, class, font tag and Office namespace element (o:p) is removed, and spans left without attributes are unwrapped.

Paragraph indents are structure the agent creates with the toolbar's Indent button, which sets margin-left on the block in steps of Froala's indentMargin (20px). A non-zero margin-left or margin-right on paragraphs, divs, headings and pre is kept, converted to px and rounded to the 20px step, so a pasted 35.7pt indent becomes two Indent levels and Indent/Outdent keep working on it. List items lose their margins; list levels are nested lists, not margins.

Before stripping, emphasis that exists only as a style (font-weight, font-style, text-decoration from Word, Outlook or Google Docs) is turned into tags so it survives, and bold or italic markup whose only content is styled back to normal is unwrapped, so text that looked plain stays plain. Headings lose their custom size too and take the editor's heading style.

The same e-mail copied from Gmail instead of Apple Mail brought two more leftovers: empty pairs where Word had <o:p>, and emoji turned into images hot-linked from fonts.gstatic.com. Empty inline tags are removed, and an image carrying data-emoji is replaced by the emoji itself.

The logic moves into a pure unifyFormatting function with tests built from real Outlook and Gmail pastes.

  • (email) Keep red text as one standard red when unifying formatting
    • Senders colour warnings red ("come fasting", deadlines), and unify formatting dropped that along with every other colour. Red now survives, but every shade of it -- #FF0000, #C00000, crimson, a -- becomes #D14841, the red from Froala's text colour palette, so the agent can apply the same red from the toolbar. Its contrast on white is about 5.9:1.

A colour counts as red by hue (within 20 degrees of red), saturation (at least 0.5) and lightness (0.25 to 0.65), which takes in dark and bright reds but leaves out orange, brown and pink.

Colour is inherited, and pasted mail often colours a paragraph red and its spans back to black, so the red cannot stay on the element that declared it. The effective colour of each text run is computed before anything is stripped; afterwards the red goes on the widest element whose text is all red, or on a span around a single run. A link does not inherit the red of its paragraph, matching how it renders.

  • (email) Keep spaces inside inline elements when pasting
    • With preservePasteParagraphSpacing on, the paste pre-processing removed every whitespace-only text node at any depth, meaning to drop the source formatting between paragraphs (

      \n

      ). It also removed real word spaces that are the only content of an inline element. Apple Mail writes the space before a bold word as , so "prosím odepište" pasted as "prosímodepište", and a plain space between and went the same way.

Only whitespace that separates paragraphs is removed now: a text node whose neighbours are paragraphs or the edge of the container. It is decided before the loop, because the loop unwraps paragraphs and changes the siblings as it goes.

  • (email) Drop invisible text colours from pasted html
    • Copying from Apple Mail in dark mode writes the on-screen colour into the clipboard html, so every element the sender did not colour carries color: rgb(255, 255, 255). Pasted with Keep, text without its own colour came out white on the editor's white -- a list item stayed invisible until selected.

After Froala's paste cleanup, each piece of text is checked against the background it actually sits on: the nearest one set in the pasted html, or the editor's white. A colour with less than 1.5:1 contrast there is removed. When a colour is invisible for some of its text and visible for the rest, it moves onto the inner backgrounds where it is visible, or the hidden text under an inner background gets black or white, whichever reads better. White text on a dark table cell keeps its colour, and colours the sender chose (black, grey fine print) are untouched. It runs in paste.afterCleanup, so it covers Keep, Clean and plain paste in the e-mail, template and auto-reply editors.

The colour parsing moves out of unify-formatting into a shared colors.ts, which knows every CSS colour name and adds the WCAG contrast ratio and readableTextOn.

  • (email) Keep hidden content, readable colours and valid markup when unifying
    • Three problems in Unify formatting:

It removed the whole style attribute, display:none included, so content the sender hid -- a newsletter's preheader, tracking text -- became visible and would be sent in the reply. display:none is now kept.

It kept the background of highlighted text and table cells but dropped every text colour, so white on a dark cell turned black on dark. Text on a kept background with too little contrast for the default black (below 3:1) keeps its own colour if that is readable there, otherwise gets white or black, whichever reads better. The colour never moves above the element carrying the background, so text typed next to it later is not white.

Turning style-only emphasis into tags wrapped every child, block children included, giving

…

and lists inside . Only runs of inline content are wrapped now; block children get the style passed down and wrap their own content.

The red colouring is generalised into this colour painting, which also drops its repeated subtree walks: one bottom-up pass records which colour, if any, a whole subtree shares.

🚜 Refactor​

  • (admin) Split relation queries per entity

    • api/relations.ts held every structure.select query and had reached 296 lines after five entities; at one or two functions per ported section it would pass two thousand. It becomes api/relations/ with the SQL helpers (sqlInt, sqlInts, sqlNumber, selectRows, uniqueBy, shared joins) in sql.ts and one file per entity. The rule that only these helpers build SQL now covers the directory instead of one file. No query changes.
  • (admin) Extract the shared list, detail and form pieces

    • The checkpoint review after six sections found the same code copied into every list, detail page and form. With about fifty sections to go, each copy would be made fifty more times, so the pieces move into src/admin and the six sections use them:
  • lists: ListSearch, AddLink, AdminLoading, BulkActionBarSeparator, BulkGroupDialog; useListSelection (prune to shown rows, deselect after a bulk run); TYPED_DELETE_THRESHOLD in api/bulk.ts

  • groups: api/groups.ts with useGroups and useGroupFilter; groupWithSubgroups moves there from the users section, which limits, periods and holidays imported it from

  • deletes: useDeleteRecord holds the record waiting for confirmation, the mutation and its toasts, and returns the ConfirmDialog props

  • forms: saveWithFieldErrors (api/save-form.ts) for onSubmitAsync, FormSection for the field cards

  • detail pages: DetailColumns for the record next to its "Used by" panel

  • usage counts: a UsageDescription per entity (each kind's labels and whether a delete removes or only clears it) rendered by UsageSummary and DeleteConsequences, replacing the per-entity summary and consequence components of periods and limits

The add pages of periods and limits now wait for the group list and pass the first group into the empty form, instead of setting it from an effect after the form rendered. The admin sees the same form; the effect and its dontUpdateMeta workaround are gone.

Two small differences: a failed delete from a detail page keeps the confirm open (the lists already did), and the admin e2e spec is renamed admin.spec.ts since it covers every section.

The skill references list the new pieces, and list-views.md's checklist asks for them.

  • (email) Share block tags and unwrap between the editor tools
    • Unify formatting, Fix typography and the paste spacing code each kept their own unwrap helper and list of block tags, and the two lists already differed (Unify's lacked blockquote, table cells and hr). They now come from html-nodes.ts, so the tools agree on what a block is. For Unify the longer list changes nothing: table cells keep their background as before, and quotes are skipped before the list is consulted.

📚 Documentation​

  • (admin) Restore the parity checklists and point to current reference sections
    • The commit that hid relation data from admins who are not superusers rewrote progress.md and cut it off after the deferred server work, losing the parity checklists of holidays, periods, parallel call limits and users. They are restored from its parent, with the private numbers checklist that was written but never saved.

The skill named holidays as the section to copy, but it is the dialog-based exception; limits is the common list -> detail shape, so the skill now lists one reference per kind of section and says to use the shared pieces instead of copying them. Also merges the duplicated queries bullet, puts the foundations sentence back under building blocks, notes that files.ts only downloads, names the admin e2e file, and asks for the UX critique run to be recorded in the checklist.

  • (admin) Record the trunks and event notifiers research
    • Port specs for the two sections, read from the PHP admin and the server code: fields and their server rules, sub-lists, server contract, hidden behaviour (non-transactional trunk delete, position insert bug, notifier server bugs) and what references each record. Kept in the repo so the ports do not depend on one session's notes.
  • (admin) Record the devices research
    • Port spec for Telephony > Devices, read from the PHP admin and the server: device and line fields with their server rules, key positions, the five line types, provisioning side effects, the user-mobility trap in PHP's extension line form, and what references a device.

[9.54.0] - 2026-11-05​

🚀 Features​

  • (email) Accept pasted recipients with display names
    • Agents paste recipient lists copied from Outlook and other mail clients, which come as "Fuxová, Alice fuxova@iscare.cz; Vodičková, Václava <...>;". The recipient fields split on commas and semicolons only, so the comma inside a name cut each entry in two and none of the addresses were recognised.

Before splitting, every "name

" group is now reduced to the address inside the angle brackets, keeping any bare addresses typed before it. Both the reply editor's To/Cc/Bcc fields and the send-again field use the shared parser now; the send-again field had its own copy that also missed case-insensitive duplicates.

[9.53.1] - 2026-11-05​

🐛 Bug Fixes​

  • (email) Keep the editor toolbar sticky inside the email scroll container
    • Froala's sticky toolbar uses position: fixed with a 40px offset from the viewport top. The email view scrolls inside a nested overflow container, so the fixed toolbar escaped it and floated over unrelated parts of the page while the reply was scrolled.

Turn Froala's sticky mode off and make the toolbar position: sticky in CSS instead, so it pins to the top of the scroll container and stays within the editor box.

[9.53.0] - 2026-11-03​

🚀 Features​

  • (design) Add new design tokens as palette variables
    • The Insoft UCS tokens from the design-decisions skill (tokens.json) become --ds-* palette variables, light and dark, and Tailwind colours (tw:bg-ds-canvas, tw:text-ds-ink, ...), so components can use the new design without hex values. Nothing existing reads them yet, so the operator's look does not change.

Design decisions: all colours follow the new tokens; --ds-on-primary (text on a primary fill) is not in the token set and is ours: on-dark in light mode, the dark canvas in dark mode.

  • (ui) Add data table, form bindings, toast and confirm dialog

    • Store-free primitives the administration needs and the operator can reuse:
  • DataTable on TanStack Table with click-to-sort headers; text sorts with Intl.Collator, since the built-in sort compares code points and put "č" after "q", unlike the database order users see elsewhere

  • useAppForm on TanStack Form with TextField, SelectField, FormSubmitButton and FormError over the existing lib/ui field, input and select, plus mapping of UCS field errors (lines-0-number) to form fields (lines[0].number)

  • toast (module-level manager, Base UI Toast) and ConfirmDialog (on lib/ui dialog) replacing the Redux-backed modules/messages and modules/confirm

Design decisions: new design tokens (ds- colours) for the table, toasts and form-level error; label typography for table heads.

  • (admin) Hide the operator tabs in the administration

    • The administration lives inside the operator so calls keep working while administering: the top bar with dialing and the bottom menu (chat, settings, version) stay, but the operator tabs would only crowd the administration's own navigation, so they are hidden on /admin/*.
  • (admin) Add the administration area at /admin

    • First step of moving the PHP UCS administration into the operator. /admin gets its own layout inside the operator shell:
  • navigation grouped like the PHP admin menu; sections not migrated yet open the PHP page (/admin/) in a new tab

  • superuser gate; others are told UCS does not yet support users who have the administration among their apps without being superusers

  • AdminTheme remaps the current-design palette variables to the new design tokens inside the area and hosts its portals, so existing lib/ui primitives and Button take the new look there and nowhere else

  • all routes lazy: the previous beta pages (announcement-tts, user, structure, settings, director) keep their URLs but move out of the main chunk; their old layout and empty dashboard are replaced by the new ones

Design decisions: new design tokens throughout (canvas, surface, lines, ink, muted, selected state, label typography); current font stack kept.

  • (admin) Port holidays

    • System › Holidays is the first section moved from the PHP admin, and the reference for the next ones: holiday classes (group, name, update URL) and their days, with add, edit and delete.
  • server access goes through admin/api/rpc.ts, which posts to /JSON/ with the session's client but reads error bodies itself, so nested UCS field errors survive; enums are cached per name for targeted invalidation

  • server validation errors show on their fields; the PHP form's wrong id hid them there

  • dates use a native date input (ISO in, user locale out) instead of the PHP DD.MM.YYYY conversion

  • lists refresh on holidays.* events, so edits made in the PHP admin show up

  • deleting a class says that its days go and time periods lose the class, which the database does by cascade and SET NULL

Checked on the dev instance against the PHP page: same data, actions and order; created, validated, read back and deleted a test class and day.

Design decisions: new design tokens (page header, table, dialogs via the admin theme).

  • (admin) Translate the administration into Czech

    • Czech for every new administration string (menu, gate, holidays, table, form and toast primitives). "Name" of a thing gets its own context, since the existing translation is a person's name ("Jméno") and holidays need "Název".
  • (admin) Make the admin menu searchable, collapsible and grouped by task

    • The menu copied the PHP admin's: about 70 entries in groups named after the PHP pages, with rarely used ones (FAX, DHCP, ...) between the everyday ones.
  • a filter above the menu finds a section by name, ignoring case and diacritics; a group's name lists the whole group. / focuses it from anywhere in the administration (⌘K stays the operator's search), arrow keys pick a result and Enter opens it, also for sections still in the PHP admin

  • groups collapse; only the one with the current page is open by default and what a user opens or closes is remembered per browser

  • groups follow tasks, most used first: number plan, users and access, contact centre, call routing, messaging, status, reports, phones and media, system and network, help. Time periods and holidays move to call routing, dialplans and wizards next to what they create, network items to system; the SMS and FAX status entries become "Outgoing SMS" and "Outgoing FAX" since PHP listed both status and configuration as "SMS queues"

Every item keeps its PHP page, so both admins can still be compared. Czech translations added; the e2e test now covers the filter and the shortcut.

Design decisions: new design tokens for the filter box (line-strong border, mark focus outline) and the keyboard highlight; group headings keep the label typography.

  • (ui) Add a tree component
    • Tree and TreeItem implement an ARIA tree for lists like the UCS number plan: one Tab stop (roving tabindex), up/down/home/end between visible items, right/left to expand, enter or collapse and go to the parent, Enter to select. Children render only while expanded, so a caller can load them lazily; TreeStatus shows a loading, error or empty row meanwhile. Data and state stay with the caller.

Design decisions: new design tokens (hover and selected states, mark focus outline, muted icons); styled with an SCSS module because focus and indent need child selectors.

  • (admin) Add the number plan tree

    • Number plan › Groups and extensions shows the telephone system's groups and extensions as a tree, the one the PHP admin keeps on the left of every page, on a page of its own with a detail pane next to it.
  • groups load their content when opened (structure.childs); partitions and the 15 extension types get their own icons and translated names, which UCS does not provide

  • the selection is in the URL (…/number-plan/extension/5); opening such a link expands the tree down to the item, and that path stays open while the next selection loads instead of collapsing and reopening

  • the detail pane shows the group or extension read-only and links to the PHP group/extension lists and the item's call records, since editing is still in the PHP admin (its tree actions are dialog-only endpoints)

  • the tree reloads on group.* and extension.* events

  • config.groups.get sends partition as a flag while structure.childs sends the partition's id; each is parsed with its own shape

Checked on the dev instance: no folder collapses on selection, deep links open the path, the PHP call records link opens the right page. Czech translations added ("Switch" as an extension type gets its own context: the existing translation means a transfer). Skill notes the tree, the hotkey and retry rules.

Design decisions: new design tokens; detail pane sticky so it stays in view while a long tree scrolls the page.

  • (ui) Jump to tree items by typing
    • Typing while a tree has focus moves to the next visible item whose label starts with the typed text (case and diacritics ignored, a pause starts a new search), the usual tree type-ahead. The keys stay in the tree: digits would otherwise jump to the operator's dial field (numpadFocusesDial); F2 still does that.
  • (admin) Search the number plan and show migrated sections on the home
      • a search box above the number plan tree finds groups by name and extensions by number or name (structure.search, diacritics ignored); results replace the tree while typing, arrows and Enter pick one, and the tree then opens down to it. The tree stays mounted meanwhile, so its open folders survive
  • the admin home lists the sections already migrated, taken from the menu, and the / shortcut, instead of a paragraph of text

Czech translations added.

Design decisions: new design tokens for the search box (like the menu filter) and the section links (surface, line, hover state).

  • (ui) Add a switch field and disabled select options to the form kit
      • SwitchField binds the lib/ui Switch to TanStack Form, its label beside the switch
  • TextField accepts type="password"
  • SelectField items can be disabled, e.g. queues a user is already in
  • inside the admin, switches take the primary colour (--accent-color) and their off track stays visible: it used the tertiary background, which the admin theme maps to the white surface

Design decisions: new design tokens (primary for checked, line-strong for the off track).

  • (admin) Port users, replacing the beta users page

    • System › Users is migrated from the PHP admin; the operator's earlier beta users page (the first try of this rewrite) is folded in and /admin/user redirects here.
  • list: username with inactive/superuser marks, display name, group, role, team; sorting, a filter by username or name, delete

  • a user's page with tabs that have addresses: settings, queues, devices, personal directory, speed dials, vCard (when properties exist), metadata, access. Each tab saves on its own; the sub-lists save each change at once

  • settings send what the PHP admin sends (empty text null, 0 for none in selects, the password only when typed), with a primary phone picker over config.extensions.find; server field errors land on their fields

  • queue memberships convert priority and penalty and map the "does not answer" state with the AUX reason as PHP does; assigned queues, campaigns and devices cannot be picked twice

  • access downloads the certificate (base64 to .pem|.pfx) and sends the mobile application set-up e-mail without ever showing its one-time code

  • after adding, the new user's page opens

  • live on user.* events; users, devices, roles and teams refresh after changes

Not ported PHP bugs: every edit wiped external_id when identity management was off, and reset the user's live presence to the value loaded with the form; both are now only sent when they can and did change.

Checked on the dev instance: add, edit, duplicate username, queue membership, directory, speed dial, device mobility, metadata and delete, verified through config.users.get. Certificate export is broken on the server except PEM without a password (deferred server work F); PEM is the default.

Design decisions: new design tokens; settings grouped in labelled sections instead of PHP's two columns.

  • (ui) Row selection in DataTable with a Base UI checkbox
    • An optional selection prop adds a checkbox column. The header box selects or clears the rows shown, and is indeterminate when only some are; selected rows use the selected-state token. The caller owns the selected ids, so list views can act on several rows at once. Without the prop the table renders as before.

The boxes are lib/ui/checkbox, a port of the shadcn/ui Base UI checkbox. Base UI has an indeterminate prop, so nothing sets the DOM property by hand. It renders role="checkbox" with aria-checked ("mixed" when partial), which is what the tests query.

Design decisions: the checkbox takes its colours from the palette variables like Switch; checked and indeterminate use the accent background with inversed text, unchecked the primary border and background, and indeterminate shows a dash (upstream leaves that to the caller); focus ring in --focus-color; a larger hit area through ::after. Selected rows use ds-state-selected.

  • (admin) Filters and bulk actions on the users list
    • The users list filters by status, group, role and team (with "not set") besides the search, all kept in the URL so going back from a user or sharing a link keeps them. Ticked users can be activated, deactivated, moved to a group, given a role or team, or deleted together; deactivating and deleting ask first. UCS has no bulk methods, so runBulk sends one request per user in sequence and collects failures with the server's field-error text; the toast lists them and failed users stay selected. Only rows the filters show are acted on.

The pieces are reusable for other list views: useListFilters, ListToolbar, ListFilterSelect, BulkActionBar, BulkChoiceDialog and api/bulk (documented in the skill's foundations). The menu e2e test no longer clicks, which the dev overlay could block.

Design decisions: bulk bar on the ds-mark tint and line, sticky above the table.

  • (ui) Danger tone for confirm dialogs
    • ConfirmDialog takes tone="danger", which turns the confirm button red, so Delete no longer looks like Save. DANGER_BUTTON_CLASSES gives the same look to a Button that starts a destructive flow (a bulk Delete). The classes use ! because Button's colours come from an unlayered SCSS module, which beats Tailwind utilities.
  • (admin) Protect unsaved edits and make risky actions explicit
    • Fixes from the first UX critique of the admin area (27/40), where P1 and the cheap P2 issues are taken on.

Protect input:

  • Settings, Metadata and vCard end with a sticky save bar ("Unsaved changes", Discard, Save; Mod+S saves). Leaving a changed form (tab, breadcrumb, menu, Back) asks first via useBlocker, and beforeunload covers closing the tab. Before, a tab click dropped the edits on a five-section form whose Save was off-screen.
  • The list tabs (queues, devices, directory, speed dials) say they save right away.

Destructive actions:

  • Every delete/remove confirm is red.
  • Bulk deactivate and delete name the users, skip the signed-in user up front (the server refuses anyway) and point out superusers.
  • Deleting 20+ users or any superuser asks for the count to be typed.
  • The bulk bar groups changes, status and a red Delete, and says "All N shown selected".

Contact-centre efficiency:

  • Bulk "Add to queue" with the defaults of a single add.
  • The add-to-queue dialog takes several queues at once, with failures per queue reported and left ticked.

Smaller fixes:

  • Campaign and queue names show "…" while loading instead of raw ids.
  • The vCard tab without properties points to vCard properties instead of an empty card holding only Save.
  • The breadcrumb names the user (useAdminCrumb, since routes.tsx must not import section code).
  • The superuser marker is violet, not danger-red, and shows for inactive superusers too.
  • The duplicate edit icon is gone, and the search placeholder is no longer cut off.
  • Page descriptions are capped at 70ch.
  • The home page is a compact list instead of a card grid.
  • The section finder also matches English titles via an English I18n instance, because production descriptors carry no source message.
  • Holiday days list upcoming closures first and dim past ones.

Design decisions: save bar on ds-canvas (ds-surface inside cards) with a ds-line top border; warnings on ds-warn-soft; name chips on ds-tag-bg/fg; dividers in the bulk bar are ds-line-strong.

  • (admin) Filters, bulk actions and overview on the holiday lists
    • Brings both holiday screens to the list-view pattern and makes them answer the question an admin opens them with: are the coming holidays in place?

Class list:

  • Columns for the number of days, the next holiday and the time periods that use each class. The days come from one listDays() call for all classes. The period usage comes from config.periods.get per period, since list has no class_id and ignores a column list over JSON; there are few periods.
  • A class with no upcoming days is marked and can be filtered for: its time periods would treat every coming day as normal, which usually means next year was never added.
  • Filters by name, group (with subgroups) and coverage, kept in the URL.
  • Bulk change group (get, then edit with every field, since edit needs them all) and bulk delete. Delete confirms name the time periods that lose their class, and ask for the typed count when any are affected.

Days list:

  • A summary line ("N coming; the next is …"), which becomes a warning when nothing is ahead.
  • Filters by name and Coming, Past or a year. The breadcrumb names the class.
  • Bulk delete, and "Copy to next year": the same day a year later, with the same name. It warns about movable holidays; duplicates come back as per-row failures, and 29 February is reported, not copied.

The list-views reference gains Holidays as a second example and a section on derived columns and dated lists.

Design decisions: "No upcoming days" as a ds-warn-soft chip; the summary line is muted text, or a ds-warn-soft panel when nothing is ahead.

  • (admin) Show what uses each record on detail screens

    • User requirement: every detail screen shows what uses the record and other useful context, not only what can be edited there. The question admins come with is usually "what happens if I change or delete this?".
  • Holiday class (days page): its time periods, and through them the time routes, trunk incoming rules and outgoing campaigns that switch on those periods. When nothing uses the class, it says its days have no effect on calls.

  • Extension: users with it as their primary phone, and time routes sending calls to its number (period routes and the default/holiday fallbacks).

  • Group: direct counts of users, extensions, trunks, time periods and holiday classes. The users and holiday-class counts link to those lists filtered to the group.

  • User (Settings tab): users taking their settings from this user (provisioning), whose configuration changes with it.

No API method answers "what uses this", so api/relations.ts reads it with structure.select. That is a read-only SQL select for superusers, and the admin is superuser-only, so no server change is needed. Because table and WHERE go into SQL as given, only sqlInt ids and dialable numbers are interpolated, and all schema-coupled queries stay in that file with tests. Deferred server item G asks for real usage methods to replace them.

The class list's "Used by time periods" column now comes from one such query instead of config.periods.get per period. Usage queries share an ['admin', 'usage'] key, refreshed by useUsageEvents on period, extension, campaign, trunk incoming period and user events.

RelatedPanel shows the results: a section per kind of reference, with links to ported pages or the PHP admin, counts linking to filtered lists, and an empty state that says what it means. The skill makes it a standard: ux-patterns.md › Related information (with a table of what each record shows), rpc.md › Reading relations, the parity checklist, SKILL.md.

Design decisions: RelatedPanel is a ds-surface card in an 18rem side column at xl (stacked below), with the small uppercase ds-text-subtle title used by form sections.

  • (admin) Show bulk runs in a progress dialog instead of a toast

    • User request: bulk actions report progress while they run and a clear end, not a toast after the fact. On a long run the old flow showed only a disabled dialog, and its summary toast vanished on its own.
  • runBulk takes onProgress, called after each item, and an AbortSignal that stops before the next item, which ends up in a new skipped list.

  • useBulkRun(onFinish) holds one run: start({ title, items, action }), stop, close.

  • BulkProgressDialog opens as soon as the confirm or choice dialog is accepted. While running it shows "12 of 50 done…", a progress bar, failures with their reasons as they happen, and Stop; it cannot be dismissed. At the end it says "Finished: all N done", "Finished: N done, M failed" or "Stopped: …, K not run", lists every failure, and waits for Close.

  • Users, holiday classes and holiday days use it. Their onFinish keeps the failed rows selected and invalidates as before. Toasts stay for single actions only.

list-views.md, foundations.md and the FEATURE notes describe the new flow.

Design decisions: progress bar on ds-surface-3, filled ds-primary, or ds-warn once something failed; failure list on ds-warn-soft, scrolling past 12rem.

  • (ui) Mount the toaster for the whole operator
    • lib/ui toasts (toast.success(), toast.error(), store-free) rendered only in the administration, because AdminLayout held the only . Anywhere else a call queued a toast that never showed. The Toaster now lives in ElementRoot, so the whole operator can use toasts, with the theme, density and the app-root portal; AdminLayout no longer mounts its own.

Toasts keep the new design (ds-* tokens) everywhere, as decided with the user. The Redux modules/messages notify() stays separate; moving its call sites to toast.* is later work.

This moves Base UI's small toast part and the toast list into the main bundle; the rest of Base UI is already there.

  • (ui) Accept datetime-local in the form kit's TextField

    • The time periods form needs validity date and time inputs. The native datetime-local input returns YYYY-MM-DDTHH:MM with no time zone, which maps straight onto UCS's local-time strings. Additive: the default type is unchanged.
  • (admin) Port time periods

    • System › Time periods moves from the PHP administration to /admin/system/periods, with a list, an add page and a page per period (PHP: one dialog).
  • Hours are a week grid: a switch per day, From/To typed as 8:00 or 8 (24:00 allowed, which a native time input cannot do), a 0–24 bar, and "copy Monday" buttons. A day is open only with both times, matching the dial plan. A From later than To is refused, because UCS reads it inconsistently: the dial plan wraps it within the same day, queue working hours never match it. The form explains how to split hours across midnight.

  • Validity dates go out and come back as UCS-local YYYY-MM-DD HH:MM:SS, never converted through Date. The holiday class says what it does; "Remove when expired" says it has no effect, since no server code acts on it.

  • Each period shows what uses it: time routes, queue working hours, trunk incoming rules, tariffs, campaigns (relations.ts periodUsage, via structure.select). Deleting cascades in the database (time-route rules, trunk incoming rules and tariffs go; campaigns and queues are left without a period), so delete confirms say how many of each. Bulk deletes of periods in use ask for the count to be typed.

  • The list shows hours, validity (expired / not yet), holiday class and use. It filters by name, group (with subgroups), holiday class (incl. not set) and validity, in the URL, and has bulk change group, set holiday class and delete through the progress dialog.

  • The holiday class page now links its time periods to their new pages, and the menu entry points here.

The catalogs are extracted with --clean, which drops obsolete entries left by earlier admin work. Deferred server items H (remove_expired unimplemented) and I (two evaluators disagree on empty days and a later From) are recorded in progress.md, together with the period semantics in hidden-semantics.md.

Design decisions: day bar on ds-surface-3 with ds-line ticks at 6/12/18 and a ds-primary fill; validity chips ds-danger-soft (expired) and ds-info-soft (not yet).

  • (admin) Port parallel call limits

    • Telephony › Parallel call limits moves from the PHP administration to /admin/telephony/limits, with a list, an add page and a page per limit group (PHP: one dialog).
  • Incoming, outgoing and total maximums say that empty means no limit and where they count: trunk incoming rules and outgoing filter destinations that pick the group. The over-limit destinations say what happens when none is set (the caller hears busy).

  • UCS bug, warned about in the form and marked in the list: the dial plan checks the outgoing limit only when an incoming one is set (an outgoing limit alone is not enforced), and an incoming limit without an outgoing one makes dial plan generation fail ("%d" % None) once an outgoing filter uses the group. Recorded as deferred server item J.

  • edit reads name unconditionally, so every edit, bulk ones included, sends the whole struct.

  • Each group shows what uses it (relations.ts limitUsage: trunk incoming rules and outgoing filter destinations with their patterns). Deleting leaves those rules unlimited (SET NULL), which the confirmations say with counts.

  • The list shows "no limit" instead of empty cells and how the group is used. It filters by name, group (with subgroups) and use, and has bulk change group and delete through the progress dialog.

Checked on dev with throwaway groups: add, warnings, invalid count and duplicate name errors, rename with Mod+S, bulk change group (names and limits kept), bulk delete.

Design decisions: "not applied" chip on ds-warn-soft; the warning in the form is a ds-warn-soft note under the three limits.

  • (admin) Hide relation data from admins who are not superusers
    • The "Used by" information comes from structure.select, which is superuser-only and ignores group access. Administrators who are not superusers but have admin access to some groups will be let in later (deferred A). For them the queries would fail, and if they did not, they would show records from groups the admin may not see. Delete confirms would then claim "nothing uses it" before a delete that can cascade.

useCanReadRelations() (use-superuser.ts, also used by AdminGate) now guards every relation query (enabled) and its UI:

  • the "Used by" panels say the information is only for superusers for now;
  • the usage columns (holiday classes, periods, limits) and the limits' use filter are hidden;
  • delete confirms say usage is unknown and to check first (UnknownUsage), never "nothing uses it", and bulk deletes then always ask for the typed count. Superusers see no change.

The skill makes it a rule: build for group-limited admins already (group-scoped config.* methods, honest fallbacks for anything superuser-only). Usage methods that respect group access (deferred G) become a prerequisite for A; the parity checklist gains the group-limited admin.

  • (admin) Port private numbers

    • Telephony > Private numbers moves to /admin/telephony/private-numbers. External calls whose destination exactly matches a private number are marked private by the CDR trigger and priced apart in call billing.
  • Inline add box instead of a dialog. Several numbers can be added at once (split on spaces, commas, lines), checked client-side against the server's 0-9#*+ rule. More than one goes through the bulk progress dialog and the failed ones stay in the box; BulkProgressDialog gets a failedHint prop for that.

  • The list shows users' own numbers (added through user billing) with a link to the user, so deleting one says it is personal.

  • Filters by number or user and by scope in the URL; bulk delete.

The admin API only adds global numbers, the duplicate check spans global and personal ones, and there are no group access checks, so the page works the same for admins who are not superusers.

  • (email) Explain the %ORIGINAL% placeholder in the template editor
    • A whole-body template replaces the reply's text, and the server puts the answered e-mail back only where the template has %ORIGINAL% (Email.useTemplate in the server). Nothing in the editor said so, so templates were written without it and replies went out without the quote.

The editor now explains the placeholder under the template type: a reply quotes the answered e-mail there, a forward inserts the forwarded one, a new e-mail leaves it empty. When the text lacks the placeholder it also warns that a reply will not include the answered e-mail, while a forward still appends the forwarded one after the template.

The note shows for whole-body templates that are usable for e-mail or have no usage set, since the e-mail template menu does not filter by usage. Inserted-text templates are left out: the server does not append anything for them.

  • (email) Check template placeholders in the template editor

    • The %ORIGINAL% note becomes a checklist that also covers the template's variables. The server replaces a variable's key exactly as written, so a variable missing from the text silently drops what the agent fills in, and a %PLACEHOLDER% that nothing fills goes out in the e-mail as written. The editor now lists, under the template type:
  • whether the text has %ORIGINAL% (whole-body templates usable for e-mail)

  • that every variable appears in the text, or each one that does not

  • placeholders that are neither variables nor built in (e-mail templates only, since task templates are also filled from the task's own data)

It also says that %FIRSTNAME% and %LASTNAME% are replaced with the name of the agent using the template, which template.use() does for every template.

Tags are stripped before looking for placeholders, because URL-encoded links in attributes contain look-alikes such as %E2%.

Design follows the new Insoft UCS tokens: ok, warn and text-subtle, added to palettes.scss as --status-ok-text-color and --status-warning-text-color (OKLCH on the existing --status-*-hue) and --subtle-text-color, light and dark; body size 14px (1rem) at line-height 1.5.

🐛 Bug Fixes​

  • (admin) Put admin dialogs above the operator's top and bottom menus
    • Admin dialogs (holiday edit, confirms, bulk dialogs) left the operator's top and bottom menus undimmed and clickable. AdminTheme handed its own box to RootElementContext, so every lib/ui portal mounted inside the admin's content column. Even after moving the portals to the app root, the menus stayed on top: they are Semantic .ui.menu flex items at z-index 1000, the same as the dialog overlay, and came later in the DOM than the portal host.

The popups now mount into .adminPortal, a host that AdminTheme creates in the app root:

  • it carries the admin tokens, so dialogs, selects and toasts keep the new design;
  • it is a fixed layer at z-index 1001, so DOM order no longer decides;
  • it sets pointer-events: none, and its children set it back, so the empty layer lets clicks through.

Checked on dev: with a dialog open, the overlay is topmost over both menus; page links, select options, dialog buttons and the bottom menu still take real mouse clicks.

  • (email) Make the template variable inputs wide enough to type in
    • The Variables column was sized with flex: 0 and width: fit-content, which suited the old redux-form inputs that carried their own width. The final-form inputs are fluid, so the column shrank to their minimum and an input showed not even one character. The column now takes a fixed 24rem.

The inputs also said "Metadata key" and "Column name", wording from the report form that shares the Metadata component. Metadata takes the placeholders as optional props, keeping those as defaults, and the template editor passes "Variable, e.g. %ORDER%" and "Label for the agent".

  • (email) Keep emptied template variable inputs from breaking the template
    • final-form sets a field to undefined once its input is emptied. The template checklist called trim() on it and crashed, and autosave sent the variable without a name, so the server stored it that way and emailTemplateParser rejected the template on the next load ("expected string, received undefined" at data.N.variable).

toTemplateVariables now sends an emptied input as an empty string, the form type says the fields can be missing, and the parser reads a variable stored without a name as an empty one, so templates already saved that way open again.

  • (email) Keep printed e-mails readable and within the page width
    • Printing wrote the e-mail body into the print window as the sender styled it. Fine print such as signatures and legal footers came out at 8-10 px, and preformatted text or nowrap cells ran off the right edge of the paper, which cannot scroll.

Before printing, every element of the print window whose computed font size is below 14 px (10.5 pt, ordinary body text on paper) is raised to 14 px, and white-space pre and nowrap become pre-wrap and normal, so line breaks and indentation survive while lines wrap at the page edge. Both are set inline with !important to win over the sender's own !important rules. Working from computed styles catches every source:

, , , , em sizes and stylesheet rules alike. The on-screen view is unchanged.

The minimum also applies to the print header, whose own rows are styled at 12 px.

  • (email) Shrink inline images to the width of the e-mail body
    • An inline image wider than the body area made the preview scroll sideways and showed a high-resolution image zoomed in; in print it ran off the page.

The viewed body now carries a stylesheet capping images at the available width with their aspect ratio kept. It has to be CSS, since the preview iframe runs no scripts. The cap is the stretch size rather than 100%, so an image with margins of its own (set by the sender) fits together with them instead of overflowing by their width; max-content and fit-content would not cap at all, as an image's content size is its natural width. Firefox only knows the -moz-available spelling and older WebKit -webkit-fill-available, and 100% stays first for engines that know none of them.

The stylesheet goes into the body because a fragment is serialized from the body only. The rules are !important so the sender's own sizing cannot undo them; height: auto does flatten deliberately stretched spacer images.

  • (email) Wrap elements that usually don't wrap for print
  • (email) Also scale line-height when enlarging font for print and skip font size smaller than 1px as they are usually just layout tricks

🚜 Refactor​

  • (email) Show the template checklist under the text editor
    • The checklist is about the template's text, so it now follows the editor instead of sitting between the form fields. TemplateEditor keeps the current form values in state to render it, and TemplateEditorForm is back to its original shape.
  • (email) Move template delete and save into the save-status bar
    • The Delete/Save column took a third of the form row and left the Variables column too narrow for its inputs. The editor autosaves, so Save is a "save now" next to the save status, and Delete sits there too, away from the fields edited all the time; it still asks for confirmation.

Save stays a submit button of the template form through the form attribute, so a manual save still reports field errors such as a duplicate name on the form. The form row is now two equal columns, fields and variables, and the fixed width of the Variables column is gone.

📚 Documentation​

  • (admin) Record foundations and holidays port in the skill
    • Foundations now lists the real APIs (admin shell, theme remap, ds tokens, rpc, enums, DataTable, form bindings, toast, confirm) instead of plans. The skill points to Holidays as the reference section and records what building it taught: describeStruct texts are English only so forms carry their own help text, a Lingui context for "Name", fresh-worktree setup, the dev URL without a slash before '#', and how to compare with the PHP admin through the dev proxy. Holidays is in parity check with its checklist, waiting for sign-off.
  • (admin) UX rules and list-view guide for the admin port
    • references/list-views.md covers filtering, selection and bulk actions on admin lists, with a checklist for new lists. references/ux-patterns.md has the UX rules from the critique: protecting input, destructive actions, loading and empty states, orientation, colour, keyboard, and running the impeccable critique per section.

SKILL.md points to both and adds a UX review step before the parity check. foundations.md lists the new building blocks. progress.md records the UX changes and a UX backlog of the critique items that are still open (number-plan routing summary, call-path trace, holiday usage, undo toasts, copying memberships, collapsible menu, review-then-apply, palette question).

Also adds the critique snapshot under .impeccable/critique/.

⚡ Performance​

  • (email) Invalidate the e-mail lists once per websocket event
    • Each mounted e-mail list widget invalidated the shared emailList cache on every email.insert, email.update and email.delivered. invalidateQueries does not coalesce calls made in the same tick: with the default cancelRefetch, each call cancels the fetch the previous one started and starts its own, and as api.call cannot be aborted, every one of those requests still reaches the server. Two widgets on screen therefore sent every refetch twice.

The invalidation now runs in querySync, which StoreProvider calls exactly once per websocket message. The widget hook only keeps the three topics subscribed, ref-counted, while a list is mounted. StoreProvider is rendered by the router inside QueryProvider, so it can reach the query client.

  • (email) Refetch only the e-mail lists an event can change
    • Every email.insert, email.update and email.delivered invalidated every cached e-mail list, so one event refetched the seven quick-filter counts and the visible page. Replying to an e-mail sends three events (the reply's insert, the original's update and a second update of the reply), so a reply cost three such rounds.

The events carry the whole e-mail: insert and update as { old, new } and delivered as the bare record. Only the lists whose API filter the e-mail could have matched before or can match after are now invalidated, across all their pages, since a change shifts every page and the total.

The check only rules a list out on fields whose filter semantics are plain equality or membership: queue, direction, agent, language, the state list and the tag. Address, subject and date filters are always treated as a possible match, as the server's substring and timezone rules are not known here. The old side of an update can come without some fields (tags and attachments are missing when an e-mail is served), and a missing field counts as a possible match. A payload that does not parse falls back to invalidating everything.

An update that changes none of the filtered fields still refetches the lists the e-mail is in. Telling such an update apart would mean deep-comparing every displayed field of the two sides, which is not worth its cost and fragility next to the refetch it would save.

On the captured events, a reply now refetches the drafts list and the three lists the original moves between, instead of three rounds of eight queries.

🧪 Testing​

  • Do not leak styles between tests

⚙️ Miscellaneous Tasks​

  • (dev) Proxy the PHP administration in the dev server
    • Unported sections of the new administration link to the PHP admin under /admin. Without a proxy the dev server answered those links with the operator's own index (history fallback); now they reach the real PHP admin, which also allows comparing both side by side while porting.
  • Satisfy oxlint in StoreProvider
    • StoreProvider took its props as PropsWithChildren of an empty interface, which oxlint's no-empty-object-type rejects. The interface had no members and no importers, so the component now takes React.PropsWithChildren directly. The next commit touches this file, which brings it under lint:changed.

[9.52.0] - 2026-10-30​

🚀 Features​

  • (email) Open video attachments in a large dialog
    • The hover preview on a video attachment is capped at the tooltip's size, too small to actually watch a clip. Received e-mails now get a view button next to the download one on video attachments, opening an xl dialog with the video playing. Composition is left alone: there the operator attached the file themselves.
  • (task) Search the task state select
    • A task queue can define many states, and scrolling a plain select to find one is slow. The state field in the task form is now built on the lib/ui combobox instead of the select: the trigger looks the same, and the popup opens with a search box that filters the states by name.

The props stay the same, so FinalTaskStateSelect and TaskForm are untouched. Closing states keep their own "Closes the task" group, and the popup says "No state found" when the search matches nothing.

  • (task) Change the task state from its reference card
    • A task linked to an email shows up as a card in the email's action history and linked list, but changing its state meant opening the task and the whole edit form. The state on the card is now clickable text: it opens the searchable state popup, and picking a state saves it with crm.tasks.edit right away. The cache is updated optimistically and rolled back with a notification if the save fails.

TaskStateSelect gets a bare variant for this, sharing the options and grouping with the form field. The option mapping moves out of TaskForm into toTaskStateOptions so the card and the form list the same states in the same order.

ReferenceCardShell was a single