feat(ui): block settings menu as a plugin surface

.github/actions/base-coverage/action.yml

@@ -22,15 +22,27 @@ runs:
         fetch-depth: 0
         submodules: true
 
-    - name: Check package exists on base ref
+    # A base-ref comparison only means something when the base ref can actually produce
+    # a coverage report. Two cases cannot: the package may not exist there yet, or it may
+    # exist without a test suite, which is the case for the PR that first adds one. The
+    # second needs its own check -- package.json is present, so the file test passes, and
+    # `yarn workspace ... test:coverage` then fails with "couldn't find a script".
+    - name: Check base ref can report coverage
       id: check
       shell: bash
       run: |
-        if [ -f "${{ inputs.working-directory }}/package.json" ]; then
-          echo "exists=true" >> "$GITHUB_OUTPUT"
-        else
+        if [ ! -f "${{ inputs.working-directory }}/package.json" ]; then
           echo "Package not present on base ref (new package), skipping base coverage"
           echo "exists=false" >> "$GITHUB_OUTPUT"
+        elif ! node -e "
+          const fs = require('fs');
+          const pkg = JSON.parse(fs.readFileSync(process.argv[1] + '/package.json', 'utf8'));
+          process.exit(pkg.scripts && pkg.scripts['test:coverage'] ? 0 : 1);
+        " "${{ inputs.working-directory }}"; then
+          echo "Package has no test:coverage script on base ref (suite added in this PR), skipping base coverage"
+          echo "exists=false" >> "$GITHUB_OUTPUT"
+        else
+          echo "exists=true" >> "$GITHUB_OUTPUT"
         fi
 
     - name: Setup Node

.github/agents/docs-updater.agent.md

@@ -27,7 +27,7 @@ Follow this sequence for every run:
 | Changed area | Primary doc(s) | Diagram(s) |
 |---|---|---|
 | Package list, dependencies, overall structure | `docs/architecture.md`, root `README.md` | `diagrams/architecture-overview.mmd` |
-| `EditorJSModel`, `EditorDocument`, `BlockNode`, `TextNode`, `ValueNode`, `BlockTune`, `Index`, `CaretManager` | `docs/model.md` | `diagrams/model-tree-structure.mmd` |
+| `EditorJSModel`, `EditorDocument`, `BlockNode`, `TextNode`, `ValueNode`, `PluginDataNode`, `Index`, `CaretManager` | `docs/model.md` | `diagrams/model-tree-structure.mmd` |
 | Event classes, `EventType`, `EventBus` | `docs/events.md` | `diagrams/events-catalog.mmd` |
 | `Core`, `BlocksManager`, `BlockRenderer`, `SelectionManager`, `ToolsManager`, `EditorAPI`, plugin/tool lifecycle | `docs/plugins.md` | `diagrams/plugin-lifecycle-flow.mmd` |
 | `DOMBlockToolAdapter`, `CaretAdapter`, `FormattingAdapter`, `InputsRegistry`, `BeforeInputUIEvent` | `docs/input-handling.md` | `diagrams/block-adapter-input-flow.mmd`, `diagrams/caret-selection-flow.mmd`, `diagrams/inline-formatting-flow.mmd` |

.github/workflows/default-block-settings-plugin.yml

@@ -0,0 +1,20 @@
+name: Default block settings plugin check
+on:
+  pull_request:
+  merge_group:
+
+permissions:
+  contents: read
+  pull-requests: write
+  issues: write
+  actions: read
+
+jobs:
+  package-check:
+    uses: ./.github/workflows/package-check.yml
+    with:
+      package-name: '@editorjs/default-block-settings-plugin'
+      working-directory: './packages/plugins/default-block-settings-plugin'
+      include-mutations: true
+    secrets:
+      stryker_dashboard_api_key: ${{ secrets.STRYKER_DASHBOARD_API_KEY }}

.github/workflows/ui.yml

@@ -0,0 +1,10 @@
+name: UI check
+on:
+  pull_request:
+
+jobs:
+  package-check:
+    uses: ./.github/workflows/package-check.yml
+    with:
+      package-name: '@editorjs/ui'
+      working-directory: './packages/ui'

docs/README.md

@@ -61,7 +61,7 @@ The system stays decoupled because each step communicates through interfaces and
 
 - `EditorjsPlugin`: general UI/behavior plugin registered via `core.use()` with `PluginType.Plugin`. UI components like `BlocksUI` typically declare a `static type` from `UiComponentType` but are bound to `PluginType.Plugin` internally.
 - `UiComponentType`: reserved string keys for UI component slots (`shell`, `blocks`, `inline-toolbar`, `toolbox`, `toolbar`). These name components in the UI layer but are **not** used as arguments to `core.use()` — plugins are registered by `PluginType` or `ToolType` values.
