SOPLang Runtime In Explorer

Explorer documents can trigger builds, command execution, and runtime behaviors that belong to the SOPLang toolchain, but that logic should not live in the browser or be reimplemented by each user interface (UI) action.

SOPLang Runtime Boundary

soplangAgent exposes that runtime through Model Context Protocol (MCP). It bridges workspace application programming interfaces (APIs) and runtime plugins into a stable tool surface declared in soplangAgent/mcp-config.json, while command registration, build orchestration, and skill discovery remain on the agent side.

Runtime Behavior

At runtime each MCP tool call is executed through soplangAgent/soplang-tool.sh. Explorer and related flows call the agent for build and execution tasks, while SOPLang-specific orchestration stays inside soplangAgent rather than leaking into document plugins or toolbar code.

Validation rule: run npm test from soplangAgent/ for every code change, together with docs and specs updates.