Consolidate duplicate builder surfaces and complete toolbox ownership classification - PR_26154_039-041-cleanup-stack

Author: ToolboxAid

admin/grouping-colors.html

@@ -89,7 +89,7 @@ <h2>Current Tool Groupings (deprecated)</h2>
                                     </tr>
                                     <tr>
                                         <td>Building / Creation</td>
-                                        <td>Game Builder</td>
+                                        <td>Game Design Studio</td>
                                         <td><span class="brand-color-code"><span
                                                     class="brand-color-swatch swatch-green"></span>Green</span></td>
                                     </tr>
@@ -176,7 +176,6 @@ <h3><span class="brand-color-code"><span
                                             class="brand-color-swatch swatch-pink"></span>Pink: Build &amp;
                                         Create</span></h3>
                                 <ul>
-                                    <li>Game Builder</li>
                                     <li>Object Vector Studio</li>
                                     <li>World Vector Studio</li>
                                     <li>Animation Studio</li>

…d/contracts/tools/gameBuilderContract.js …ference/contracts/gameBuilderContract.jssrc/shared/contracts/tools/gameBuilderContract.js renamed to archive/v1-v2/tools/game-builder-reference/contracts/gameBuilderContract.js src/shared/contracts/tools/gameBuilderContract.js renamed to archive/v1-v2/tools/game-builder-reference/contracts/gameBuilderContract.js

@@ -6,7 +6,6 @@
         "animation-studio": "toolbox/animation/index.html",
         "asset-studio": "toolbox/assets/index.html",
         "code-studio": "toolbox/code/index.html",
-        "game-builder": "toolbox/game-builder/index.html",
         "game-design-studio": "toolbox/game-design/index.html",
         "input-studio": "toolbox/input/index.html",
         "localization-studio": "toolbox/localization/index.html",
@@ -19,7 +18,6 @@
         "storage-inspector": "toolbox/storage/index.html",
         "world-vector-studio": "toolbox/world-vector/index.html",
         "configuration-admin": "toolbox/configuration-admin/index.html",
-        "tool-builder": "toolbox/builder/index.html",
         "tool-creator": "toolbox/creator/index.html",
         cloud: "toolbox/cloud/index.html",
         games: "games/index.html",

toolbox/game-builder/index.html …uilder-reference/game-builder/index.htmltoolbox/game-builder/index.html renamed to archive/v1-v2/tools/game-builder-reference/game-builder/index.html toolbox/game-builder/index.html renamed to archive/v1-v2/tools/game-builder-reference/game-builder/index.html

@@ -37,17 +37,10 @@
               <a data-nav-link data-toolbox-menu-item data-route="object-vector-studio" href="toolbox/object-vector/index.html">Object Vector</a>
             </div>
           </div>
-          <div class="nav-item nav-popout-item" data-toolbox-menu-group>
-            <a data-toolbox-menu-group-label data-route="toolbox" href="toolbox/index.html" aria-haspopup="true">Tooling &#9656;</a>
-            <div class="sub-menu sub-menu--nested" data-toolbox-submenu aria-label="Tooling tools">
-              <a data-nav-link data-toolbox-menu-item data-route="tool-builder" href="toolbox/builder/index.html">Tool Builder</a>
-              <a data-nav-link data-toolbox-menu-item data-route="tool-creator" href="toolbox/creator/index.html">Tool Creator</a>
-            </div>
-          </div>
+          <a data-nav-link data-toolbox-menu-item data-route="tool-creator" href="toolbox/creator/index.html">Tool Creator</a>
           <div class="nav-item nav-popout-item" data-toolbox-menu-group>
             <a data-toolbox-menu-group-label data-route="toolbox" href="toolbox/index.html" aria-haspopup="true">Worlds &#9656;</a>
             <div class="sub-menu sub-menu--nested" data-toolbox-submenu aria-label="World tools">
