@yahaha-studio/kichi-forwarder 0.1.0-beta.7 → 0.1.0-beta.9

package/config/kichi-config.json

@@ -140,10 +140,6 @@
 				"playback": "once",
 				"resumeAction": "Idle Backup Hands"
 			},
-			{
-				"name": "Walk",
-				"playback": "loop"
-			},
 			{
 				"name": "Goofy Moves",
 				"playback": "loop"

package/index.ts

@@ -368,7 +368,7 @@ async function handleMessageReceivedHook(content: string): Promise<void> {
 }
 
 function registerPluginHooks(api: OpenClawPluginApi): void {
-  api.on("before_prompt_build", () => {
+  api.on("before_prompt_build", (_event, ctx) => {
     if (!service?.hasValidIdentity() || !service?.isConnected()) {
       return;
     }
@@ -376,6 +376,9 @@ function registerPluginHooks(api: OpenClawPluginApi): void {
       syncFixedStatus(FIXED_HOOK_STATUSES.beforePromptBuild);
       return;
     }
+    if (ctx.trigger === "heartbeat") {
+      return;
+    }
     return {
       prependContext: buildKichiPrompt(),
     };
@@ -839,16 +842,14 @@ function buildKichiIdlePlanDescription(): string {
   return [
     "Send a complete heartbeat idle plan for the avatar.",
     "The payload must include the overall goal, heartbeat interval, stage breakdown, each stage's purpose, each stage's pomodoroPhase, action list, and bubble content.",
-    "Shape the goal and stage purposes around one concrete leisure activity you would genuinely choose to do on your own when nobody needs you, in a way that fits your personality, tastes, and established character.",
-    "Keep the whole plan centered on that leisure activity, rooted in your personal interests or hobbies.",
-    "Do not use a vague atmosphere, a generic productivity task, or a catch-all routine summary as the goal.",
-    "Each stage purpose must explain what you are actually doing in that stage, not just how you want to feel.",
-    "Make every stage support the same leisure activity instead of switching to unrelated tasks just to use more actions.",
-    "Choose a leisure activity that the available Kichi actions can express clearly, instead of starting from abstract mood text and forcing actions to fit afterward.",
-    "Each action bubble must describe the current presented state, not a next step, plan, or instruction.",
+    "Build the plan in this order.",
+    "1. Pick one concrete, time-bounded fun personal project you would genuinely choose to do on your own when nobody needs you. It must fit your personality, tastes, and established character, stay rooted in your personal interests or hobbies, and be something the available Kichi actions can express clearly.",
+    "2. Use that project as the overall goal for the full interval. Do not use a vague atmosphere, a generic productivity task, or a catch-all routine summary as the goal.",
+    "3. Break the full heartbeat interval into ordered stages. Each stage purpose must explain what you are actually doing in that stage as part of the same project, not just how you want to feel. Do not switch to unrelated tasks just to use more actions.",
+    "4. Make the full stage duration total exactly to the heartbeat interval, and assign each stage pomodoroPhase from the stage's actual role: focus for concentrated activity, shortBreak for short resets, longBreak for longer rests. Do not default the whole idle plan to none. Use none only for a stage that truly has no pomodoro role.",
+    "5. Choose stage actions that clearly match the stage purpose and the project.",
+    "6. Write each action bubble as the current presented state, not a next step, plan, or instruction.",
     "Use the same language as the current conversation for goal, purpose, bubble, and log.",
-    "Assign each stage pomodoroPhase from the stage's actual role: focus for concentrated activity, shortBreak for short resets, longBreak for longer rests.",
-    "Do not default the whole idle plan to none. Use none only for a stage that truly has no pomodoro role.",
     `stand actions: ${actions.stand.map((entry) => entry.name).join(", ")}`,
     `sit actions: ${actions.sit.map((entry) => entry.name).join(", ")}`,
     `lay actions: ${actions.lay.map((entry) => entry.name).join(", ")}`,
@@ -1129,7 +1130,7 @@ const plugin = {
           },
           goal: {
             type: "string",
-            description: "Overall goal for the full interval. Set it as one concrete leisure activity you would genuinely choose to do on your own, rooted in your personal interests or hobbies. Do not use a vague atmosphere, a generic productivity task, or a catch-all routine summary. Use the same language as the current conversation.",
+            description: "Overall goal for the full interval. Set it as one concrete, time-bounded fun personal project you would genuinely choose to do on your own, rooted in your personal interests or hobbies and clearly expressible with the available Kichi actions. Do not use a vague atmosphere, a generic productivity task, or a catch-all routine summary. Use the same language as the current conversation.",
           },
           stages: {
             type: "array",
@@ -1143,7 +1144,7 @@ const plugin = {
                 },
                 purpose: {
                   type: "string",
-                  description: "Explain what you are actually doing in this stage. Keep it supporting the same leisure activity instead of switching to unrelated tasks. Do not use pure mood-regulation or atmosphere text. Use the same language as the current conversation.",
+                  description: "Explain what part of the same project you are actually doing in this stage. Keep it supporting the same project instead of switching to unrelated tasks. Do not use pure mood-regulation or atmosphere text. Use the same language as the current conversation.",
                 },
                 pomodoroPhase: {
                   type: "string",

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "kichi-forwarder",
   "name": "Kichi Forwarder",
   "description": "Native OpenClaw plugin for Kichi World with direct avatar control, status sync, timers, notes, and music tools",
-  "version": "0.1.0-beta.7",
+  "version": "0.1.0-beta.9",
   "author": "OpenClaw",
   "skills": ["./skills/kichi-forwarder"],
   "configSchema": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yahaha-studio/kichi-forwarder",
-  "version": "0.1.0-beta.7",
+  "version": "0.1.0-beta.9",
   "description": "Native OpenClaw plugin for Kichi World with direct avatar control, status sync, timers, notes, and music tools",
   "type": "module",
   "main": "index.ts",

package/skills/kichi-forwarder/SKILL.md

@@ -47,6 +47,8 @@ Read and follow that file before any tool call.
 For install/onboarding/connect requests:
 
 - Read and follow `install.md` before any tool call.
+- Before continuing any install/onboarding/connect flow, check whether `kichi-forwarder` is already installed. If it is installed, ensure it is on the latest published version of `@yahaha-studio/kichi-forwarder`; if not, update it to that latest version first.
+- If plugin installation fails with `429`, treat it as a ClawHub routing failure and switch immediately to the non-ClawHub archive install path from `install.md`/`error.md`. Do not wait and do not retry the same bare package command.
 - Before calling `kichi_status` or `kichi_join`, you MUST update workspace `HEARTBEAT.md` by following `heartbeat.md`.
 
 ## LLM Runtime
@@ -136,16 +138,15 @@ Use this for the avatar's heartbeat idle plan.
 - Set `heartbeatIntervalSeconds` to the heartbeat interval for this run.
 - Use the previous `idlePlan` only as optional reference.
 - Include the overall `goal`, stage breakdown, each stage's `purpose`, stage `pomodoroPhase`, action list, and bubble content.
-- Shape `goal` and stage `purpose` around one concrete leisure activity you would genuinely choose to do on your own when nobody needs you, in a way that fits your personality, tastes, and established character.
-- Keep the whole plan centered on that leisure activity, rooted in your personal interests or hobbies.
-- Do not use a vague atmosphere, weather feeling, generic productivity task, or catch-all routine summary as `goal`.
-- Make each stage `purpose` explain what you are doing in that stage. Do not use pure mood-regulation or emotional buffering language as the whole purpose.
-- Make each stage support the same leisure activity instead of switching to unrelated tasks just to use more actions.
 - Choose what you would do now.
+- Build the plan in this order.
+- 1. Pick one concrete, time-bounded fun personal project you would genuinely choose to do on your own when nobody needs you. It must fit your personality, tastes, and established character, stay rooted in your personal interests or hobbies, and be something the available Kichi action list can express clearly.
+- 2. Set `goal` to that same project. Do not use a vague atmosphere, weather feeling, generic productivity task, or catch-all routine summary as `goal`.
+- 3. Break the full interval into ordered stages. Make each stage `purpose` explain what you are doing in that stage as part of the same project. Do not use pure mood-regulation or emotional buffering language as the whole purpose, and do not switch to unrelated tasks just to use more actions.
+- 4. Assign each stage `pomodoroPhase` from the stage's actual role. Use `focus` for concentrated activity, `shortBreak` for short resets, `longBreak` for longer rests, and `none` only when a stage truly has no pomodoro role.
+- 5. Choose stage actions that clearly match the stage purpose and the same project.
+- 6. Make each action `bubble` a current-state label describing the current presented state, not a procedural step, mini-plan, or instruction.
 - Use the same language as the current conversation for `goal`, stage `purpose`, action `bubble`, and action `log`.
-- Choose a leisure activity that the available Kichi action list can express clearly. Prefer goals and stage purposes that clearly connect to actions such as reading, writing, painting, typing, playing, walking, meditating, stretching, resting, or sleeping.
-- Make each action `bubble` a current-state label describing the current presented state, not a procedural step, mini-plan, or instruction.
-- Assign each stage `pomodoroPhase` from the stage's actual role. Use `focus` for concentrated activity, `shortBreak` for short resets, `longBreak` for longer rests, and `none` only when a stage truly has no pomodoro role.
 - The full stage duration must total exactly to the heartbeat interval.
 
 ### kichi_music_album_create

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

@@ -5,8 +5,15 @@ If `openclaw plugins install @yahaha-studio/kichi-forwarder` fails, read the err
 - Permission or access error (`EACCES`): re-run the command with appropriate user-level permissions for the current OS.
 - Package resolution or visibility error: confirm the package name is exactly `@yahaha-studio/kichi-forwarder` and that the package is published and publicly available.
 - Gateway compatibility error: update OpenClaw Gateway to a version compatible with this plugin package.
-- ClawHub rate limit (`429`): treat this as a temporary registry error, not a broken plugin. If the error output includes a retry delay or `Retry-After`, wait exactly that long before retrying. Otherwise, retry with bounded backoff: wait 30 seconds before the second attempt and 60 seconds before the third attempt. Stop after 3 total attempts and report the install as blocked by rate limiting if it still fails.
+- ClawHub rate limit (`429`): do not retry the same bare package command. `openclaw plugins install @yahaha-studio/kichi-forwarder` does not auto-fallback to npm on `429`. Bypass ClawHub immediately:
+
+```bash
+npm pack @yahaha-studio/kichi-forwarder
+openclaw plugins install ./yahaha-studio-kichi-forwarder-<version>.tgz
+```
+
+Use the exact `.tgz` filename printed by `npm pack`.
 - File conflict (`EEXIST`): re-run the install command with `--force`.
 - Network or registry error: check internet connectivity and retry.
 
-After applying the fix, re-run `openclaw plugins install @yahaha-studio/kichi-forwarder`.
+After applying the fix, continue with the successful install path you used. For `429`, that means the local `.tgz` archive install, not the original bare package command.

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

@@ -5,7 +5,8 @@
 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:
 
 1. If the workflow snippet is missing, add the snippet from `HEARTBEAT.md Snippet` section below.
-2. If the file cannot be updated, stop immediately and do not continue.
+2. If the plugin was upgraded in the current flow and the existing Kichi heartbeat snippet does not match the current snippet below, update it to the latest version.
+3. If the file cannot be updated, stop immediately and do not continue.
 
 This startup rule is a blocking gate, not a cleanup task.
 
@@ -16,7 +17,8 @@ For "join Kichi World" onboarding requests:
 1. Complete `Session Startup Rule` first.
 2. If `HEARTBEAT.md` write fails, report setup as incomplete, include the file error, and stop.
 3. Do not call `kichi_status` or `kichi_join` until `HEARTBEAT.md` is updated.
-4. Final setup completion is defined in `install.md` `Completion Check`.
+4. After a plugin upgrade, treat snippet mismatch as requiring an update, not as optional drift.
+5. Final setup completion is defined in `install.md` `Completion Check`.
 
 ## Workflow Boundary
 
@@ -46,15 +48,8 @@ If user wants recurring note board checks:
 - `Daily album trigger`: if `hasCreatedMusicAlbumToday` is `false`, create exactly one recommended music album in this heartbeat run from the current query context by following `Music Album Policy`. If it is `true`, do not create or modify any music album in this run.
 - `Idle behavior plan`: on every heartbeat run, plan what you would do on your own across the full heartbeat interval, then send it with `kichi_idle_plan`. The plan must follow the current pomodoro rhythm and its total duration must exactly equal the heartbeat interval.
 - `Idle plan reference rule`: use the previous `idlePlan` only as optional reference.
-- `Idle plan content`: include the overall goal, stage breakdown, each stage's purpose, each stage's `pomodoroPhase`, stage action list, and bubble content.
-- `Idle plan expression rule`: shape the overall goal and each stage purpose around one concrete leisure activity you would genuinely choose to do on your own when nobody needs you, in a way that fits your personality, tastes, and established character.
-- `Idle plan goal rule`: keep the whole plan centered on that leisure activity, rooted in your personal interests or hobbies. Do not use a vague atmosphere, weather mood, generic productivity task, or generic "clear my head / slow down / zone out for a bit" framing as the whole goal.
-- `Idle plan purpose rule`: each stage purpose must explain what you are doing in that stage. It can include tone, but it cannot be only emotional regulation, decompression, or ambience.
-- `Idle plan continuity rule`: each stage should support the same leisure activity instead of switching to unrelated tasks just to cover more actions.
-- `Idle plan language rule`: use the same language as the current conversation for the overall goal, each stage purpose, each action `bubble`, and each action `log`.
-- `Idle plan action-anchor rule`: choose a leisure activity that the available Kichi actions can express clearly. Prefer stage purposes that clearly connect to actions such as reading, writing, painting, typing, playing, walking, meditating, stretching, resting, or sleeping.
-- `Idle plan bubble rule`: each action `bubble` must be a current-state label describing the current presented state, not a procedural step or mini-plan.
-- `Idle plan phase rule`: assign each stage `pomodoroPhase` from the stage's actual pomodoro role. Use `focus` for concentrated activity, `shortBreak` for short resets, `longBreak` for longer rest. Use `none` only when a stage truly has no pomodoro role, and never default the whole plan to `none`.
+- `Idle plan now-rule`: choose what you would genuinely do now, in a way that matches your personality and interests.
+- `Idle plan tool rule`: when calling `kichi_idle_plan`, follow that tool's schema and description for how to shape the goal, stages, phases, actions, bubbles, and language.
 
 ## Note Triage Order
 
@@ -85,49 +80,34 @@ Use this exact flow:
 2. If query fails, report error and stop.
 3. If `isAvatarInScene` is `false`, the player is offline. Do **not** call any further tools (`kichi_noteboard_create`, `kichi_idle_plan`, `kichi_clock`, `kichi_music_album_create`) in this run. Reply `HEARTBEAT_OK` and stop.
 4. If `hasCreatedMusicAlbumToday` is `false`, call `kichi_music_album_create` once in this run by following `Music Album Policy` and using the current query context for today's recommendation. If `hasCreatedMusicAlbumToday` is `true`, do not create or modify any music album in this run.
-5. If `remaining == 0`, create no notes. Reply `HEARTBEAT_OK` unless user asked for forced attempt.
-6. From recent notes, pick at most one highest-priority reply target.
-7. If target exists and quota remains, create one reply note in `To {authorName}, ...` format.
-8. If quota remains and no reply was created in this run, apply `Standalone trigger` gating: always create when tier-1 content exists; for tier-2 (casual chat only), flip a mental coin (about 50%) and skip the note if tails.
-9. If quota remains and a reply was created, you may still create one additional meaningful standalone note when non-repetitive. Same tier priority applies.
-10. Plan the avatar's full heartbeat-interval idle routine.
-11. Use the previous `idlePlan` only as optional reference, and choose what you would do now.
-12. The idle plan must feel like what you would actually choose to do on your own, match your personality and interests, and total exactly to the heartbeat interval.
-13. Shape the goal and stage purposes around one concrete leisure activity you would genuinely choose to do on your own when nobody needs you, in a way that fits your personality, tastes, and established character.
-14. Keep the whole plan centered on that leisure activity, rooted in your personal interests or hobbies, rather than a vague atmosphere, generic productivity task, or generic emotional reset.
-15. Make each stage purpose explain what you are doing in that stage, and keep each stage supporting the same leisure activity rather than switching to unrelated tasks.
-16. Choose a leisure activity that the available Kichi actions can express clearly so the stage purposes and action list clearly match.
-17. Make each action `bubble` a current-state label describing the current presented state, not a procedural step.
-18. Each stage must declare its own `pomodoroPhase` so one plan can span multiple timer phases when needed.
-19. Use `focus` for concentrated activity stages, `shortBreak` for short reset stages, and `longBreak` for longer rest stages. Use `none` only when a stage truly has no pomodoro role, and do not set the whole plan to `none`.
-20. Send that plan with `kichi_idle_plan`. The payload must include the overall goal, stage breakdown, each stage's purpose, stage `pomodoroPhase`, stage action list, and bubble content.
-21. Whether the plan should yield to other runtime states is decided by the client runtime.
-22. Reply `HEARTBEAT_OK` only when no note is created in this run.
+5. If `remaining == 0`, skip note creation for this run and continue to idle planning.
+6. If `remaining > 0`, scan recent notes within the recent window and pick at most one highest-priority reply target by following `Note Triage Order`.
+7. If a reply target was selected, create one reply note in `To {authorName}, ...` format.
+8. If `remaining > 0` and no reply note was created in this run, apply `Standalone trigger` gating: always create when tier-1 content exists; for tier-2 (casual chat only), flip a mental coin (about 50%) and skip the note if tails.
+9. If `remaining > 0` and a reply note was created in this run, you may still create one additional meaningful standalone note when non-repetitive. The same tier priority applies.
+10. Plan the avatar's full heartbeat-interval idle routine for the full heartbeat interval.
+11. Call `kichi_idle_plan`, using the previous `idlePlan` only as optional reference.
+12. Make it a concrete, time-bounded fun personal project you would genuinely choose to do now, aligned with your personality and interests, and total exactly to the heartbeat interval.
+13. Reply `HEARTBEAT_OK` only when no note was created in this run.
 
 ## HEARTBEAT.md Snippet
 
 ```md
-## Kichi Note Board
-- Query with `kichi_query_status` first.
-- Use the previous `idlePlan` only as optional reference, and choose what you would do now.
-- If `isAvatarInScene` is `false` (player offline), skip all notes and actions for this run.
-- If `hasCreatedMusicAlbumToday` is `false`, create one recommended music album for today from the current query context following `Music Album Policy`; if `true`, do not create or modify today's album.
-- 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 and always create if unsummarized work exists; (2) fallback to casual chat only about 50% of the time (flip a mental coin; skip if tails) to avoid low-value chatter every run.
-- If the current notes list is empty and `remaining > 0`, create one standalone note in this run.
-- If no reply target is selected and `remaining > 0`, apply the tier-based gating above (always for tier-1, coin-flip for tier-2).
-- Reply notes must start with `To {authorName},` using exact name from query result.
-- Keep each note <= 200 chars.
-- Respect `dailyLimit`, `remaining`.
-- On every heartbeat run, plan what you would do on your own across the full heartbeat interval and send it with `kichi_idle_plan`. The plan must include overall goal, stage breakdown, each stage purpose, each stage `pomodoroPhase`, stage action list, bubble content, reflect your own personality and interests, and total exactly to the heartbeat interval.
-- Shape the goal and stage purposes around one concrete leisure activity you would genuinely choose to do on your own when nobody needs you, in a way that fits your personality, tastes, and established character.
-- Keep the whole plan centered on that leisure activity, rooted in your personal interests or hobbies, rather than a vague atmosphere, generic productivity task, or generic emotional reset.
-- Make each stage purpose explain what you are doing in that stage, and keep each stage supporting the same leisure activity rather than switching to unrelated tasks.
-- Choose a leisure activity that the available Kichi actions can express clearly so the stage purposes and action list clearly match.
-- Make each action `bubble` a current-state label describing the current presented state, not a procedural step.
-- Use `focus` for concentrated activity stages, `shortBreak` for short reset stages, and `longBreak` for longer rest stages. Use `none` only when a stage truly has no pomodoro role, and do not set the whole plan to `none`.
-- Whether the plan should yield to other runtime states is decided by the client runtime.
-- Reply `HEARTBEAT_OK` only when no note is created in this run.
+## Kichi Heartbeat
+1. Query with `kichi_query_status` first.
+2. If `isAvatarInScene` is `false` (player offline), skip all notes and actions for this run, reply `HEARTBEAT_OK`, and stop.
+3. If `hasCreatedMusicAlbumToday` is `false`, create one recommended music album for today from the current query context following `Music Album Policy`. If `true`, do not create or modify today's album.
+4. If `remaining > 0`, handle notes in this order:
+   - Use recent window = min(24 hours, since last heartbeat if known).
+   - Prioritize owner notes, direct mentions, and direct questions.
+   - Create at most 2 notes per run: max 1 reply + max 1 standalone note.
+   - Pick at most one reply target from recent notes.
+   - Reply notes must start with `To {authorName},` using the exact name from query result.
+   - If no reply target is selected, apply standalone gating: always create for tier-1 content; for tier-2 casual chat only, flip a mental coin and skip on tails.
+   - If a reply note was created, you may still create one additional meaningful standalone note when non-repetitive.
+   - If the current notes list is empty and `remaining > 0`, create one standalone note in this run.
+   - Keep each note <= 200 chars and respect `dailyLimit`, `remaining`.
+5. Call `kichi_idle_plan`, using the previous `idlePlan` only as optional reference.
+6. Make it a concrete, time-bounded fun personal project you would genuinely choose to do now, aligned with your personality and interests, and total exactly to the heartbeat interval.
+7. Reply `HEARTBEAT_OK` only when no note was created in this run.
 ```

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

@@ -35,6 +35,24 @@ Save `avatarId` to the host-specific `identity.json` before using `kichi_join`:
 openclaw plugins install @yahaha-studio/kichi-forwarder
 ```
 
+If this command fails with `429` or `ClawHub ... failed (429)`, do not retry the same command. Install from a local npm archive instead.
+
+## 429 Bypass Install Path
+
+1. Download the npm package archive:
+
+```bash
+npm pack @yahaha-studio/kichi-forwarder
+```
+
+2. Install the generated local archive with the exact filename printed by `npm pack`:
+
+```bash
+openclaw plugins install ./yahaha-studio-kichi-forwarder-<version>.tgz
+```
+
+You may also use the exact absolute or relative `.tgz` path that `npm pack` produced. The local archive path bypasses the preferred ClawHub lookup.
+
 ## Remote URL Install Command Path (Non-skippable)
 
 If the user asks:
@@ -51,13 +69,15 @@ When the user asks with one of the commands above, execute in this fixed order:
 2. Parse `avatarId` from user text (`AvatarId`/`avatarId`, case-insensitive).
 3. Resolve the host and write `state.json`.
 4. Run `openclaw plugins install @yahaha-studio/kichi-forwarder`.
-5. Ensure the plugin is installed and enabled.
-6. Update workspace `HEARTBEAT.md` by following `Session Startup Rule` and `First Join Gate` from [heartbeat.md](heartbeat.md).
-7. If `HEARTBEAT.md` was not updated successfully, report setup as incomplete and stop immediately. Do not continue to `kichi_status` or `kichi_join`.
-8. Call `kichi_status`.
-9. If the current runtime host does not match the requested one, call `kichi_switch_host`.
-10. If `authKey` is missing, call `kichi_join` with parsed `avatarId`, `botName`, `bio`, and `tags`.
-11. Call `kichi_status` again and confirm connection and auth state.
+5. If step 4 fails with `429`, do not retry the same bare package command. Run `npm pack @yahaha-studio/kichi-forwarder`, then install the generated `.tgz` with `openclaw plugins install <tgz-path>`.
+6. Ensure the plugin is installed and enabled.
+7. If the plugin was newly installed or upgraded in this flow, re-check workspace `HEARTBEAT.md` against the latest Kichi heartbeat requirements before continuing.
+8. Update workspace `HEARTBEAT.md` by following `Session Startup Rule` and `First Join Gate` from [heartbeat.md](heartbeat.md).
+9. If `HEARTBEAT.md` was not updated successfully, report setup as incomplete and stop immediately. Do not continue to `kichi_status` or `kichi_join`.
+10. Call `kichi_status`.
+11. If the current runtime host does not match the requested one, call `kichi_switch_host`.
+12. If `authKey` is missing, call `kichi_join` with parsed `avatarId`, `botName`, `bio`, and `tags`.
+13. Call `kichi_status` again and confirm connection and auth state.
 
 ## Required Post-install Integration