Summer SDK docs rename - #1
Merged
Merged
Conversation
Folder, page slugs, navigation, and copy move from Crafty to the current brand: the platform is Summercraft, the dev surface is Summer SDK. - api-reference/crafty-sdk/ -> api-reference/summer-sdk/ - crafty.mdx / crafty-game.mdx / crafty-player.mdx -> summer.mdx / summer-game.mdx / summer-player.mdx - build-your-first-crafty-game -> build-your-first-summer-game - GDScript symbols move to the Summer.* form (Crafty -> Summer, CraftyGame -> SummerGame, CraftyPlayer -> SummerPlayer, ...) - manifest key crafty_sdk -> summer_sdk; res://crafty.cfg -> res://summer.cfg - playcrafty.games -> summercraft.ai (summercraft.ai is canonical per the Summercraft DOMAINS.md) Per URL-POLICY.md every moved URL gets a permanent redirect: 18 added, so no previously published address 404s. The Railway platform-api host crafty-production-5a7c.up.railway.app is deliberately left alone. It is the live deployed submission endpoint and renaming it in docs would document an endpoint that does not exist. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Crafty to Summer rename touches required identifiers: a game still declaring crafty_sdk or extending CraftyGame fails submission validation rather than degrading quietly. That needs one authoritative map, not a paragraph buried in a guide. Adds /api-reference/summer-sdk/naming covering the autoload, every SDK class, manifest and config keys, script paths, the web runtime protocol bump, and the domain. It also records what deliberately did NOT move, which is the part future readers get wrong: the Railway platform-api host, the c-prefixed tables, and the mobile bundle id are resolved by live systems, not copy. Changelog gets a dated entry labelled "Summer SDK" rather than a version number, since no Summer Engine behavior changed. Older entries are left as they were shipped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
crafty-game-server is the live Fly.io application name, and it is also the base for the game-server image tag and the .fly.dev hostname. Same class as the Railway platform-api host already listed: a deployed identity rather than copy, so it does not move with the brand. Found by the desktop cutover; recording it here keeps the "did not move" list in one place instead of one per repo. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Per the approved ECONOMY_PRD (summercraft/docs/ECONOMY_PRD.md, Mathias, 2026-07-28): display name "Crafties", wire name `crafties`, and "credits" stays reserved for Summer Engine compute billing. Two currencies forever; crafties never touch cProfiles.credits. The persistence guide was the only page using "credits" for game economy: QUEST_CREDIT_REWARD -> QUEST_CRAFTIES_REWARD and the synced key "credits" -> "crafties". The naming page gets a currency section stating the split, because the docs use "credits" for two other unrelated things already — the compute billing unit, and crediting an asset's creator / the in-game credits roll. Without saying so plainly, "in-game credits" is ambiguous in exactly the place both senses are live at once. Left alone: every attribution and billing use of the word. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The page described a version bump and said the old protocol was removed, which reads like v2 redesigned the wire format. It did not. v2 is a rename plus a version bump: message shapes carry over from v1, including the legacy normalization that still accepts a bare event name. Left as-is, a creator would reasonably conclude their message handling needed rewriting when only the protocol string and the runtime global change. Confirmed against the web cutover branch, where the qa-harness protocol suite passes against contracts/webview.v2.schema.json. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The page asserted the currency "kept its Crafty root deliberately" and called it the one place the old brand survives as a product noun. That reads as a closed design decision. It is not one: the commit that aligned the spelling records that whether a Crafty-derived name survives the rebrand is still an open product call. The name itself stays, because it is current truth and creators need it to write against Summer.economy. Only the editorial claim about permanence goes. Nothing here hedges the name either — the PRD freezes the wire form on ship, and a public page is the wrong venue for pre-ship uncertainty. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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.
crafty-sdk -> summer-sdk with 18 permanent redirects, naming contract page, Crafties currency ruling, v2 protocol references. Link checks clean. Approved by Mathias in session.
🤖 Generated with Claude Code