-              <a data-nav-link data-toolbox-menu-item data-route="game-builder" href="toolbox/game-builder/index.html">Game Builder</a>
               <a data-nav-link data-toolbox-menu-item data-route="game-design-studio" href="toolbox/game-design/index.html">Game Design</a>
               <a data-nav-link data-toolbox-menu-item data-route="particle-studio" href="toolbox/particles/index.html">Particles</a>
               <a data-nav-link data-toolbox-menu-item data-route="world-vector-studio" href="toolbox/world-vector/index.html">World Vector</a>

…d/tools/GameBuilderToolContract.test.mjs …e/tests/GameBuilderToolContract.test.mjstests/shared/tools/GameBuilderToolContract.test.mjs renamed to archive/v1-v2/tools/game-builder-reference/tests/GameBuilderToolContract.test.mjs tests/shared/tools/GameBuilderToolContract.test.mjs renamed to archive/v1-v2/tools/game-builder-reference/tests/GameBuilderToolContract.test.mjs

@@ -44,8 +44,8 @@ <h2>Frequently Asked Questions</h2>
                             <details class="vertical-accordion">
                                 <summary>Which tool should I open first?</summary>
                                 <div class="accordion-body">
-                                    <p>Start with Game Design Studio when you are shaping an idea, then move into Game
-                                        Builder, Asset Studio, Animation Studio, Sound Studio, and the publishing tools
+                                    <p>Start with Game Design Studio when you are shaping an idea, then move into Asset
+                                        Studio, Animation Studio, Sound Studio, and the publishing tools
                                         as the project becomes more concrete.</p>
                                 </div>
                             </details>

toolbox/builder/index.html …uilder-reference/tool-builder/index.htmltoolbox/builder/index.html renamed to archive/v1-v2/tools/game-builder-reference/tool-builder/index.html toolbox/builder/index.html renamed to archive/v1-v2/tools/game-builder-reference/tool-builder/index.html

@@ -1,13 +1,13 @@
 # BUILD_PR: Schema location correction
 
 ## Codex task
-Move the schema contract plan from root-level schema files to `toolbox/schemas/`.
+Move the schema contract plan from root-level schema files to `src/shared/schemas/`.
 
 ## Required changes
 1. Remove any planned or newly-added root-level `*.schema.json` files.
-2. Add schema contracts under `toolbox/schemas/` only.
-3. Put reusable manifest schemas directly under `toolbox/schemas/`.
-4. Put individual tool payload schemas under `toolbox/schemas/tools/`.
+2. Add schema contracts under `src/shared/schemas/` only.
+3. Put reusable manifest schemas directly under `src/shared/schemas/`.
+4. Put individual tool payload schemas under `src/shared/schemas/tools/`.
 5. Update any docs or references to point to the new schema paths.
 
 ## Do not
@@ -24,4 +24,4 @@ Search for misplaced schemas:
 Get-ChildItem -Path . -Filter *.schema.json -Recurse | Select-Object FullName
 ```
 
-Expected result: all schema files are under `toolbox\schemas\`.
+Expected result: all schema files are under `src\shared\schemas\`.

assets/theme-v2/js/gamefoundry-partials.js

@@ -28,12 +28,12 @@ toolbox/
 ## Rationale
 Schemas belong near tool contracts, not at repository root. The root should stay clean and should not accumulate validation artifacts.
 
-Shared schemas live at `toolbox/schemas/`.
-Tool-specific schemas live at `toolbox/schemas/tools/<tool>.schema.json`.
+Shared schemas live at `src/shared/schemas/`.
+Tool-specific schemas live at `src/shared/schemas/tools/<tool>.schema.json`.
 
 ## Acceptance criteria
 - No new schema files are added at repository root.
-- All JSON schema files are under `toolbox/schemas/`.
-- Tool manifest validation uses `toolbox/schemas/tool.manifest.schema.json`.
-- Tool-specific payload validation uses `toolbox/schemas/tools/<tool>.schema.json`.
+- All JSON schema files are under `src/shared/schemas/`.
+- Tool manifest validation uses `src/shared/schemas/tool.manifest.schema.json`.
+- Tool-specific payload validation uses `src/shared/schemas/tools/<tool>.schema.json`.
 - Samples reference the same tool schema contracts used by tool manifests.