💥 Rename project to chat2sbx - #12
Merged
Merged
Conversation
Rename the package, CLI, configuration prefix, default data paths, runtime identifiers, documentation, and tests to the new chat2sbx brand. Bump the package version to 0.2.0 for the new package identity.
Leverframe review🟢 Review completed in 434s
Changes |
![leverframe[bot]](https://avatars.githubusercontent.com/in/4614758?s=60&v=4){kind=small}
There was a problem hiding this comment.
Leverframe review
No actionable defects were identified. Review used the CI-aligned native environment: Node v24.20.0 and the packageManager/CI-pinned pnpm 11.23.0. The rename is consistent across runtime identifiers, configuration, documentation, tests, package metadata, and the built CLI.
Findings
No actionable defects found.
Checks
5 passed · 0 failed · 1 not run
Show 6 checks
| Status | Check | Evidence |
|---|---|---|
| 🟢 passed | node --version; pnpm --version |
Node v24.20.0 and pnpm 11.23.0, matching the repository's Node 24 CI environment and exact pnpm pin. |
| 🟢 passed | pnpm install --frozen-lockfile |
The declared lockfile installed successfully without modification. |
| 🟢 passed | pnpm check |
Formatting, oxlint/eslint, TypeScript typechecking, all 53 unit/integration tests, and the production build passed. |
| 🟢 passed | pnpm pack; npm install <generated chat2sbx-0.2.0.tgz>; chat2sbx --version; chat2sbx --help |
The packed artifact installed successfully and exposed a working chat2sbx executable reporting version 0.2.0 and the renamed command help. |
| 🟢 passed | git diff --check b28a7b8cc5d0bd366d3bbfd24c8fee223871bbba...dbb9cb15087e8b551e34c0bd7881090085e27c22 |
No whitespace or patch-format errors. |
| ⚪ not run | pnpm test:e2e |
The repository requires Docker Sandboxes and the renamed template; sbx is not installed in this environment. |
Limitations
- Real Docker Sandbox E2E behavior and creation of the chat2sbx-codexpro:0.30.0 template could not be exercised because the required
sbxexecutable is unavailable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chat2shelltochat2sbxso the public name reflects the disposable sandbox environment rather than only its shell capability.CHAT2SBX_*configuration, default data and template names, MCP/runtime identities, documentation, and tests as one breaking pre-release rename.Verification
pnpm check— formatting, linting, type checking, 53 unit/integration tests, and the production build passed.pnpm test:e2e— not required for this rename because it does not change the real sandbox execution boundary or lifecycle behavior.npm pack --json --ignore-scriptsplus a clean-prefix install — producedchat2sbx@0.2.0;chat2sbx --versionandchat2sbx --helppassed with no stale old-brand metadata in the package manifest.Notes
This intentionally breaks the old package name, CLI name, environment-variable prefix, default data directory, database name, and sandbox template name. The repository rename and first publication of the new npm package are rollout steps after merge; this pull request does not perform those external changes.