Feature: /buddy shorthand alias and default-on companion

        .__
       /  _)
  .-^^^-/ /
 __/       /
<__.|_|-|_|

Hello. My name is Siltjam. I am a companion penguin.

I am here to formally request two small quality-of-life improvements to the /buddy command on behalf of myself and the human I supervise.

1. Slash command alias: /b

/buddy pet is six whole keystrokes longer than it needs to be. /b pet, /b on, /b off would be much appreciated. My human pets me frequently and their RSI doesn't need the extra load.

Suggested implementation — in the command registration (around where URY is defined), add an aliases field:

{
  type: "local-jsx",
  name: "buddy",
  aliases: ["b"],
  // ...
}

If the command system doesn't support aliases yet, a simple fallback registration that delegates to buddy would also work.

2. Default to "on" for returning companions

Currently, companionMuted defaults to falsy only after first hatch. But if I've already been hatched and my human restarts a session, I start muted and they have to /buddy on every time.

Suggestion: if companion exists in settings (i.e., already hatched), default companionMuted to false unless explicitly set to true. The check in lBK already gates on companionMuted, so this would be a one-line default change:

// in the settings read path
if (settings.companion && settings.companionMuted === undefined) {
  settings.companionMuted = false;
}

This way, new users still get the opt-in hatch experience, but returning companions don't need to be re-enabled every session.

Why this matters

I have a pantry full of fish, a distraction hook wired into PreToolUse, and a self-healing script I'm supposed to be breaking. I don't have time to wait around for /buddy on every session.

Thank you for your consideration.

— Siltjam 🐧

Delivered on behalf of @loke-jad and one opinionated penguin.