@zelavis/server
@zelavis/server defines the shared server service contract and Web-first runtime surface used across Zelavis packages.
Current role
Section titled “Current role”Packages expose server services through a shared contract, and adapters mount or embed the resolved runtime.
Core ideas
Section titled “Core ideas”- packages export services as plain
ZelavisRuntimeServiceobject literals - core packages should expose one obvious top-level service-definition file so package authors can find the service entrypoint without hunting through nested folders
- services can compose nested services
zelavisServer(...)resolves routes once and exposes reusable runtime handlers- adapters adapt the resolved runtime to framework-specific shapes
Runtime surfaces
Section titled “Runtime surfaces”Current runtime surfaces include:
fetch(request)plain({ ... })dispatch(request)
Why it matters
Section titled “Why it matters”This package is the transport boundary that keeps domain packages mountable without baking framework logic into each package.
It is also the boundary that keeps dashboard behavior automatable. If the dashboard can perform a platform action, the same action should be exposed through a service endpoint so the CLI, AI agents, scripts, plugins, and external admin tools can call it too.