Skip to content

chore(rename P1): brand prose ClawDnD → WorldOS (cosmetic stragglers) - #982

Merged
100yenadmin merged 1 commit into
mainfrom
chore/rename-p1-cosmetic
Jun 17, 2026
Merged

chore(rename P1): brand prose ClawDnD → WorldOS (cosmetic stragglers)#982
100yenadmin merged 1 commit into
mainfrom
chore/rename-p1-cosmetic

Conversation

@100yenadmin

Copy link
Copy Markdown
Member

Phase 1 of the owner-approved full ClawDnD→WorldOS cutover

The v1.0.3 rename (#296/#299/#300/#301, tracker #295) shipped the bulk; this finishes the
job in phased PRs to zero going-forward clawdnd. Phase 1 = brand prose only.

What changed (30 files, brand token only)

Renamed the brand word ClawDnDWorldOS in command/skill descriptions, agent
prose, adventure flavor text, SRD attribution, and user-facing status strings. Dual
"WorldOS / ClawDnD" labels collapsed to "WorldOS".

Surgically PRESERVED (this is why it's not a blind find-replace)

  • Retained wire contracts (move atomically in later phases): clawdnd-engine/-rules/-voice/-player, CLAWDND_* env vars, dev.clawdnd.app, ClawDnD-val path, ClawDnDNative web-bridge, lowercase clawdnd_* shell/py functions.
  • Historical / legal (never rewrite): CHANGELOG.md, qa/SCORECARD.md, the LICENSE trademark list (keeps "ClawDnD" as a protected mark), servers/*/_env.py "renamed from ClawDnD" explanation, docs/roadmap/SPRINT_MAP.md, qa/transcripts/*.

Transform = collapse dual-naming, then ClawDnD→WorldOS with a negative lookahead on -val/Native, applied to an explicit 30-file allowlist.

Gates (local; CI degraded repo-wide → squash-admin per dev loop)

  • license_check.py
  • bash -n clean on all touched scripts ✅
  • both adventure.json still valid JSON ✅
  • spot-checked: DM SKILL.md keeps clawdnd-engine/rules/voice; play.sh keeps CLAWDND_PLAY_* + clawdnd_write_provider_status

No engine/runtime behavior changes.

First phase of the owner-approved full ClawDnD→WorldOS cutover (the v1.0.3 rename
shipped #296/#299/#300/#301 but left brand-prose stragglers). This renames ONLY the
brand token in prose/docs/flavor/command+skill descriptions and user-facing status
strings — surgically PRESERVING every retained contract and historical record:

KEPT (moved in later phases / immutable): clawdnd-engine/-rules/-voice/-player MCP ids,
CLAWDND_* env vars, dev.clawdnd.app, ClawDnD-val path, ClawDnDNative web-bridge,
lowercase clawdnd_* shell/py functions; and the historical/legal text (CHANGELOG,
qa/SCORECARD.md, LICENSE trademark list, servers/*/_env.py "renamed from ClawDnD"
explanation, docs/roadmap/SPRINT_MAP.md, qa/transcripts/*).

Transform: collapse dual "WorldOS / ClawDnD" → "WorldOS", then ClawDnD→WorldOS with a
negative lookahead preserving -val/Native suffixes; applied to an explicit allowlist of
30 brand-prose files only.

Gates: license_check pass; bash -n clean on all touched scripts; both adventure.json
still valid JSON; spot-checked that DM SKILL.md keeps clawdnd-engine/rules/voice and
play.sh keeps CLAWDND_PLAY_* + clawdnd_write_provider_status.
@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@100yenadmin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 823c8717-6239-4ccd-8345-e1bce78c3a57

📥 Commits

Reviewing files that changed from the base of the PR and between 5544ab1 and bb492f5.

📒 Files selected for processing (30)
  • .codex/environments/environment.toml
  • .coveragerc
  • .pre-commit-config.yaml
  • agents/companion-agent.md
  • commands/campaign-new.md
  • commands/save.md
  • commands/session-start.md
  • commands/voice-toggle.md
  • commands/world-play.md
  • content/campaigns/cellar-rats/adventure.json
  • content/campaigns/cellar-rats/adventure.md
  • content/campaigns/embergloom-pact/adventure.json
  • content/campaigns/embergloom-pact/adventure.md
  • data/srd/ATTRIBUTION.md
  • data/srd/LICENSE-DATA.md
  • data/srd/bg-midtier/ATTRIBUTION.md
  • qa/lib_beat_driver.sh
  • scripts/launch_common.sh
  • scripts/license_check.py
  • scripts/play.sh
  • scripts/play_codex_actor.sh
  • scripts/play_codex_dm.sh
  • scripts/play_party.sh
  • scripts/qa_reap.sh
  • skills/campaign-author/SKILL.md
  • skills/companion/SKILL.md
  • skills/dungeon-master/AGENT.md
  • skills/dungeon-master/SKILL.md
  • skills/dungeon-master/reference/living-world.md
  • skills/world-author/SKILL.md

Comment @coderabbitai help to get the list of available commands and usage tips.

@100yenadmin
100yenadmin merged commit cb5da8f into main Jun 17, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant