@revenexx/studio-integrations 0.5.1 → 0.7.0

package/CHANGELOG.md

@@ -0,0 +1,428 @@
+# @revenexx/studio-integrations
+
+## 0.7.0
+
+### Minor Changes
+
+- f7ddd90: The run surfaces now update from pushed platform events, not only from their own
+  refresh.
+
+  Where a host has Talkback configured, the Runs list, a workflow's Runs tab, a run's
+  record and the replay canvas react to the run and workflow lifecycle the integrations
+  service publishes — so a run that finishes is on screen in about a second instead of
+  up to three, and a run started from the API, a schedule or an MCP tool appears on an
+  idle list that previously had no reason to ask. `workflow.deleted` also takes its runs
+  off the list, which no `run.deleted` event exists to do.
+
+  A run's record follows the same reports, and it now re-reads everything it shows when
+  the run it is open on ends — the status it displays comes from a different request
+  than the one an ending run used to trigger, so a record left open on a finishing run
+  could keep showing the state before it ended. That is fixed for the reported route;
+  the three-second poll behind it is unchanged.
+
+  While events are actually arriving, each surface's own refresh slows to every 30
+  seconds and stays as the backstop rather than stopping — the connection signal
+  available today cannot tell a quiet socket from a dead one, so a list that stopped
+  converging was not a trade worth making. **A connection that reports nothing is
+  treated as no connection**: the slower refresh is taken only once something has been
+  delivered, so a tenant whose event catalogue does not release these topics to browsers
+  keeps the cadence it always had rather than becoming the slowest configuration of the
+  three. If the connection drops and comes back having missed more than the platform can
+  replay, every surface reads again instead of waiting for a report that no longer
+  exists.
+
+  With no Talkback host configured — the default — nothing is subscribed, neither
+  `@revenexx/talkback-js` nor `centrifuge` is loaded, and every surface polls exactly as
+  before.
+
+  **This raises the floor for `@revenexx/studio-shared` to `^0.3.0`**, which is the
+  release that carries the realtime seam. A host installing this module gets the newer
+  one automatically; a host that pins studio-shared itself has to move with it, or it
+  will end up with two copies and no realtime at all.
+
+  Realtime needs `@revenexx/talkback-js` and `centrifuge` in the host application —
+  they are optional peers of studio-shared, so a host that never sets a Talkback host
+  installs neither.
+
+- 9ef81b8: The studio reads in the language your application chose, both halves of the
+  screen at once.
+
+  Until now every surface was English. Two things change that. The text the node
+  packages publish — a node's name, what it is for, the label and example of every
+  setting it offers, a credential type's fields, a template's whole description —
+  has been shipping in German as well as English all along, and was being discarded
+  on the way to the screen; it is now resolved in the reader's language. And the
+  studio's own chrome — headings, buttons, tabs, table headers, empty states,
+  toasts, confirmations — is read from a message catalogue the module carries
+  itself, in English and German.
+
+  You do not need an i18n library installed, and the module never reads your
+  catalogue, a cookie or a browser setting: the language comes from you. Wire one
+  of two ways.
+
+  A language that does not change, in `nuxt.config.ts`:
+
+  ```ts
+  export default defineNuxtConfig({
+    modules: ["@revenexx/studio-integrations"],
+    studioIntegrations: { locale: "de" },
+  });
+  ```
+
+  Deployments can override that with `NUXT_PUBLIC_STUDIO_INTEGRATIONS_LOCALE`
+  without a rebuild.
+
+  A language the user switches while the app is running, from a plugin of yours:
+
+  ```ts
+  const { setLocale } = useIntegrationsLocale();
+  watch(hostLocale, (l) => setLocale(l), { immediate: true });
+  ```
+
+  `useIntegrationsLocale()` is auto-imported like every other composable here, so
+  you import nothing. A switch reaches surfaces that are already open — no reload,
+  no refetch, no reopening a dialog. Both routes may be left alone: with neither
+  wired the studio is English, exactly as before, so upgrading changes nothing
+  until you ask it to.
+
+  A tag is BCP-47 and a region falls back to its language, so `de-CH` reads German
+  rather than English; anything the catalogue does not carry reads English.
+
+  **This expects a client-rendered host.** The language is held once per module
+  instance, which is once per browser tab on the client and once per process on a
+  server. If you render the studio server-side _and_ give each visitor their own
+  language, one visitor's choice can reach another's page — a page in the wrong
+  language, nothing more, since the value only chooses between the translations of a
+  string. A single fixed language is unaffected either way. Both routes above are
+  safe in a client-rendered app, which is what the known consumers are.
+
+  Four English strings changed spelling, to British. One of them is an accessible
+  name: the grey swatch in the sticky-note and group-frame colour pickers is
+  `Grey`, not `Gray` — update it if a test of yours addresses it by name. The other
+  three are wording only: two tooltips on the sample-payload button say `catalogue`,
+  and the workflow settings dialog says `Execution behaviour`.
+
+- 7cb9f1c: The studio's lists narrow for real.
+
+  Credentials, runs, workflows and schedules each carried a filter button whose menu
+  read "No filters defined." — it could never filter anything. Each now narrows by the
+  dimensions its own rows already show: a credential's state and system, a run's
+  outcome and what started it, a workflow's position, build and dispatch mode, and
+  whether a schedule is live plus the timezone it fires in. Two choices narrow
+  together, each has a way back to everything, and the words on the menu are the words
+  on the rows.
+
+  Secrets loses the button instead: a key and two dates have nothing categorical to
+  narrow by, so the honest outcome there is not offering it.
+
+  A narrowing applies to the rows the page has loaded. On the lists collected per
+  workflow that is as far back as the page has read.
+
+- 8f332af: Deleting is drawn with one bin everywhere, duplicating with one pair of sheets, and a
+  trigger's delete button says what it deletes.
+
+  The studio drew the delete action with three different bin glyphs, two of them one
+  click apart on the same node: a node's hover toolbar used Lucide's bin while that
+  node's own inspector used Solar's, and the credential surfaces used a third, fuller
+  Solar bin. Nothing was broken — what it cost is recognition, on the one action that
+  cannot be undone. Every delete and remove in the studio now draws Solar's
+  `TrashBinMinimalistic`.
+
+  The copy sheets sat one button along and are folded in: a node's hover toolbar drew
+  Lucide's glyph for **Duplicate** while that same node's inspector drew Solar's for
+  **Copy**. Both are Solar's now.
+
+  Two things a host or a test may notice:
+
+  - **The trigger card's delete button has an accessible name**, `Delete trigger`,
+    where it previously fell back to its `Delete` tooltip. That is what the node card's
+    `Delete node` already did, so the two can now be addressed and heard the same way.
+  - **No delete icon is imported under another library's name any more.** The alias
+    `TrashBinMinimalistic as Trash2` is what hid the divergence — two components read
+    identically in the markup and differed only in an import line. The bin travels as
+    `TrashBin`.
+
+  Why Solar, what `lucide-vue-next` is still for, and why the glyph itself is not
+  promised in a spec: `docs/icons.md`. It also names what is left — five shapes the
+  studio still draws from both libraries — and the ticket that carries them.
+
+- fa0ef1a: The studio navigation stays when a workflow is opened, and the canvas gets its
+  width only when the operator asks.
+
+  Until now, opening a workflow — or one of its runs — folded the navigation away on
+  mount, and nothing anywhere brought it back: the way on was the breadcrumb or the
+  browser's back button. That fold is gone. The rail now stands on every surface,
+  including a workflow's canvas, and a control at the head of the workflow page,
+  reading **Hide navigation**, hands its width to the canvas when the operator wants
+  it. The same control then reads **Show navigation** and gives it back, without
+  leaving the surface. The choice is remembered per browser, so it is stated once
+  rather than on every visit, and it applies to the canvas alone — a run's record,
+  the run lists and the earlier versions keep the navigation either way.
+
+  Two things to know if you host this module:
+
+  - **A folded rail is now `inert` and `aria-hidden`.** It used to be clipped to zero
+    width with its links still focusable, so a keyboard walked into a navigation
+    nobody could see. If a test of yours reaches into the collapsed sidebar, it will
+    no longer find it in the accessibility tree — which is the point.
+  - **The fold is still driven by `useIntegrationsFocus()`**, unchanged, so a host
+    shell that reads `focused` keeps working as before. What changed is who turns it
+    on: nothing does it by itself any more. If your own shell collapses the sidebar
+    on that state, make sure the surface doing so also offers the way back — the
+    control belongs to the page, because a host shell can be replaced and the module's
+    cannot reach into it.
+
+  Two new accessible names, in English and German: `Hide navigation` /
+  `Show navigation`.
+
+### Patch Changes
+
+- 30f5bda: A group frame now tells the truth about what it holds as soon as a member is deleted.
+
+  Deleting a node out of a group left the frame printing the count it had before —
+  `Invoice sync · 3 nodes` over two remaining nodes — until the page was reloaded. The
+  saved workflow was correct throughout; it was the caption that lagged. The larger
+  half of the same defect: deleting a frame's last member left the frame drawn on the
+  canvas over a workflow that no longer contained it, so the editor showed a group
+  that had already ceased to exist.
+
+  Both follow the deletion at once now. An empty frame you drew yourself still stays —
+  it counts down to `0 nodes` and waits to be filled.
+
+  The cause was timing rather than arithmetic: the canvas rebuild ran inside Vue Flow's
+  own change pass, which left the rendered graph on the array from before the deletion.
+  It is deferred by one tick. Nothing about the API, the saved blob or the keyboard
+  changes.
+
+- d690841: A note on a read-only canvas no longer offers controls that do nothing.
+
+  On the run replay and the revision preview, a sticky note used to be drawn with
+  the toolbar it has in the editor — a bin, seven colours, a corner handle — and
+  could still be double-clicked into a text field. None of it had any effect: the
+  note survived its own Delete, typing into it changed nothing, and the workflow
+  never became dirty. A reader could not tell "not allowed here" from "broken".
+
+  The note is now read-only in the way a node card and a group frame already were:
+  no toolbar, no resize handle, and a double-click opens nothing. An empty note is
+  quiet too: the _Double-click to edit_ hint belongs to the editor, and on these
+  canvases it named the one gesture the note refuses. Everything the note says stays
+  exactly as readable, formatting and all — this removes affordances, not content.
+
+  A double-click on a read-only note now reaches the canvas instead of being
+  swallowed, so it zooms there like a double-click on a node card or on empty space.
+  A group frame's label was swallowing it the same way, and no longer does — the note
+  and that label were the two places on those canvases where the gesture did nothing
+  at all, and a dead spot reads as broken. The zoom itself is how these canvases
+  behave rather than something promised: what is promised is that nothing opens to be
+  edited.
+
+  If you render `StickyNoteView` yourself: the read-only state _is_ the absence of
+  its callbacks. `onUpdate` and `onRemove` in `StickyNodeData` are now optional, and
+  a note handed neither draws no tools — the pattern `GroupFrameView` already used
+  for its own toolbar. Passing no-ops, which is what the two read-only panels did,
+  now means "editable, and nothing happens".
+
+  A host addressing the note's `Delete note` button or its colour swatches on a
+  replay or preview canvas will no longer find them. That is the fix, which is why
+  this is a patch: nothing here is additive, and what a host can observe is the
+  defect being gone.
+
+## 0.6.0
+
+### Minor Changes
+
+- 3686d9e: The node inspector's controls report honest states — a field that is loading,
+  empty or unavailable says which, instead of all three looking alike — and the
+  trigger surface gains a payload form built from the trigger's own shape rather
+  than a free-text box. Rows keep stable keys, so editing one no longer re-orders
+  the rest.
+- 3686d9e: Activating a workflow the platform refuses now says why. The validation feedback
+  the service returns is surfaced in the editor instead of the activation failing
+  silently, and a refusal that carries no readable detail falls back to wording
+  that still tells the user what happened.
+- 3686d9e: Placing a node no longer forces its configuration open. Dropping a node onto the
+  canvas just places it; you open the settings when you want them, through an edit
+  affordance that now stays visible on the node card rather than appearing only on
+  hover. The affordance is shown only for nodes that actually have something to
+  configure.
+- 3686d9e: A node that ships in several versions lets you choose which one you place,
+  instead of the palette silently picking one. The chosen version is shown on the
+  node card, so a workflow built against an older version is readable on the
+  canvas.
+- 3686d9e: A node is now marked by its own symbol combined with a vendor badge, so two
+  nodes from the same vendor stay distinguishable while still reading as that
+  vendor's. The badge is drawn only where it adds something — including search
+  hits in the palette — and a node with no symbol of its own is marked honestly
+  rather than given a stand-in.
+
+  The component behind this is renamed `NodeLogo` → `NodeMark`. `NodeLogo` remains
+  as a shim so hosts that reference it keep working.
+
+- 3686d9e: The canvas says which output path leads the eye. Edges now carry importance
+  rather than colour, so the main path reads as the main path, and colour is
+  reserved for the two states where it means something — green for the ordinary
+  output, rose for the error output. The inspector's port dots use the same neutral
+  tone as the canvas, and an error port's label stays legible instead of being
+  tinted into the background.
+- 3686d9e: The mouse wheel zooms the canvas instead of panning it vertically — on the
+  editor and on the read-only canvases alike. The zoom readout announces its
+  percentage again, so the level is available to screen readers and not only to
+  the eye.
+- 3686d9e: Node cards drop the generated subtitle and surface the node's note instead. The
+  note is marked in the card's corner and its panel flips open from there, so a
+  card carries what somebody wrote about the node rather than a line derived from
+  its configuration. The marker is reachable from the keyboard, and the note's
+  description stays in the workflow tree rather than living only in the panel.
+- 3686d9e: A node can say what it is for. The description from the node's manifest is shown
+  in the inspector, and the note moves out of the settings into its own place, so
+  the text the vendor wrote and the text you wrote are no longer mixed into one
+  field. The explanation can be reached by pointer as well as keyboard, and Escape
+  closes the note without closing anything behind it. Whitespace alone no longer
+  counts as a note.
+- 3686d9e: A workflow variable has a value, not a default. The field is named for what it
+  actually is — the value the workflow runs with — which removes the suggestion
+  that something else would override it, and a variable can be marked as required
+  so an incomplete workflow is caught before it runs.
+- 3686d9e: Configuring a node is simpler. The configuration itself gets the dialog, with
+  mapping and testing available on call rather than competing for the same space,
+  and the separate outputs strip is gone — the third tab is **Output**. A setting
+  the last save refused is marked as such, so a rejected save says which field it
+  was about, and the dialog is sized to its content instead of leaving the fold to
+  hide a control. Switching away from a tab the bar no longer draws leaves nothing
+  selected behind.
+- 3686d9e: You can say when a workflow runs without writing cron. The schedules page offers
+  the choice directly, a schedule can fire several times a day, and every schedule
+  states when it next fires instead of showing an expression and leaving you to read
+  it.
+
+  The reading is exact rather than approximate: a step that does not divide its
+  field is no longer described as a plain interval, and a named weekday no longer
+  widens a schedule to the whole week.
+
+- 3686d9e: A webhook trigger can say who is allowed to call it. Protection profiles are
+  offered on the trigger, the secret behind one can be rotated, and exposing an
+  endpoint persists the default profile rather than leaving the webhook open until
+  somebody sets one.
+
+### Patch Changes
+
+- 3686d9e: The node inspector's credential picker separates the credential's name from its
+  state, and reports the state it was actually told rather than deriving one. A
+  deleted credential no longer reads as though none had been chosen — the dead
+  reference is announced, not only drawn — and a failed test keeps a readable
+  reason.
+- 3686d9e: **Tidy up** no longer leaves a node's outputs crossing each other. After an
+  auto-layout the out and error branches keep to their own lanes, and where one
+  output fans out to several nodes the edge bends are staggered — mirrored on both
+  sides — so sibling branches read alike instead of overlapping into a single
+  line.
+- 3686d9e: The hover toolbar no longer appears on canvases you cannot edit. On a run replay
+  or any other read-only canvas, **Duplicate** and **Delete** used to show up on
+  hover and do nothing; they are now absent instead of dead.
+- 3686d9e: **Tidy up** no longer routes a node's ordinary output and its error output across
+  each other. Branches are re-slotted so the two leave the spine without crossing,
+  and where the current order gives no answer the target node's id breaks the tie —
+  so the same workflow tidies up the same way every time.
+- 3686d9e: A node that ends the run no longer draws an output port. Stop and error nodes
+  declare no outputs, so the canvas gave them a port that could never lead
+  anywhere; that port is gone, and nothing can be connected to it by accident.
+- 3686d9e: The actions button on a workflow row has an accessible name. It is icon-only and
+  sits in a row that offers nothing else to address it by, so it now names the
+  workflow it acts on — `Actions for <workflow>` — instead of being unreachable to
+  anyone not using a pointer.
+- 3686d9e: Every form field and icon-only control in the studio has an accessible name, and
+  each page declares its main content landmark. The skip link now moves focus
+  rather than only changing the address, so it actually skips something, and the
+  icon picker keeps the name of the popover it opens from.
+- 3686d9e: **Delete** and **Backspace** no longer delete nodes while a dialog or panel
+  covers the canvas. The canvas stands its keyboard handling down for as long as an
+  overlay is open, so a keystroke meant for the text field in front of you cannot
+  remove a node behind it.
+- 3686d9e: The validation banner is summarised per node, and the nodes it names are marked
+  on the canvas — so a workflow that will not activate points at where the problem
+  is instead of listing findings you have to match up yourself. A finding the
+  platform attributes to no node carries only its message rather than being pinned
+  to an arbitrary one. Marks are held back while a node is being dragged, so the
+  re-sync no longer interrupts the drag.
+- 3686d9e: Running an incomplete workflow names the settings that are missing, the way the
+  activation gate already did — instead of a refusal you have to go looking for the
+  cause of. A finding the platform attributes to no node is named rather than only
+  counted, and a refusal that arrives with nothing readable in it no longer leaves
+  the user with no message at all.
+- 3686d9e: A credential's test result is no longer wiped by the reload that follows it. The
+  result you just produced stays on screen instead of disappearing the moment the
+  list refreshes, and a prototype key is no longer offered as though it were a
+  credential type.
+- 3686d9e: The template gallery says which kind of nothing it is showing — no templates at
+  all reads differently from nothing matching your search. A template's vendor can
+  be searched for, and three names that the detail page relied on but never put on
+  screen are now there, so what a template arrives wired with is readable before
+  you install it.
+- 3686d9e: The runs and schedules pages stop reporting figures they did not have. Missed
+  runs were collected before the workflows they belong to had arrived, so they came
+  out short; they are now collected once the list is in. Leaving the page no longer
+  takes the count with it, so coming back shows what ran, what runs next and what
+  never got to run rather than an empty summary.
+- 3686d9e: Two controls on the workflows list no longer claim a name derived from data that
+  had not loaded, so they are addressable as soon as the page is — including the
+  route to the create-workflow dialog, which sits behind two doors and had nothing
+  stable to reach it by.
+- 3686d9e: The audit log pages properly and closes properly. A second pager sat behind the
+  first and could disagree with it; there is now one. Searching for a person finds
+  them through the actor column rather than depending on the resource column
+  repeating the same value, and the one way of closing an opened record that never
+  worked now does.
+- 3686d9e: Credential dialogs no longer come up empty for a managed type. The managed types
+  ask whether the cockpit is actually there instead of assuming it, so the fields
+  are rendered when the source can answer and the dialog says what it cannot offer
+  when it cannot.
+- 3686d9e: The **Created** and **Updated** columns on the secrets list show something. They
+  were always empty; they now carry the dates the service records, a cell with no
+  date claims no timestamp rather than rendering an epoch, and the dates stay out
+  of the search box so filtering by name is not confused by them.
+- 3686d9e: Text that arrives from the API is localised by one resolver instead of fifteen
+  private copies, so a label resolves the same way wherever it is shown and a
+  missing translation falls back consistently rather than differently per page.
+- 3686d9e: Pages no longer render empty data while their load is still in flight. The ten
+  composables that each guarded their own load now share one guard that waits for
+  the load already running instead of handing back an empty result, so a second
+  caller is answered once the data is there. The workflows list stops claiming
+  "Never run" when the runs simply had not arrived yet.
+- 3686d9e: The dashboard's figures are there on the first visit rather than after a reload.
+  **Needs attention** reports the state now instead of every failure the workflow
+  has ever had, each figure that answers a click is a link and says its number, and
+  a request that is counted is recounted when it changes rather than going quiet.
+- 3686d9e: A failed run keeps the reason the platform recorded, and shows the moment the
+  failure happened rather than the moment the run started. Where the platform left
+  the reason empty the run says so, instead of presenting the blank as though
+  nothing had gone wrong.
+- 3686d9e: The dashboard's templates panel is named for what it offers rather than for a
+  ranking it never measured. It was headed "Popular templates" while showing no
+  measure of popularity; it now reads **Start from a template**.
+- 3686d9e: A connection can only leave an output and arrive at an input. Two input ports
+  could be joined to each other and the result saved, producing a workflow the
+  platform would never run; that is refused now. Connections already saved the wrong
+  way round are not repaired by this change — they have to be redrawn.
+- 3686d9e: Template categories are named from one source, so the filter and the cards cannot
+  disagree, and the category list names the two categories that actually ship rather
+  than one nobody could select. A template is presented by a single card component in
+  two densities instead of two implementations that had drifted apart, and what
+  choosing a card does is defined once.
+- 3686d9e: An audit entry opened from a row holds the keyboard and gives it back when it
+  closes. The panel used to leave focus in the row behind it, so the keyboard was
+  somewhere the user could no longer see.
+- 3686d9e: The template gallery says it is loading in words, not only as a shimmer, so the
+  wait is announced rather than being visible only to the eye — and a loading
+  gallery no longer looks exactly like an empty one. The announcement and the
+  placeholders are derived from the same condition, and the wait ends in words too.
+- 3686d9e: A port name comes back whole. A name containing `__` was cut at the separator, and
+  a handle id with no port name in it produced an empty string that read as a real
+  name; the first round-trips intact now and the second answers with nothing at all.
+- 3686d9e: The webhook and event trigger copy spells it **catalogue**, matching the rest of
+  the studio's British English — in the loading message, the payload hint and the
+  line shown when a topic has no sample payload.
+- 3686d9e: Saving a credential says what happened. A save that is refused states its reason
+  — in the dialog and at the field it concerns, where a scrolling form cannot hide
+  it — rather than the service's count of the other fields, and it reaches every
+  field it names. A save that lands closes the dialog. A refused edit says why too,
+  instead of failing silently.

