chore(deps): move from buddy-bot to @buddysh/buddy

buddy-bot was renamed to @buddysh/buddy. This repo was still calling the old name, which is frozen at 0.10.5 (2026-08-19, the final pre-rename build) and carries no deprecation notice — so it looks current while receiving nothing.

That is why #1168 arrived with a corrupted deps.yaml: the fix for it (stacksjs/buddy#1453) shipped in 0.11.2, under the new name only.

Three things had to move together

Switching the bunx calls alone would have looked fine and quietly regressed:

1. The nine bunx buddy-bot invocations in .github/workflows/buddy-bot.yml.

2. .config/buddy-bot.ts → .config/buddy.ts. 0.11.2 resolves its config as buddy.ts, so the old filename is simply not read — getConfig() falls back to defaults and silently loses repository, dashboard and packages. Verified in both directions against the published build:

   .config/buddy.ts      -> discovered stacksjs/bun-query-builder   (true)
   .config/buddy-bot.ts  -> fell back to defaults                   (false)

3. The config type, BuddyBotConfig → BuddyConfig.

Declared as a devDependency

Rather than leaving it to bunx, so the version is pinned in bun.lock instead of resolved fresh on every CI run, and so the type import in the config file resolves — it previously resolved only because better-dx happened to pull the old package in.

Known leftover

better-dx@0.2.25 (latest) still depends on buddy-bot: ^0.10.5, so the stale package remains in node_modules until that updates. It is unused once the workflow stops calling it. Worth an upstream nudge — every better-dx consumer is pinned to the dead name.

Noting this because CLAUDE.md says not to install better-dx's tooling separately. That rule is about its peer dependencies; buddy-bot is a regular dependency of better-dx, and the two package names don't conflict — but if you'd rather wait for better-dx to follow the rename, this PR's package.json change is the part to drop.

Verification

• Workflow YAML parses; all five jobs intact
• bunx @buddysh/buddy --version → buddy/0.11.2
• Config loads and typechecks against BuddyConfig; getConfig() discovers the right repository, dashboard title and strategy
• update-check, update, dashboard, scan and rebase all present in the 0.11.2 CLI
• bun --bun tsc and pickier clean
• The branch check now matches buddy/* and buddy-bot/*, so PRs already open from the old CLI keep rebasing

I did not run any update/scan/dashboard command while testing — those open PRs and write issues.

🤖 Generated with Claude Code