chore(openspec): archive add-plugin-public-api

Folds the change's delta specs into openspec/specs/ (+11 added, ~4 modified) and
moves it to changes/archive/2026-08-26-add-plugin-public-api/.

Two corrections were needed first, both surfaced by the merge of main:

- The keyboard-shortcuts delta was filed under `core`, but #180 extracted that
  requirement into its own `shortcuts-plugin` capability. The fold matches
  requirements by header text within the target capability, so archiving as-is
  would have silently appended a duplicate to core/spec.md instead of updating
  the intended requirement.
- As a MODIFIED block the delta replaces the whole requirement, and it carried
  only 3 of the 7 existing scenarios — dropping the IME, first-match, IndexError,
  destroy and non-string-shortcut cases, all still true and still tested.

The capability's Purpose is updated in this commit rather than left to the fold,
which rewrites requirement blocks only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: gohabereg

…ges/add-plugin-public-api/.openspec.yaml …-26-add-plugin-public-api/.openspec.yamlopenspec/changes/add-plugin-public-api/.openspec.yaml renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/.openspec.yaml openspec/changes/add-plugin-public-api/.openspec.yaml renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/.openspec.yaml

@@ -23,11 +23,12 @@ Plugins registered through `core.use()` are currently write-only participants: t
 ### Modified Capabilities
 - `sdk`: the plugin contract requirement changes — `EditorjsPluginConstructor` gains the static `name`, `EditorjsPlugin` gains the optional public-API declaration, `EditorAPI` gains the `plugins` namespace, and `BaseToolOptions` gains the `plugins` key.
 - `ui`: the blocks-holder requirement changes — `BlocksUI` delegates `keydown` as a `KeydownUIEvent` and yields to plugins that claim a key before applying its own undo/redo handling.
-- `core`: the keyboard-shortcuts requirement changes — `ShortcutsPlugin` sources shortcuts from `options.plugins.shortcuts` rather than `options.shortcut`, and exposes a runtime registration API. `Core` additionally builds and owns the plugin registry that backs `api.plugins`.
+- `core`: `Core` builds and owns the plugin registry that backs `api.plugins`.
+- `shortcuts-plugin`: the keyboard-shortcuts requirement changes — `ShortcutsPlugin` sources shortcuts from `options.plugins.shortcuts` rather than `options.shortcut`, and exposes a runtime registration API. The capability's `## Purpose` paragraph is updated in this change directly, since the mechanical fold rewrites requirement blocks only and leaves surrounding prose untouched.
 
 ## Impact
 
-- **Code**: `packages/sdk/src/entities/EditorjsPlugin.ts`, `BaseTool.ts`, `packages/sdk/src/api/EditorAPI.ts` (new `PluginsAPI.ts`), `packages/sdk/src/tools/facades/BaseToolFacade.ts`; `packages/core/src/index.ts` (plugin instantiation + registry), `packages/core/src/api/` (new `PluginsAPI`), `packages/core/src/plugins/ShortcutsPlugin.ts`; `packages/tools/{bold,italic,inline-link}`; `packages/plugins/clipboard-plugin` and `packages/dom-adapters` gain a `name`; `packages/ui/src/Blocks/Blocks.ts` gains the `KeydownUIEvent` dispatch.
+- **Code**: `packages/sdk/src/entities/EditorjsPlugin.ts`, `BaseTool.ts`, `packages/sdk/src/api/EditorAPI.ts` (new `PluginsAPI.ts`), `packages/sdk/src/tools/facades/BaseToolFacade.ts`; `packages/core/src/index.ts` (plugin instantiation + registry), `packages/core/src/api/` (new `PluginsAPI`), `packages/plugins/shortcuts-plugin/src/index.ts`; `packages/tools/{bold,italic,inline-link}`; `packages/plugins/clipboard-plugin` and `packages/dom-adapters` gain a `name`; `packages/ui/src/Blocks/Blocks.ts` gains the `KeydownUIEvent` dispatch.
 - **APIs**: additive for `EditorAPI`; breaking for plugin constructors (static `name`) and for tools declaring a flat `shortcut`.
 - **Ordering**: plugin instantiation currently happens before tools are prepared, and plugins receive the `EditorAPI` in their constructor — the registry must therefore be populated lazily enough that a plugin constructed first can still reach a plugin constructed later. Addressed in design.md.
 - **Docs**: `docs/plugins.md` (Registration, EditorAPI, Lifecycle sections) is superseded in part and must be updated; `docs/diagrams/plugin-lifecycle-flow.mmd` gains the registry step.

…/changes/add-plugin-public-api/design.md …26-08-26-add-plugin-public-api/design.mdopenspec/changes/add-plugin-public-api/design.md renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/design.md openspec/changes/add-plugin-public-api/design.md renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/design.md

