refactor(core): rename formatMemoryUsage to formatBytes for clarity and reuse

[NubeBuster]

Summary

The formatMemoryUsage function in packages/core/src/utils/formatters.ts is a general-purpose byte formatting utility that converts byte values to human-readable strings (e.g., 1024 → "1.0 KB").

The current name formatMemoryUsage is misleading as it suggests the function is specific to memory metrics, when it actually formats any byte value.

Proposed Change

Rename formatMemoryUsage → formatBytes within the core package scope only.

Files affected:

• packages/core/src/utils/formatters.ts - rename function
• packages/core/src/utils/formatters.test.ts - update test suite name
• packages/core/src/tools/shell.ts - update import and usage

Why this matters:

1. Clarity: formatBytes accurately describes what the function does
2. Reuse: The current name discourages reuse because it sounds memory-specific, even though it's a general byte formatter
3. Consistency: Aligns with common naming conventions (formatBytes is standard across ecosystems)

Scope

This refactor is limited to packages/core/ only. The cli/ package has its own formatMemoryUsage function which remains unchanged (intentional package independence per project conventions).

[NubeBuster]

/assign

[gemini-cli]

👋 @NubeBuster, you've been assigned to this issue! Thank you for taking the time to contribute. Make sure to check out our contributing guidelines.

[gemini-cli]

This is a refactoring enhancement to rename a utility function in the core package for improved clarity, reusability, and consistency. This is a good first issue.

[madhavmadupu]

Hi, I would like to pick this up!

Here is my plan:

1. Rename formatMemoryUsage to formatBytes in packages/core/src/utils/formatters.ts to better reflect its generic utility.
2. Update the corresponding unit tests in packages/core/src/utils/formatters.test.ts.
3. Rename the matching utility in packages/cli/src/ui/utils/formatters.ts for consistency.
4. Refactor all call sites across the codebase (e.g. MemoryUsageDisplay.tsx, bugCommand.ts, shellCommandProcessor.ts) to use the new formatBytes name.
5. Verify with npm run preflight.

Let me know if this looks good!