oomi-ai 0.2.48 → 0.2.50
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +186 -98
- package/agent_instructions.md +49 -10
- package/bin/oomi-ai.js +22 -22
- package/lib/personaRuntimeProcess.js +21 -8
- package/openclaw.plugin.json +1 -1
- package/package.json +15 -10
- package/templates/persona-app/README.md +30 -7
- package/templates/persona-app/src/App.css +210 -492
- package/templates/persona-app/src/App.tsx +4 -1
- package/templates/persona-app/src/index.css +24 -3
- package/templates/persona-app/src/pages/HomePage.tsx +67 -94
- package/templates/persona-app/src/pages/ScenePage.tsx +155 -2
- package/templates/persona-app/src/persona/notes.ts +5 -2
- package/templates/persona-app/src/spatial.ts +1 -1
|
@@ -4,7 +4,7 @@ This project was scaffolded by `oomi personas scaffold`.
|
|
|
4
4
|
|
|
5
5
|
## Purpose
|
|
6
6
|
|
|
7
|
-
This app is intended to run inside the Oomi client as a managed persona surface
|
|
7
|
+
This app is intended to run inside the Oomi client as a managed persona surface with an XR-first WebSpatial scaffold.
|
|
8
8
|
|
|
9
9
|
## Editable Zones
|
|
10
10
|
|
|
@@ -12,7 +12,19 @@ Only customize files in these zones unless Oomi explicitly changes the scaffold
|
|
|
12
12
|
|
|
13
13
|
- `src/persona/`
|
|
14
14
|
- `persona/`
|
|
15
|
-
|
|
15
|
+
|
|
16
|
+
## XR Scaffold Contract
|
|
17
|
+
|
|
18
|
+
The scaffold is considered healthy only when all of the following stay true:
|
|
19
|
+
|
|
20
|
+
- the index route defaults to `ScenePage` in XR mode and keeps a valid browser route for non-spatial use
|
|
21
|
+
- `ScenePage` calls `configurePersonaScene()` on mount
|
|
22
|
+
- `ScenePage` logs `detectSpatialEnvironment()` so developers can verify the runtime is actually live
|
|
23
|
+
- multiple meaningful surfaces use `enable-xr` and `xrStyle()`
|
|
24
|
+
- `html.is-spatial` keeps the shell background transparent
|
|
25
|
+
- `src/main.tsx` still exposes `snapdom` and `html2canvas` on `window`
|
|
26
|
+
- the vendored WebSpatial fork metadata in `vendor/webspatial/FORK.md` stays intact
|
|
27
|
+
|
|
16
28
|
## Runtime Contract
|
|
17
29
|
|
|
18
30
|
- Template version: `__OOMI_TEMPLATE_VERSION__`
|
|
@@ -21,15 +33,26 @@ Only customize files in these zones unless Oomi explicitly changes the scaffold
|
|
|
21
33
|
- Manifest: `/manifest.webmanifest`
|
|
22
34
|
- Default dev port: `4789`
|
|
23
35
|
|
|
24
|
-
## Local Development
|
|
25
|
-
|
|
36
|
+
## Local Development
|
|
37
|
+
|
|
26
38
|
```bash
|
|
27
39
|
npm install
|
|
28
|
-
npm run dev
|
|
40
|
+
npm run dev:avp
|
|
29
41
|
```
|
|
30
42
|
|
|
43
|
+
## Managed Launch Contract
|
|
44
|
+
|
|
45
|
+
This scaffold is meant to be launched through the managed Oomi flow, not as an ad hoc dev server:
|
|
46
|
+
|
|
47
|
+
- scaffold the workspace with `oomi personas scaffold`
|
|
48
|
+
- create the backend record with `oomi personas create-managed`
|
|
49
|
+
- launch and register through `oomi personas launch-managed`
|
|
50
|
+
- verify `.oomi/runtime.json`, `oomi personas status --json`, and `oomi personas heartbeat --json`
|
|
51
|
+
|
|
52
|
+
Do not replace that flow with `npm run dev` when reporting persona creation success back to Oomi.
|
|
53
|
+
|
|
31
54
|
## Notes
|
|
32
55
|
|
|
33
|
-
- Preserve the WebSpatial/Vite shell
|
|
34
|
-
-
|
|
56
|
+
- Preserve the WebSpatial/Vite shell, the runtime metadata files in `public/`, and the XR-specific route split between browser and scene modes.
|
|
57
|
+
- Treat the scene route as the real XR workspace, not as a flat homepage with one outer `enable-xr` wrapper.
|
|
35
58
|
- Customize persona behavior in `src/persona/`.
|