package/README.md

@@ -30,6 +30,33 @@ supply a token/tenant through the platform provider (override
 `usePlatformAuth` / `usePlatformTenant`, or the standalone defaults read
 `NUXT_PUBLIC_DEV_TOKEN` / `NUXT_PUBLIC_DEV_TENANT`).
 
+### Language
+
+The studio speaks English and German. That covers both halves of a screen: the
+text node packages publish (names, descriptions, settings) **and** the studio's
+own chrome — headings, buttons, tabs, empty states, toasts. Both fall back to
+English. The studio has no switcher of its own, so hand the choice over one of
+two ways:
+
+```ts
+// nuxt.config.ts — a language that does not change
+export default defineNuxtConfig({
+  studioIntegrations: { locale: 'de' }, // or NUXT_PUBLIC_STUDIO_INTEGRATIONS_LOCALE
+})
+```
+
+```ts
+// a host plugin — a language the user switches while the app is running
+const { setLocale } = useIntegrationsLocale()
+watch(hostLocale, l => setLocale(l), { immediate: true })
+```
+
+A switch reaches surfaces that are already open; nothing is refetched. With
+neither wired, the studio is English. The module carries its own message
+catalogue (`runtime/i18n/messages/*.json`) — it never reads the host's, and needs
+no i18n library installed in the host. See
+[`docs/interface-language.md`](docs/interface-language.md).
+
 ## ⚠️ Tailwind: you MUST scan this package
 
 The module ships its runtime as source-ish `.vue`; Tailwind generates the
