admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
npc0-hue
2026-07-11 14:56:10 +08:00
commit 7e05d0a4e7
660 changed files with 78119 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/docs/local-development.md
+24
View File
@@ -0,0 +1,24 @@
# Local Plugin Development
Local development must exercise the same platform-mediated flows used by installed plugins.
## Flow
1. Validate the plugin manifest with `npm run validate:manifest`.
2. Register the validated manifest with platform `POST /api/v1/game-plugins/register-manifest` using a manifest artifact reference and the manifest payload.
3. Serve plugin page from a local dev server or static directory.
4. Select a test server instance and run endpoint.
5. Use platform bridge calls for jobs, logs, files, artifacts, and AI.
Plugins must not bypass platform authorization by calling run directly.
Manifest validation rejects raw host paths, raw credentials, direct run sockets, and raw AI/provider keys. Platform registration repeats the same safety class of validation before storing registry metadata, so a plugin workspace validation result is not treated as a trusted backend bypass.
For full local stack proof, run the repository local debug workspace:
```bash
scripts/local-debug-start.sh
scripts/local-debug-smoke.sh
```
That workflow registers `plugins/examples/dev-game-plugin/manifest.json`, creates a safe `server-local-debug` fixture through platform APIs, and verifies that plugin/browser evidence exposes only logical IDs, platform routes, job refs, log refs, artifact refs, and safe metadata.