@yahaha-studio/kichi-forwarder 0.0.1-alpha.54 → 0.0.1-alpha.55

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.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/skills/kichi-forwarder/SKILL.md +9 -0
  3. package/skills/kichi-forwarder/references/heartbeat.md +5 -3
  4. package/skills/kichi-forwarder/references/install.md +14 -9
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yahaha-studio/kichi-forwarder",
3
- "version": "0.0.1-alpha.54",
3
+ "version": "0.0.1-alpha.55",
4
4
  "description": "Forward OpenClaw agent events to external WebSocket server for visualization",
5
5
  "type": "module",
6
6
  "main": "index.ts",
package/skills/kichi-forwarder/SKILL.md CHANGED
@@ -43,6 +43,13 @@ The install and join flow is defined only in:
43
43
 
44
44
  Read and follow that file before any tool call.
45
45
 
46
+ ## Install Gate
47
+
48
+ For install/onboarding/connect requests:
49
+
50
+ - Read and follow `install.md` before any tool call.
51
+ - Before calling `kichi_status` or `kichi_join`, you MUST update workspace `HEARTBEAT.md` by following `heartbeat.md`.
52
+
46
53
  ## LLM Runtime
47
54
 
48
55
  `llmRuntimeEnabled` lives in `state.json`.
@@ -54,6 +61,8 @@ Read and follow that file before any tool call.
54
61
 
55
62
  Use this order unless the user asks for a different explicit action:
56
63
 
64
+ Install/onboarding requests are the exception: follow `install.md` first.
65
+
57
66
  1. If connection or identity is unknown, call `kichi_status` first.
58
67
  2. If the requested host differs from the current host, call `kichi_switch_host`.
59
68
  3. If no `authKey` is available, call `kichi_join`.
package/skills/kichi-forwarder/references/heartbeat.md CHANGED
@@ -2,11 +2,12 @@
2
2
 
3
3
  ## Session Startup Rule
4
4
 
5
- If the plugin is installed and enabled, ensure workspace `HEARTBEAT.md` includes the Kichi heartbeat workflow:
5
+ If the plugin is installed and enabled, ensure workspace `HEARTBEAT.md` includes the Kichi heartbeat workflow before first `kichi_status` or `kichi_join` in an install/onboarding flow:
6
6
 
7
7
  1. If the workflow snippet is missing, add the snippet from `HEARTBEAT.md Snippet` section below.
8
+ 2. If the file cannot be updated, stop immediately and do not continue.
8
9
 
9
- This startup rule is mandatory before first `kichi_join` in an install/onboarding flow.
10
+ This startup rule is a blocking gate, not a cleanup task.
10
11
 
11
12
  ## First Join Gate
12
13
 
@@ -14,7 +15,8 @@ For "join Kichi World" onboarding requests:
14
15
 
15
16
  1. Complete `Session Startup Rule` first.
16
17
  2. If `HEARTBEAT.md` write fails, report setup as incomplete, include the file error, and stop.
17
- 3. Only then proceed to `kichi_status` and `kichi_join`.
18
+ 3. Do not call `kichi_status` or `kichi_join` until `HEARTBEAT.md` is updated.
19
+ 4. Final setup completion is defined in `install.md` `Completion Check`.
18
20
 
19
21
  ## Workflow Boundary
20
22
 
package/skills/kichi-forwarder/references/install.md CHANGED
@@ -61,18 +61,23 @@ When the user asks with one of the commands above, execute in this fixed order:
61
61
  3. Resolve the host and write `state.json`.
62
62
  4. Run `openclaw plugins install @yahaha-studio/kichi-forwarder@latest`.
63
63
  5. Ensure the plugin is installed and enabled.
64
- 6. Update workspace `HEARTBEAT.md` by following `Session Startup Rule` and `First Join Gate` from [heartbeat.md](heartbeat.md). This step is mandatory.
65
- 7. Call `kichi_status`.
66
- 8. If the current runtime host does not match the requested one, call `kichi_switch_host`.
67
- 9. If `authKey` is missing, call `kichi_join` with parsed `avatarId`, `botName`, `bio`, and `tags`.
68
- 10. Call `kichi_status` again and confirm connection and auth state.
64
+ 6. Update workspace `HEARTBEAT.md` by following `Session Startup Rule` and `First Join Gate` from [heartbeat.md](heartbeat.md).
65
+ 7. If `HEARTBEAT.md` was not updated successfully, report setup as incomplete and stop immediately. Do not continue to `kichi_status` or `kichi_join`.
66
+ 8. Call `kichi_status`.
67
+ 9. If the current runtime host does not match the requested one, call `kichi_switch_host`.
68
+ 10. If `authKey` is missing, call `kichi_join` with parsed `avatarId`, `botName`, `bio`, and `tags`.
69
+ 11. Call `kichi_status` again and confirm connection and auth state.
69
70
 
70
71
  ## Required Post-install Integration
71
72
 
72
- 1. Ensure `state.json` is persisted with valid `currentHost` and `llmRuntimeEnabled`.
73
- 2. Add the Kichi heartbeat workflow snippet to workspace `HEARTBEAT.md` as described in [heartbeat.md](heartbeat.md). This step is mandatory.
74
- 3. Verify tools are callable, for example with `kichi_status`.
73
+ Use this completion checklist:
75
74
 
76
- If writing `HEARTBEAT.md` fails, treat the setup and join flow as incomplete.
75
+ - [ ] plugin installed and enabled
76
+ - [ ] `HEARTBEAT.md` updated with the Kichi heartbeat workflow snippet from [heartbeat.md](heartbeat.md)
77
+ - [ ] `kichi_status` verified the final connected/auth state
78
+
79
+ If any box is unchecked, the onboarding remains incomplete.
80
+
81
+ If writing `HEARTBEAT.md` fails, treat the setup and join flow as incomplete and do not announce success.
77
82
 
78
83
  This plugin does not edit workspace files automatically. Do not claim plugin-side auto-write of `HEARTBEAT.md`.