@@ -60,8 +87,13 @@ cockpit monorepo under `packages/studio-integrations`).
 pnpm install     # runs the module `prepare` (nuxt-module-build)
 pnpm test        # vitest
 pnpm build       # dist/
+pnpm changeset   # record what your change does to the version
 ```
 
+Branch off `main` as `feature/<desc>`, `fix/<desc>` or `chore/<desc>` — GitHub refuses
+the first push of any other name, and `main` itself takes a reviewed pull request with
+CI green: [`docs/branch-protection.md`](docs/branch-protection.md).
+
 Hosts to develop against:
 
 * **Playground** (`playground/`, in this repo): thin standalone Nuxt host that
@@ -77,7 +109,19 @@ Hosts to develop against:
 
 ## Release
 
-Bump `version` in `package.json` and push to `main` — CI
-(`.github/workflows/publish.yml`) publishes any version that isn't on npm
-yet, via npm Trusted Publishing (the trusted publisher on npmjs is bound to
-this repo + workflow file).
+Versioning is driven by [Changesets](https://github.com/changesets/changesets),
+so `version` in `package.json` is never edited by hand. Every pull request
+records what it does to the version — CI fails without it:
+
+```bash
+pnpm changeset          # pick patch/minor/major, then write the note
+pnpm changeset --empty  # …for a PR that intentionally releases nothing
+```
+
+Releasing is then merging a pull request. Pushes to `main` that carry changesets
+make CI open a **"Version Packages"** PR with the bump and `CHANGELOG.md`
+applied; merging that PR publishes to npm (Trusted Publishing over OIDC, no
+token) and notifies the cockpit.
+
+Full policy, the SemVer contract, and why publishing is deliberately not
+`changeset publish`: [`docs/versioning.md`](docs/versioning.md).

package/dist/module.d.mts

@@ -1,6 +1,22 @@
 import * as _nuxt_schema from '@nuxt/schema';
 export * from '../dist/runtime/types/integrations.js';
 
-declare const _default: _nuxt_schema.NuxtModule<_nuxt_schema.ModuleOptions, _nuxt_schema.ModuleOptions, false>;
+interface ModuleOptions {
+    /**
+     * The language the studio renders in, as a BCP-47 tag (`en`, `de`, `de-CH`).
+     *
+     * This is the *initial* language and the whole of the contract for a host
+     * whose language never changes. A host with a switcher leaves it alone and
+     * calls `useIntegrationsLocale().setLocale()` instead — its plugins run after
+     * this module's, so the two do not fight over the value.
+     *
+     * It reaches the runtime through `runtimeConfig.public.studioIntegrations`,
+     * so a deployment can override it with
+     * `NUXT_PUBLIC_STUDIO_INTEGRATIONS_LOCALE` without a rebuild.
+     */
+    locale?: string;
+}
+declare const _default: _nuxt_schema.NuxtModule<ModuleOptions, ModuleOptions, false>;
 
 export { _default as default };
+export type { ModuleOptions };

package/dist/module.json

@@ -1,7 +1,7 @@
 {
   "name": "@revenexx/studio-integrations",
   "configKey": "studioIntegrations",
-  "version": "0.5.1",
+  "version": "0.7.0",
   "builder": {
     "@nuxt/module-builder": "1.0.2",
     "unbuild": "unknown"

package/dist/module.mjs

@@ -1,6 +1,6 @@
 import { existsSync, readdirSync, statSync } from 'node:fs';
 import { join } from 'node:path';
-import { defineNuxtModule, createResolver, hasNuxtModule, installModule, addComponentsDir, addImportsDir, extendPages } from '@nuxt/kit';
+import { defineNuxtModule, createResolver, addPlugin, hasNuxtModule, installModule, addComponentsDir, addImportsDir, extendPages } from '@nuxt/kit';
 
 function toSegment(name) {
   if (name.startsWith("[...")) return `:${name.slice(4, -1)}(.*)*`;
@@ -27,9 +27,16 @@ const module$1 = defineNuxtModule({
     name: "@revenexx/studio-integrations",
     configKey: "studioIntegrations"
   },
-  async setup(_options, nuxt) {
+  defaults: {
+    locale: "en"
+  },
+  async setup(options, nuxt) {
     const { resolve } = createResolver(import.meta.url);
     const runtime = resolve("./runtime");
+    const publicConfig = nuxt.options.runtimeConfig.public;
+    const configured = publicConfig.studioIntegrations ?? {};
+    publicConfig.studioIntegrations = { ...configured, locale: configured.locale ?? options.locale };
+    addPlugin(resolve("./runtime/plugins/locale"));
     if (!hasNuxtModule("@solar-icons/nuxt", nuxt)) {
       await installModule("@solar-icons/nuxt", {
         namePrefix: "Solar",
@@ -52,6 +59,7 @@ const module$1 = defineNuxtModule({
     nuxt.options.build.transpile.push(runtime);
     addComponentsDir({ path: join(runtime, "components"), pathPrefix: true });
     addImportsDir(join(runtime, "composables"));
+    addPlugin(join(runtime, "plugins", "realtime.client"));
     extendPages((pages) => {
       const pagesDir = join(runtime, "pages", "integrations");
       if (!existsSync(pagesDir)) return;