spine-server-handlers

What problem does it solve?

Developers need a consistent, scalable pattern for adding WebSocket JSON-RPC endpoints to Spine across multiple domains, with standardized validation, error handling, and session context management.

Core Features & Use Cases

• Standardized handler naming and registration for domain operations like serial.bible.character.create and serial.structure.tree.
• Structured request/response schemas and robust error handling using a shared RpcError framework and zod-based validation.
• Session-aware context management to persist and reuse current project/structure state across requests.
• Use Case: rapidly onboard new domain endpoints with predictable behavior and testability.

Quick Start

Implement a new domain endpoint by creating a typed handler with params and results, then register it during server startup.