chore: rename Blazebot to AI Workflow going forward - #293
Conversation
…kills Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015kfeohXE66xx7RJPxZ2pvH
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015kfeohXE66xx7RJPxZ2pvH
… both paths Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015kfeohXE66xx7RJPxZ2pvH
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Goal
Everything going forward is "AI Workflow", not "Blazebot". Existing Blazebot artifacts keep working (backward-compat, no data migration); only new writes and new-facing defaults switch.
A prior change (2026-07-23) already renamed the functional branch prefix and gate check name (
ai-workflow/andAI Workflow /are the current defaults;blazebot/kept only asLEGACY_aliases). This PR finishes the product-name rename in the three places that were still left on the old name.What changed
1. Product-name prose (docs + skills) —
SETUP.md,docs/SPEC.md,docs/user-stories.md, and theinit-*setup skills now say "AI Workflow" /@ai-workflow. Staleblazebot/*branch andblazebot / ...check-name references in SETUP.md corrected toai-workflow/*andAI Workflow / .... No behavior change.2.
CHAT_SDK_BOT_NAMEdefault — flipped fromblazebottoai-workflow(env.ts,.env.example, docs). Deployments that set the variable explicitly keep their value (backward-compat).3. Agent-memory directory
blazebot/memory->ai-workflow/memory, with full backward-compat (the substantive part):ai-workflow/memory/<task>.md.blazebot/memory/...one (migrate-forward: found legacy content is re-stored under the new key). No run loses memory across the cutover.verifyPublishedMemoryScope), the git pre-commit hook +core.excludesFileexcludes, the publication scrub markers, the repo-memoryENTRY_PLATFORM_PATH_PATTERN, and the disposable-review excludes. A doc under either directory can never be committed to or published into a customer repo.default-prompts.ts) points atai-workflow/memory(restore lines also mention the legacy path). Migration0052_builtin_prompt_resync(generated, no-op-safe,IS DISTINCT FROM-guarded,created_by='system'-scoped, nodb.transaction) propagates the new prompt text to already-provisioned DBs; customer-edited prompts untouched.Not changed (intentional backward-compat)
LEGACY_BRANCH_PREFIX="blazebot/"andLEGACY_GATE_CHECK_NAME_PREFIXinworkflow-naming.ts, the GitHub App, Slack app identity, and git history — all left as-is.blazebot/memoryremains a fully-gated, still-read legacy path.Verification
tsc --noEmitclean;build:sharedclean.🤖 Generated with Claude Code