Share to Esbabbler

A Share command on published resources: pick one of your rooms, add an optional note, and the public /view/[type]/[id] link lands there as a message. It is the first real bridge between resources and esbabbler, and it is deliberately the smallest one that works — client-side only, reusing the existing message-create path, with no new procedures and no schema.

Copying the link off the Overview blade and pasting it into a room by hand still works; this does the same thing in place.

How it works

flowchart LR
  CMD["Share command<br/>(command bar, published only)"] --> DLG["ShareDialog"]
  DLG -->|room.readRooms| ROOMS["your rooms → UiSelect"]
  DLG --> MSG["getShareMessage<br/>note + newline + public URL"]
  MSG -->|"message.createMessage<br/>{ roomId, message }"| ROOM[("room message")]
  ROOM --> OK["notification: Shared to {room}<br/>+ Open room action"]

• The command appears for PublishableResourceType only while published. An unpublished resource has no public URL, so there is nothing to share until it has one — the command is absent, not disabled. It sits beside the publish toggle in the command bar and collapses into the … overflow on narrow viewports with everything else.
• The dialog reads your rooms once per open (it mounts only while open) into a UiSelect, with an optional note field. No rooms is an empty state pointing at esbabbler, not a disabled button with no explanation.
• The message is sanitized HTML with an explicit anchor — message bodies render through v-html and nothing in the pipeline autolinks bare text, so getShareMessage builds the link itself (<a href … target="_blank">) and wraps the escaped note above it, newlines as line breaks. It goes through the standard message.createMessage mutation, so RBAC, rate limits, profanity filtering, and the whole message pipeline apply unchanged; rich embeds/unfurls stay deferred.
• The dialog validates what it sends — the length rule checks the composed message (note + markup + link) against the message cap, not just the raw note, so a note that fits the counter can never produce a message the server rejects.
• Success lands in the notifications store with an Open room action.

Key files

Notes

• Deliberately one direction (resource → room). Surfacing "shared with me" inside the explorer is a different feature needing read-model thought, and is not in this cut.
• The message is the caller's own message in their own room — no special message type, no service-to-service write, no elevated permission. Deleting the resource later leaves a dead link, exactly like any pasted URL.