Skip to content

Rename Foundry / Power / Compute / Factory player labels - #994

Merged
mohanpednekar merged 1 commit into
claude/purge-code-renamefrom
claude/naming-foundry-hardware
Nov 4, 2026
Merged

mohanpednekar merged 1 commit into
claude/purge-code-renamefrom
claude/naming-foundry-hardware

Conversation

@mohanpednekar

Copy link
Copy Markdown
Owner

Summary

  • Renames player-facing labels from the naming pass (Epic: naming pass — consistent computing-theme names #986, step 2 of 3). Closes Naming pass 2/3: Foundry / Power / Compute / Factory label renames #988. This PR is stacked on Rename Purge code from reboot → purge (save schema v3) #990 and will be retargeted to main after Rename Purge code from reboot → purge (save schema v3) #990 merges.
  • Boosters page → ⚡ Power:
    • The merge chain is renamed Cell → Battery → Pack → Bank → Generator → Turbine → Plant → Grid → Reactor → Fusion.
    • The merge action is now Charge up / Auto-charge.
    • Boost modes are now Turbo / Balanced / Eco.
    • Data Lakes now sell Cells.
  • PP Compute tiers are renamed Cores → Chips → Servers → Racks → Pods → Clusters → Datacenters → Regions → Clouds → Superclouds. Each tier shows its KFlops…QFlops output.
  • Byte Foundry:
    • Data Stream Speed is now Bitrate, Combine is Compile, and tap is Ping.
    • The pool speed readout is now Bandwidth and the pool buffer is Staging.
    • Reset Pool is now 🗜 Compact Pool.
  • Factory:
    • Speed Up is now Clock Speed.
    • The overlay at the Purge threshold now reads "Disk full".
    • The uncapped mode is now called Overflow mode.
    • The nav icon is now 🏭.
  • Labels only: page ids, state fields, preset keys and tier ids are unchanged, so saves are not affected.
  • Fix: three buttons passed variant="purge", which the Button component doesn't define: Upgrade Capacity, Upgrade Bitrate and the selected Auto Boost preset. They now use variant="prestige" and get their intended colour back.

Test plan

  • yarn test passes (2213/2213), with test queries pointed at the new strings and no assertions loosened
  • yarn build succeeds
  • yarn test:e2e: not run. data-lake.e2e.js uses the new strings. The visual-regression baselines will need regenerating.

Documentation

  • Updated CLAUDE.md (nav order, architecture wording, the player label ↔ code mapping), AGENTS.md and the three docs/*_REFERENCE.md files.
  • Added entries under CHANGELOG ### Changed and ### Fixed.

Generated by Claude Code

Boosters page -> Power (chain Cell..Fusion, Charge up/Auto-charge, presets
Turbo/Balanced/Eco); PP Compute tiers -> Cores..Superclouds with KFlops..QFlops
output; Data Stream Speed -> Bitrate, Combine -> Compile, tap -> Ping; pool
speed -> Bandwidth, pool buffer -> Staging, Reset Pool -> Compact Pool; Speed
Up -> Clock Speed; Purge overlay headline -> Disk full; Overflow mode copy;
Factory icon -> factory. Labels only: ids/state/preset keys unchanged.
Fixes Button variant='purge' (unresolved) -> 'prestige'.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WvzZB7A6LFCYnhw8YhQfSW
@mohanpednekar
mohanpednekar marked this pull request as ready for review November 4, 2026 03:36

Copy link
Copy Markdown
Owner Author

Adversarial review of eb418dc: NEEDS CHANGES. It found no economy, state, identifier or save-key change, and the tests pass. To fix:

  • Reference docs (COMPONENTS_REFERENCE, MAINPAGE_REFERENCE, ECONOMY_REFERENCE, plus the summaries in CLAUDE.md and AGENTS.md) still list the old accessible names.
  • Two doc sentences now use "Cores" for the Power-chain entity, but "Cores" now names the Flops tier.
  • The visual-regression baselines are stale.
  • The Data Lake's own fill was wrongly relabelled "staging".
  • "Ping" was applied to plain button clicks.
  • A few mixed strings remain: "Auto-merging" and "base Speed … raises Bitrate".
  • There's no regression test for the Button variant fix.

Fixing these now.


Generated by Claude Code

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-04T03:36:56.419224Z eb418dc Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@mohanpednekar
mohanpednekar merged commit 2ae761b into claude/purge-code-rename Nov 4, 2026
2 checks passed
@mohanpednekar
mohanpednekar deleted the claude/naming-foundry-hardware branch November 4, 2026 03:36
cursor Bot pushed a commit that referenced this pull request Nov 4, 2026
#994 landed on this branch with a NEEDS_CHANGES review that was never
followed up. Restore Provision Disk "tap to queue", Auto-charging status,
and the Data Lake's own buffer label; keep Ping/Staging for the tap and
pool buffer only. Update current-behavior docs so Power-chain Cells are
not called Cores, and add a Button variant="prestige" regression test.

Co-authored-by: Mohan Namdeo Pednekar <mohanpednekar@users.noreply.github.com>
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.

2 participants