[Phase 3] Implement the JavaScript action registry and applicability engine #18

New issue

Closed

opened 2026-07-25 21:54:28 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:54:28 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #7, #14, #17

Scope

Define action identity, version, label, description, accepted selection shapes, parameter schema, required capabilities, result contract, and implementation adapter.
Register, list, find, enable, disable, and rank actions.
Compute applicable actions from selected node/edge types and current capabilities.
Expose the same registry to context menus, command palette, and programmatic invocation.

Acceptance criteria

Applicable, disabled, and hidden actions are distinguishable with reasons.
Selection values contain stable graph-domain data, never Cytoscape objects.
Duplicate action IDs or incompatible versions are rejected.
Registry behavior is deterministic and unit tested.
The core editor remains useful with an empty registry.

Parent: #2 Depends on: #7, #14, #17 ## Scope - Define action identity, version, label, description, accepted selection shapes, parameter schema, required capabilities, result contract, and implementation adapter. - Register, list, find, enable, disable, and rank actions. - Compute applicable actions from selected node/edge types and current capabilities. - Expose the same registry to context menus, command palette, and programmatic invocation. ## Acceptance criteria - Applicable, disabled, and hidden actions are distinguishable with reasons. - Selection values contain stable graph-domain data, never Cytoscape objects. - Duplicate action IDs or incompatible versions are rejected. - Registry behavior is deterministic and unit tested. - The core editor remains useful with an empty registry.