@@ -1,25 +1,3 @@
-## MODIFIED Requirements
-
-### Requirement: Keyboard shortcuts plugin
-The system SHALL provide a `ShortcutsPlugin` (an `EditorjsPlugin` with `name` `shortcuts`) that maps keyboard shortcuts declared in a tool's `options.plugins.shortcuts` to inline-tool application through the `EditorAPI`, and that exposes a public API for registering and unregistering shortcuts at runtime.
-
-#### Scenario: Triggering an inline tool via shortcut
-- **GIVEN** an inline tool is registered with `options.plugins.shortcuts.shortcut` set to a key combination (e.g. `CMD+B`)
-- **WHEN** that key combination is pressed while the editor has focus
-- **THEN** `ShortcutsPlugin` applies the corresponding inline tool to the current selection via the `EditorAPI`
-
-#### Scenario: Legacy flat shortcut key is ignored
-- **GIVEN** a tool declares a flat `options.shortcut` and no `options.plugins.shortcuts`
-- **WHEN** that key combination is pressed
-- **THEN** no inline tool is applied, since shortcuts are sourced only from the namespaced key
-
-#### Scenario: Registering a shortcut at runtime
-- **GIVEN** an integrator holds `api.plugins.shortcuts`
-- **WHEN** a shortcut and handler are registered through that public API
-- **THEN** pressing the shortcut invokes the handler, and unregistering it through the same API stops further invocations
-
-Implemented in `src/plugins/ShortcutsPlugin.ts`.
-
 ## ADDED Requirements
 
 ### Requirement: Plugin registry

…hanges/add-plugin-public-api/proposal.md …-08-26-add-plugin-public-api/proposal.mdopenspec/changes/add-plugin-public-api/proposal.md renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/proposal.md openspec/changes/add-plugin-public-api/proposal.md renamed to openspec/changes/archive/2026-08-26-add-plugin-public-api/proposal.md

@@ -0,0 +1,53 @@
+## MODIFIED Requirements
+
+### Requirement: Keyboard shortcuts plugin
+The system SHALL provide a `ShortcutsPlugin` (an `EditorjsPlugin` with `name` `shortcuts`) that, on construction, subscribes to the `core:tool:loaded` and `ui:key-down` events, registers the string `shortcut` each loaded tool addresses to it under `options.plugins.shortcuts`, applies the matching inline tool to the current selection via the `EditorAPI` when its shortcut is pressed, and exposes a public API for registering and unregistering shortcuts at runtime. Tool-declared and API-registered shortcuts SHALL share one table, so a shortcut always resolves to exactly one handler.
+
+#### Scenario: Registering a shortcut from a loaded tool
+- **GIVEN** a tool is loaded whose `options.plugins.shortcuts.shortcut` is a string (e.g. `CMD+B`)
+- **WHEN** the `core:tool:loaded` event fires
+- **THEN** the plugin registers a handler for that shortcut string which applies the tool
+
+#### Scenario: Ignoring tools without a string shortcut
+- **GIVEN** a tool is loaded that addresses no slice to the `shortcuts` plugin, or whose `options.plugins.shortcuts.shortcut` is absent or is not a string
+- **WHEN** the `core:tool:loaded` event fires
+- **THEN** the plugin registers no shortcut for that tool
+
+#### Scenario: Legacy flat shortcut key is ignored
+- **GIVEN** a tool declares a flat `options.shortcut` and no `options.plugins.shortcuts`
+- **WHEN** that key combination is pressed
+- **THEN** no inline tool is applied, since shortcuts are sourced only from the namespaced key
+
+#### Scenario: Triggering an inline tool via shortcut
+- **GIVEN** an inline tool is registered with `options.plugins.shortcuts.shortcut` set to a key combination (e.g. `CMD+B`)
+- **WHEN** that key combination is pressed while the editor has focus
+- **THEN** the plugin prevents the native event's default action and applies the corresponding inline tool to the current selection via `api.selection.applyInlineTool`
+
+#### Scenario: Registering a shortcut at runtime
+- **GIVEN** an integrator holds `api.plugins.shortcuts`
+- **WHEN** a shortcut and handler are registered through that public API
+- **THEN** pressing the shortcut invokes the handler, and unregistering it through the same API stops further invocations
+
+#### Scenario: Matching only the first registered shortcut
+- **GIVEN** more than one registered shortcut would match the keydown
+- **WHEN** the `ui:key-down` event fires
+- **THEN** the plugin applies only the first matching tool and stops
+
+#### Scenario: Ignoring keydown during IME composition
+- **GIVEN** the native keydown event has `isComposing === true`
+- **WHEN** the `ui:key-down` event fires
+- **THEN** the plugin performs no matching and leaves the native event untouched
+
+#### Scenario: Tolerating a missing caret when applying a tool
+- **GIVEN** applying the inline tool throws an `IndexError` (e.g. no caret in a text input)
+- **WHEN** a matching shortcut is dispatched
+- **THEN** the plugin swallows the error and leaves the editor unchanged, while any other error propagates
+
+#### Scenario: Releasing shortcuts on destroy
+- **GIVEN** a `ShortcutsPlugin` instance has registered shortcuts
+- **WHEN** `destroy()` is called
+- **THEN** it clears the registered shortcuts so subsequent keydowns dispatch nothing
+
+Shortcuts for block tools and block tunes (a `shortcuts` map under `options.plugins.shortcuts`) are reserved for future work and not yet implemented.
+
+Implemented in `src/index.ts`, validated by its co-located `.spec.ts`.