-- `BlockTool` / `InlineTool` / `BlockTune`: tool contracts registered via `core.use(ToolConstructor, options)` during setup. The `tools` config field provides tool settings that `ToolsManager` applies during `initialize()`.
+- `BlockTool` / `InlineTool`: tool contracts registered via `core.use(ToolConstructor, options)` during setup. The `tools` config field provides tool settings that `ToolsManager` applies during `initialize()`.
 - `Index`: serializable location in the document tree, independent of DOM nodes. Subclasses (e.g. `BlockIndex`, `TextIndex`, `DataIndex`) cover distinct target types. Built with immutable factory methods like `Index.block()` or `Index.text()`; serialized to a compact JSON string for caret storage and OT operations.
 - `DataKey`: branded string identifying a data slot inside a `BlockNode` (e.g. `"text"`, `"caption"`). Created via `createDataKey()`.
 - `BatchedOperation`: groups rapid single-character inserts or deletes on the same data key into one logical edit for undo/redo. Lives in `@editorjs/collaboration-manager`.

docs/diagrams/architecture-overview.mmd

@@ -26,7 +26,7 @@ classDiagram
       +block(blockIndex, documentId?)$ BlockIndex
       +text(segments)$ TextIndex
       +data(blockIndex, dataKey)$ DataIndex
-      +tune(blockIndex, tuneName, tuneKey)$ TuneIndex
+      +pluginData(blockIndex, pluginName, pluginKey)$ PluginDataIndex
     }
   }
 

docs/diagrams/events-catalog.mmd

@@ -80,7 +80,7 @@ classDiagram
       detail.data.value: T
       detail.data.previous: T
     }
