refactor(ccenter): migrate queues to pinia + ui-datalist [WTEL-10140]

[dlohvinov]

Description

Migrates the queues section — the registry, the card, its seven nested tabs and
the members sub-entity — from Vuex + mixins onto Pinia + @webitel/ui-datalist,
and deletes the Vuex module at the end.

165 files, −2,500 lines net. Eleven commits, each of which typechecks,
lints, tests and builds on its own; the legacy module is removed only in the
last one.

Important

Blocked on webitel/webitel-ui-sdk#1665. This branch imports
getQueueDefaults, queueSchema, queueTypeRules, seven api modules and
QueuesAPI.getPermissionsList, none of which are in the published
@webitel/api-services yet. CI will be red until that lands and publishes.
Left as a draft for that reason.

Shape

commit	what
1	groundwork — shared defaults and api, the pinia stores, the type-branching configs
2	the queues table
3	the queue card and its five form tabs
4–8	the nested tabs: hooks, buckets + resource groups, skills, agents, logs
9	members
10	delete the legacy vuex module
11	tests

Worth knowing when reviewing

Type-dependent queues. A new queue's fields depend on ?type=, which
createCardStore knows nothing about, so the card uses manualSetup and seeds
getQueueDefaults(type) into the draft before anything reads it. That is what
gives Regle a complete key set to build $fields from — it derives them from
state, not from the schema, so a missing key costs a field its required marker
and error text with no error anywhere. The 250-line per-type Vuelidate switch
is gone; the asterisk on a type-dependent field now comes from the shared rule
table rather than the old :required="v.itemInstance.calendar" trick.

Create-on-demand is kept. Adding a hook or skill to an unsaved queue still
saves the queue first, but through the card's own validated save, provided to
the tabs. The mixin dispatched ADD_ITEM directly and could persist a
half-filled queue; now an invalid one blocks the add and shows its errors.

The logs filters move into the logs tab. The card used to render them in
its actions panel via a currentTab.filters component name, so the page had to
know one tab's internals and no other tab could ever have filters.

Persistence is off for the five in-card tabs. Route persistence writes
un-namespaced filters/page/size/sort, and the tabs share one url. Logs
and members keep it — they have their own routes, and a filtered log is worth
sharing.

Behaviour changes

• Queue filters now survive leaving and returning, like every migrated
  registry. The WTEL-9657 ?type=-preserving reset goes with its cause: the
  old panel reset by rewriting the whole route query, on unmount.
• The agents tab loses its edit and delete row actions — the api has no
  delete, and editItem pushed a param no route declares, so neither worked.
• Members' mislabelled settings icon becomes a real column selector.
• The queue log's duration filter starts working. The store held duration
  as {from, to} while the api read durationFrom/durationTo, so the bounds
  were never sent.
• Buckets and resource groups still delete without confirmation, and hooks
  still asks. Preserved as-is — unifying them is a UX call, not a refactor.
• Validation messages are English-only until a Regle i18n layer exists. That
  is already true of every migrated entity.

Tests

The five component specs here were shallowMount + exists() smoke tests
bound to mixin mocks, two of them overriding a computed, which <script setup> does not allow. They are replaced by 86 tests over the logic that can
fail silently: the CSV normaliser, the member communications collection, the
per-type control map, tab-to-route mapping, table headers across all eight
tables, and filter names matching the params each api reads.

Writing them found a real bug in this branch: useMemberCommunications.remove
compared raw objects against the draft's reactive proxies, so Set.has never
matched. It worked from the tab, which passes proxies back, but any caller
holding the underlying object would have deleted nothing.

Verification

typecheck at the repo's pre-existing error count (this branch adds none) · lint
clean · 136 unit tests · production build succeeds.

Not verified: the app was never exercised against a backend. The per-type
$fields seeding is the one thing no automated check covers — please open a
queue of each of the ten types, create and edit, and confirm required markers
and error text appear on Params and Processing.

Related Tasks

• WTEL-10140

Related PR's / Issues

• refactor(api-services): queue api modules, Zod schemas and type defaults [WTEL-10140] webitel-ui-sdk#1665 — must merge and publish before this one.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c761c6fe-66d3-4078-a9db-cb2eeebfd3e5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}