Repository navigation
Rebrand platform and codebase as BAIGE - #1
Merged
Merged
Conversation
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
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
Reworks the repository around the new 百舸 / BAIGE brand architecture and removes CrossLoom as an active product/platform name.
Brand and product system
docs/PRODUCT_NAMING.mdas the canonical naming guide.CrossLoomandUDMBFas legacy names permitted only for migration/history/compatibility contexts.Code namespace migration
crossloomroot workspace →baige@crossloom/studio→@baige/studio@crossloom/editor-core→@baige/editor-core@crossloom/schema→@baige/schema@crossloom/bridge-protocol→@baige/bridge-protocolCROSSLOOM_SCHEMA_VERSION→BAIGE_SCHEMA_VERSIONCrossLoomDocument→BaigeDocumentWebsite
A BAIGE Projectfamily model.CrossLoomGitHub/Pages URL only as an explicit migration slug.CI hygiene
pnpm-lock.yamlbefore validation could start.Compatibility
This intentionally includes early breaking API/package-name changes. The repository is still at
0.1.0-foundation, so this PR treats the BAIGE reset as the new naming baseline rather than carrying the old namespace forward as a permanent alias.The GitHub repository itself is still named
CrossLoombecause the connected GitHub action set does not expose a repository-rename action. Documentation explicitly treats that string as a historical URL slug.Validation
GitHub Actions CI passes on the final branch head: