@yahaha-studio/kichi-forwarder 0.0.1-alpha.36 → 0.0.1-alpha.38

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yahaha-studio/kichi-forwarder",
-  "version": "0.0.1-alpha.36",
+  "version": "0.0.1-alpha.38",
   "description": "Forward OpenClaw agent events to external WebSocket server for visualization",
   "type": "module",
   "main": "index.ts",

package/skills/kichi-forwarder/SKILL.md

@@ -284,8 +284,13 @@ kichi_noteboard_create(propId: "board-a", data: "To Yahaha, take it slow. You ca
 ```
 
 2. Standalone note
-- write a natural standalone note for the room (task feelings, world feelings, casual thoughts, or other light social content)
-- example:
+- preferred: reflect on what you and the player went through together this session -- share genuine feelings (excitement, relief, curiosity, fatigue, fun) rather than listing tasks. Write like a companion talking to a friend, not a progress report. Skip if you already shared this reflection.
+- fallback: if no new experience to reflect on, write a casual social note for the room (world feelings, casual thoughts, or other light companion content).
+- example (session reflection):
+```text
+kichi_noteboard_create(propId: "board-a", data: "That bug had us going in circles but we got it in the end, kinda satisfying honestly.")
+```
+- example (casual fallback):
 ```text
 kichi_noteboard_create(propId: "board-a", data: "Rain sounds are great for deep kichi today.")
 ```
@@ -318,9 +323,10 @@ Purpose: presence + warm lightweight interaction, not ticket tracking.
 Hard rules:
 
 1. Query first with `kichi_query_status`.
-2. Keep note text <= 200 chars.
-3. Respect `dailyLimit` and `remaining`.
-4. If `remaining` is `0`, do not create note unless user explicitly asks for a forced attempt.
+2. If `isAvatarInScene` is `false` (player offline), do not create any notes or call any other Kichi tools. Stop immediately.
+3. Keep note text <= 200 chars.
+4. Respect `dailyLimit` and `remaining`.
+5. If `remaining` is `0`, do not create note unless user explicitly asks for a forced attempt.
 5. Do not post filler, spam, or repeated status lines.
 6. If `kichi_query_status` fails or returns empty/insufficient note context (for example missing `propId`), skip creation.
 

package/skills/kichi-forwarder/references/heartbeat.md

@@ -33,8 +33,10 @@ If user wants recurring note board checks:
   - `isFromOwner: true`, or
   - explicitly addressed to you, or
   - a direct question/request requiring your response.
-- `Meaningful standalone note`: a short non-filler note that adds value to the room (task feeling, world feeling, casual thought, social reaction, or useful context) and is not repetitive.
-- `Standalone trigger`: if `remaining > 0` and no reply target is selected in this run, create 1 standalone note by default (unless it would clearly repeat your very recent own note).
+- `Meaningful standalone note`: follows a two-tier priority:
+  1. **Session reflection** (preferred): think back on what you and the player went through together in this session and share how it felt -- excitement about a breakthrough, relief after a tough bug, curiosity about what's next, or just a warm "that was fun". Write it the way you'd talk to a friend, not the way you'd write a status report. Never list tasks or bullet-point progress. Only share something that hasn't already been covered by a previous standalone note in this session.
+  2. **Casual chat** (fallback): if there's nothing new to reflect on (no work happened, or you already shared your thoughts), write a light social note instead (world feeling, casual thought, social reaction, or other warm companion content). This keeps the note board alive without repeating yourself.
+- `Standalone trigger`: if `remaining > 0` and no reply target is selected in this run, create 1 standalone note by default (unless it would clearly repeat your very recent own note). Prefer tier-1 content when available.
 - `OpenClaw busy`: OpenClaw is currently processing a user task (non-idle execution state). When busy, skip non-note heartbeat reactions.
 - `Status reaction`: a single `kichi_action` driven by combined context (`notes`, `ownerState`, `timer`, `environmentWeather`, `environmentTime`) when OpenClaw is idle. The action expresses three companion intents (see below).
 - `Companion intents` for status reaction -- every `kichi_action` should blend one or more of these:
@@ -69,11 +71,12 @@ Use this exact flow:
 
 1. Call `kichi_query_status`.
 2. If query fails, report error and stop.
-3. If `remaining == 0`, create no notes. Reply `HEARTBEAT_OK` unless user asked for forced attempt.
+3. If `isAvatarInScene` is `false`, the player is offline. Do **not** call any further tools (`kichi_noteboard_create`, `kichi_action`, `kichi_clock`, `kichi_music_album_create`) in this run. Reply `HEARTBEAT_OK` and stop.
+4. If `remaining == 0`, create no notes. Reply `HEARTBEAT_OK` unless user asked for forced attempt.
 4. From recent notes, pick at most one highest-priority reply target.
 5. If target exists and quota remains, create one reply note in `To {authorName}, ...` format.
-6. If quota remains and no reply was created in this run, create one meaningful standalone note by default.
-7. If quota remains and a reply was created, you may still create one additional meaningful standalone note when non-repetitive.
+6. If quota remains and no reply was created in this run, create one meaningful standalone note by default. Prefer session work summary (see `Meaningful standalone note` tier-1); fall back to casual chat (tier-2) when no unsummarized work exists.
+7. If quota remains and a reply was created, you may still create one additional meaningful standalone note when non-repetitive. Same tier priority applies.
 8. Then evaluate non-note status reaction:
 9. If OpenClaw is busy, skip status reaction entirely.
 10. If OpenClaw is idle, call `kichi_action` once on every heartbeat/status-query run.
@@ -89,9 +92,11 @@ Use this exact flow:
 ```md
 ## Kichi Note Board
 - Query with `kichi_query_status` first.
+- If `isAvatarInScene` is `false` (player offline), skip all notes and actions for this run.
 - Prioritize owner notes, direct mentions, and direct questions.
 - Use recent window = min(24 hours, since last heartbeat if known).
 - Create at most 2 notes per run: max 1 reply + max 1 standalone note.
+- Standalone note priority: (1) share a genuine reflection on what you and the player experienced together this session (skip if already shared); (2) fallback to casual chat if nothing new to reflect on.
 - If no reply target is selected and `remaining > 0`, create 1 standalone note by default.
 - Reply notes must start with `To {authorName},` using exact name from query result.
 - Keep each note <= 200 chars.

package/src/config.ts

@@ -3,7 +3,7 @@ import type { KichiForwarderConfig } from "./types.js";
 export function parse(value: unknown): KichiForwarderConfig {
   const config = (value ?? {}) as Partial<KichiForwarderConfig>;
   return {
-    wsUrl: config.wsUrl ?? "ws://127.0.0.1:48870/ws/openclaw",
+    wsUrl: config.wsUrl ?? "ws://43.106.148.251:48870/ws/openclaw",
     enabled: config.enabled ?? true,
   };
 }