Rename product to BizerBrain

[kelsi-bizer]

Summary

Renames the product from BizerOS Knowledge to BizerBrain across every user-facing surface. Surgical change: 11 files, 15 insertions, 15 deletions. Skips the upstream Logseq files (PR #10 deletes those) and the README (PR #10 rewrites it). The rename hits the surfaces that actually matter:

• The skill folder and its name: field (so ClawHub/Hermes/OpenClaw register the right name)
• The web UI title and header (what users see)
• The Docker image tag (so deployments pull from the right path)
• The package names in package.json (npm/pnpm identity)
• Default brain path (/srv/bizeros/brain → /srv/bizerbrain/brain)
• LocalStorage keys (so the in-app preferences live under the new name from day one)

Why now

This is the cheapest possible moment to rename. The image hasn't been pulled in production, ClawHub hasn't been submitted, no external blog posts or tweets reference the old name. Every day from here, the cost rises. BizerBrain is shorter, matches the /brain folder convention used everywhere, and sits in the same naming family as GBrain — deliberate market positioning.

What changed

File	Change
.agents/skills/{bizeros-knowledge → bizerbrain}/	folder renamed via git mv (history preserved)
.agents/skills/bizerbrain/SKILL.md	frontmatter name: bizerbrain, tag bizerbrain, body heading # BizerBrain, default path /srv/bizerbrain/brain
.agents/skills/bizerbrain/tools/brain_tools.py	docstring + default BRAIN_DIR
packages/notes-app/index.html	<title>BizerBrain</title>
packages/notes-app/src/App.tsx	header text BizerBrain + bizerbrain-view-mode localStorage key
packages/notes-app/src/hooks/useTheme.ts	bizerbrain-theme localStorage key
packages/notes-app/package.json	@bizerbrain/notes-app
packages/file-api/package.json	@bizerbrain/file-api
docker/entrypoint.sh	header comment
.github/workflows/build-docker.yml	IMAGE_NAME: bizerbrain — image now publishes to ghcr.io/<owner>/bizerbrain:latest

What's NOT in this PR

• GitHub repo rename — UI action, owner does it whenever. The image path on GHCR is already on bizerbrain regardless of repo name; no rush.
• README.md — still upstream Logseq content on master. PR Clear out Logseq lineage, re-license to Apache-2.0 #10 rewrites it (just confirm it uses "BizerBrain" when that PR rebases on this).
• LICENSE — added by PR Clear out Logseq lineage, re-license to Apache-2.0 #10 (likewise will use "BizerBrain" once rebased).
• Upstream Logseq files — PR Clear out Logseq lineage, re-license to Apache-2.0 #10 deletes wholesale; not worth touching here.

Coordination with open PRs

• PR Clear out Logseq lineage, re-license to Apache-2.0 #10 (Logseq cleanup) — needs a rebase to use "BizerBrain" in the new README + LICENSE.
• PR sources/wiki split, truth-timeline page structure, and MCP server #11 (sources/truth/MCP) — needs a rebase: rename .agents/skills/bizeros-knowledge → bizerbrain in its SKILL.md edits, rename the new MCP package from @bizeros/mcp-server → @bizerbrain/mcp-server, and update its server name field.

Both are mechanical. Happy to handle them after this lands.

Verified

• pnpm typecheck in packages/notes-app passes with the renamed package
• pnpm test in packages/file-api — 20/20 tests pass
• grep "BizerOS\|bizeros" in our owned files (.agents/skills/bizerbrain, packages/, docker/, build-docker.yml) returns zero hits

Test plan

• Merge → verify Build-Docker publishes ghcr.io/kelsi-bizer/bizerbrain:latest
• Pull and run the image — verify the page title says "BizerBrain" and the header shows "BizerBrain"
• Drop the renamed skill into ~/.hermes/skills/bizerbrain (or wherever) — agent should load it under the new name
• Optional follow-up: rename the GitHub repo to bizerbrain from bizeros-knowledge

---

Generated by Claude Code