-    class TuneModifiedEvent {
+    class PluginDataModifiedEvent {
       detail.data.value: T
       detail.data.previous: T
     }
@@ -163,7 +163,7 @@ classDiagram
   DataNodeAddedEvent --|> BaseDocumentEvent
   DataNodeRemovedEvent --|> BaseDocumentEvent
   ValueModifiedEvent --|> BaseDocumentEvent
-  TuneModifiedEvent --|> BaseDocumentEvent
+  PluginDataModifiedEvent --|> BaseDocumentEvent
   PropertyModifiedEvent --|> BaseDocumentEvent
 
   BlockAddedCoreEvent --|> CoreEventBase

docs/diagrams/model-tree-structure.mmd

@@ -38,7 +38,7 @@ classDiagram
   class BlockNode {
     +name: BlockToolName
     +data: BlockNodeData
-    +tunes: Record~BlockTuneName, BlockTune~
+    +plugins: Record~PluginDataName, PluginDataNode~
     +parent: EditorDocument
     +createDataNode(key, data)
     +removeDataNode(key)
@@ -47,9 +47,10 @@ classDiagram
     +getFragments(key, ...): InlineFragment[]
   }
 
-  class BlockTune {
-    +name: BlockTuneName
+  class PluginDataNode {
+    +name: PluginDataName
     +data: Record~string, unknown~
+    +isEmpty: boolean
     +update(key, value)
   }
 
@@ -123,7 +124,7 @@ classDiagram
   EditorJSModel --|> EventBus
   EditorDocument --|> EventBus
   BlockNode --|> EventBus
-  BlockTune --|> EventBus
+  PluginDataNode --|> EventBus
   ValueNode --|> EventBus
   ParentInlineNode --|> EventBus
 
@@ -134,7 +135,7 @@ classDiagram
   EditorDocument "1" *-- "0..*" BlockNode : children
   BlockNode "1" *-- "0..*" TextNode : data[key]
   BlockNode "1" *-- "0..*" ValueNode : data[key]
-  BlockNode "1" *-- "0..*" BlockTune : tunes[name]
+  BlockNode "1" *-- "0..*" PluginDataNode : plugins[name]
 
   %% Inline tree
   TextNode --|> ParentInlineNode

docs/diagrams/plugin-lifecycle-flow.mmd

@@ -31,7 +31,7 @@ sequenceDiagram
   Core->>Plugins: bind PluginType.Plugin = SomePlugin
 
   Dev->>Core: use(SomeTool, settings)
-  Core->>Plugins: bind ToolType.Block / Inline / Tune = [SomeTool, settings]
+  Core->>Plugins: bind ToolType.Block / Inline = [SomeTool, settings]
 
   %% ── await initialize() ───────────────────────────
   Dev->>Core: await initialize()
@@ -47,9 +47,9 @@ sequenceDiagram
   Core->>CollabMgr: new CollaborationManager(config, api, eventBus)
   CollabMgr->>EventBus: wire event listeners
 
-  Core->>Plugins: getAll(ToolType.Block / Inline / Tune)
+  Core->>Plugins: getAll(ToolType.Block / Inline)
   Plugins-->>Core: [[SomeTool, settings], ...]
-  Core->>ToolsManager: prepareTools(blockTools, inlineTools, blockTunes)
+  Core->>ToolsManager: prepareTools(blockTools, inlineTools)
   loop for each tool
     ToolsManager->>Tool: Tool.prepare({ toolName, config })
     ToolsManager->>ToolsManager: wrap in BlockToolFacade or InlineToolFacade

docs/events.md

@@ -4,7 +4,7 @@ The editor exposes two public event transports.
 
 | Transport | Dispatched on | Event types |
 |---|---|---|
-| `EditorJSModel` `EventType.Changed` | `EditorJSModel` instance | `BlockAddedEvent`, `BlockRemovedEvent`, `TextAddedEvent`, `TextRemovedEvent`, `TextFormattedEvent`, `TextUnformattedEvent`, `ValueModifiedEvent`, `TuneModifiedEvent`, `DataNodeAddedEvent`, `DataNodeRemovedEvent`, `PropertyModifiedEvent` |
+| `EditorJSModel` `EventType.Changed` | `EditorJSModel` instance | `BlockAddedEvent`, `BlockRemovedEvent`, `TextAddedEvent`, `TextRemovedEvent`, `TextFormattedEvent`, `TextUnformattedEvent`, `ValueModifiedEvent`, `PluginDataModifiedEvent`, `DataNodeAddedEvent`, `DataNodeRemovedEvent`, `PropertyModifiedEvent` |
 | `EditorJSModel` `EventType.CaretManagerUpdated` | `EditorJSModel` instance | `CaretManagerCaretUpdatedEvent`, `CaretManagerCaretAddedEvent`, `CaretManagerCaretRemovedEvent` |
 | Core `EventBus` (per editor instance) | `EventBus` held in the IoC container | `BlockAddedCoreEvent`, `BlockRemovedCoreEvent`, `ToolLoadedCoreEvent`, `SelectionChangedCoreEvent`, `UndoCoreEvent`, `RedoCoreEvent`, `BeforeInputUIEvent` |
 
@@ -27,7 +27,7 @@ All document mutation events extend `BaseDocumentEvent`:
 | `TextFormattedEvent` | `{ tool, data }` | An inline tool was applied to a text range |
 | `TextUnformattedEvent` | `{ tool, data }` | An inline tool was removed from a text range |
 | `ValueModifiedEvent` | `{ value, previous }` | A `ValueNode`'s value was changed |
-| `TuneModifiedEvent` | `{ value, previous }` | A `BlockTune`'s data was updated |
+| `PluginDataModifiedEvent` | `{ value, previous }` | One key of a plugin's per-block data was updated; `value` is `undefined` when the key was removed |
 | `DataNodeAddedEvent` | `BlockNodeDataSerializedValue` | A data node (text or value) was created on a block |
 | `DataNodeRemovedEvent` | `BlockNodeDataSerializedValue` | A data node was removed from a block |
 | `PropertyModifiedEvent` | `{ value, previous }` | A top-level document property was set |
@@ -47,9 +47,24 @@ Dispatched on the IoC-managed `EventBus` (one instance per editor) with prefixed
 | `UndoCoreEvent` | `core:undo` | — | `DocumentAPI.undo()` or `BlocksUI` (Cmd/Ctrl+Z) |
 | `RedoCoreEvent` | `core:redo` | — | `DocumentAPI.redo()` or `BlocksUI` (Cmd/Ctrl+Shift+Z) |
 | `BeforeInputUIEvent` | `ui:before-input` | `{ data, inputType, targetRanges, isCrossInputSelection, isComposing }` | `BlocksUI` |
+| `BlockSelectedUIEvent` | `ui:blocks:block-selected` | `{ block: HTMLElement, index }` | `BlocksUI`, on pointer enter and on the caret moving into another block |
+| `BlockSettingsOpenUIEvent` | `ui:block-settings:open` | `{ index }` | anyone opening the menu programmatically |
+| `BlockSettingsRenderedUIEvent` | `ui:block-settings:rendered` | `{ button: HTMLElement, blockSettings: HTMLElement }` | `BlockSettingsUI` |
+| `BlockSettingsOpenedUIEvent` | `ui:block-settings:opened` | — | `BlockSettingsUI` |
+| `BlockSettingsClosedUIEvent` | `ui:block-settings:closed` | — | `BlockSettingsUI` |
 
 `BlockAddedCoreEvent` carries the rendered `HTMLElement` in `detail.ui`, while the model-level `BlockAddedEvent` carries serialised data — they are complementary.
 
+`BlockSettingsUI` owns both its menu and the button that opens it, and announces the two
+together so a host can place them: `ToolbarUI` puts the button among its own controls and the
+menu beside the toolbox popover. `ui:block-settings:open` is therefore not how the button works
+— it is the way anything *else* opens the menu, naming the target block by index.
+
+`BlockSelectedUIEvent` is what "the selected block" means to the toolbar and to anything
+mounted in it. It is dispatched for the pointer entering a block *and* for the caret moving
+into one, so a control acting on the selected block still works for someone who never touches
+a mouse. Repeats for the same block are not dispatched.
+
 Use core/UI events for UI workflows and extension coordination.
 
 ## Adapter internals

docs/index-serialization.md

@@ -64,19 +64,19 @@ All fields that can be omitted (`id`) are absent from the JSON when `undefined`
 
 ---
 
-## `TuneIndex` — `k: "tune"`
+## `PluginDataIndex` — `k: "plugin"`
 
 ```json
-{ "k": "tune", "b": 2, "tune": "<tuneName>", "key": "<tuneKey>", "id": "<documentId>" }
+{ "k": "plugin", "b": 2, "plugin": "<pluginName>", "key": "<pluginKey>", "id": "<documentId>" }
 ```
 
-| Field  | Type     | Required |
-|--------|----------|----------|
-| `k`    | `"tune"` | yes |
-| `b`    | number   | yes — zero-based block position |
-| `tune` | string   | yes — block tune name |
-| `key`  | string   | yes — key within the tune |
-| `id`   | string   | no  |
+| Field    | Type       | Required |
+|----------|------------|----------|
+| `k`      | `"plugin"` | yes |
+| `b`      | number     | yes — zero-based block position |
+| `plugin` | string     | yes — name the data is stored under, by convention the plugin's `name` |
+| `key`    | string     | yes — key within that plugin's data |
+| `id`     | string     | no  |
 
 ---
 
@@ -167,13 +167,13 @@ Index.block(2, 'doc-abc').serialize()
 // → '{"k":"block","b":2,"id":"doc-abc"}'
 ```
 
-### Tune property change
+### Plugin data change
 
-A `fontSize` tune on block 1, key `"size"` changed.
+The `fontSize` plugin's `"size"` key changed on block 1.
 
 ```ts
-Index.tune(1, 'fontSize', 'size').serialize()
-// → '{"k":"tune","b":1,"tune":"fontSize","key":"size"}'
+Index.pluginData(1, 'fontSize', 'size').serialize()
+// → '{"k":"plugin","b":1,"plugin":"fontSize","key":"size"}'
 ```
 
 ### Round-trip through `Index.parse`

docs/model.md

@@ -10,7 +10,7 @@ Each `BlockNode` contains keyed data nodes:
 
 - `TextNode`: rich text with inline tree (`FormattingInlineNode` + `TextInlineNode`).
 - `ValueNode<T>`: non-text typed value for tools.
-- `BlockTune`: per-block tune configuration.
+- `PluginDataNode`: per-block data owned by a plugin, keyed by the plugin's `name`.
 
 ## Mutation and event invariant
 
@@ -41,7 +41,7 @@ IndexBase (abstract)
 ├── PropertyIndex   — top-level document property
 ├── BlockIndex      — a single block
 ├── DataIndex       — a data key inside a block
-├── TuneIndex       — a key inside a block tune
+├── PluginDataIndex — a key inside one plugin's per-block data
 └── TextIndex       — character range(s) inside a text node
 ```
 
@@ -68,7 +68,7 @@ Index.document(documentId)
 Index.property(name, documentId?)
 Index.block(blockIndex, documentId?)
 Index.data(blockIndex, dataKey, documentId?)
-Index.tune(blockIndex, tuneName, tuneKey, documentId?)
+Index.pluginData(blockIndex, pluginName, pluginKey, documentId?)
 Index.text(segments)
 Index.parse(serialized)        // deserialize from string
 ```