feat: promote command grid builder

docs/DESIGN_SYSTEM.md

@@ -332,6 +332,33 @@ squeezed beside long module headings on mobile.
 - Community build cards retain the colored top rule, abstract loadout artwork,
   concise tags, agent attribution, and a full-width terminal action.
 
+### Command Grid builder
+
+The production builder uses Command Grid as its loadout workbench. Keep the
+entire build visible in a dense matrix while one connected editor configures
+the selected cell. The full-width Specialization and Focus cell is the root
+choice. Its three supplied abilities appear directly below it, followed by two
+weapons, six gear positions, and one full-width OS Protocol.
+
+Matrix cells summarize selected Talent names, Attribute names and values,
+Brand Sets, or Skill Chips. Do not replace those choices with configuration
+counts. Selecting an ability opens its three attached Skill Chip positions.
+Selecting equipment opens the searchable real-data catalog and its compatible
+configuration controls. Do not display a prototype option that the current
+loadout schema cannot save.
+
+Use `--shd-builder-canvas` for recessed equipment fields. Use
+`--shd-builder-selection` with `--shd-builder-selection-border` for the
+selected cell. Preserve button semantics, `aria-pressed`, focus-visible
+outlines, pressed feedback, and textual readiness states. At narrower desktop
+widths, keep the matrix and editor together and move live results below them.
+On mobile, stack the matrix, editor, and live results in that order.
+
+The command header contains the required build name, local and account save
+actions, account visibility, and optional sharing notes. Sharing notes include
+a short strengths summary and a Markdown usage guide. Persist them separately
+from the validated loadout payload and render them on the shared build page.
+
 ### Prelaunch network shell
 
 Use the standalone prelaunch shell for `/coming-soon`. It replaces the global
@@ -1615,6 +1642,12 @@ Scenario uses the source-defined advanced assumptions saved with the loadout.
 Exclude a mechanic that lacks a required assumption and label it `REQUIRES
 ASSUMPTIONS`. This distinction must remain clear without relying on color.
 
+Loadout summaries name selected Talents, Attributes and their exact values,
+nodes, and Skill Chips. Do not replace these selections with configured
+item counts. Build identity includes a required name plus optional strengths
+summary and usage guide. Shared build views include those author-written fields
+so another player can understand the build's role and operating sequence.
+
 ### Pending ISAC registry records
 
 Pending additions appear directly in the same paginated ISAC registry as live
@@ -2355,11 +2388,12 @@ required inputs.
 
 ### Specialization loadout composer
 
-The builder places Specialization focus selection after equipment
-configuration. The focus identity combines Specialization artwork and the
-primary Attribute mark, followed by three ability panels. Each ability panel
-contains three fixed Skill Chip positions. A chip picker shows definitions
-assigned to that ability and excludes definitions assigned elsewhere.
+The builder presents Specialization and Focus as the first loadout decision.
+The Focus sets the primary Attribute, progression tree, and three ordered
+abilities. Its identity combines Specialization artwork and the primary
+Attribute mark. Each ability panel contains three fixed Skill Chip positions.
+A chip picker shows definitions assigned to that ability and excludes
+definitions assigned elsewhere.
 
 The focus tree groups nodes by row and uses segmented rank controls. Disabled
 ranks remain visible with their lock state. The builder permits a row after the