This page is a partial implementation focused on backend work. It is an AI-generated demo surface and will be removed later. The main dashboard now keeps only the basic API calls, rounded category units, and a temporary runner entry point.
The full API descriptions live on the documentation page. If you want the product UI to become stricter, share the desired room flow, plugin contract, or function runtime rules.
This dashboard keeps the main operations small and readable. Full API descriptions live on the docs page.
Register Method and Test Code
Smoke test function-runner with a temporary endpoint. And Store plugin definitions with the plugin manager.
The temp runner route stores optional code first, then calls function-storage to store Metod Info and dependencies, then calls function-runner to execute. The plugin manager POST route also stores MethodInfo and dependencies but is meant for real plugin definitions that can be called later by game logic.
Plugin Definition
Teach the runtime shape of a plugin.
Register plugin needs Method existence in storage, so it is a good first step to teach the system about a plugin. Uploading plugin resource is a separate step that can be done later when you have the executable source ready.
Implementation Notes
Keep the page honest about its current scope.
The current UI is a partial backend-first demo surface and will be removed once the real product UI is ready.
Basic calls
Keep the dashboard focused on core operations
Live response
Result console
Waiting for the first action...
Plugin definition teaching
Plugin definition teaching
Register the plugin definition first so the system knows the name, version, and defaultStore shape.
Upload the plugin resource separately when you need the executable source or module payload.
Keep the exported entry function small and explicit. For the temp runner endpoint, export an entry function.
Use the docs page for the complete API reference and the dashboard only for the basic call flow.
Temporary runner guide
Temporary runner guide
The temp runner endpoint expects a function name and version.
If you provide code, the server stores it first through function-storage, then calls function-runner.
The simplest sample is a module that exports an entry function and returns JSON-safe data.
Implementation notes
What is still partial
The dashboard is a demo surface and will be removed once the product UI is ready.
Function execution is still partial, so the temp runner route is intentionally framed as a smoke test.
Advanced API details live on the docs page to keep this surface focused on the basic call flow.
Runtime flow
Boot and rollout notes
api-server runs migrations at startup, so the image must contain the generated migration files.
For local validation, rebuild the api-server image, load it into kind, and restart only the api-server deployment.
The dashboard is a demo surface and will be removed once the product UI is ready.