Add ISAC Skill Chips data module

docs/DESIGN_SYSTEM.md

@@ -251,7 +251,7 @@ squeezed beside long module headings on mobile.
   unrestricted administrative role; `Community Oversight` is reserved for
   community content moderation and does not imply ISAC access. Operational
   ISAC access is delegated separately through scoped roles and permissions.
-- Roles & Permissions is a separate User Operations registry. Role definitions
+- Roles is a separate User Operations registry. Role definitions
   compose discrete capabilities through a dense permission catalogue with an
   explicit selected count and textual `GRANTED` / `NOT GRANTED` states. The
   built-in Admin role is visible but system-protected. Delegated access managers
@@ -751,3 +751,35 @@ when the complete option set is small enough to scan comfortably. Dropdowns
 remain appropriate for long, dynamic, or search-oriented lists. Both modes
 share hover, pressed, focus-visible, selected, disabled, responsive, and
 44-pixel mobile-target behavior so feature modules do not reimplement it.
+
+### Skill Chip data console
+
+Skill Chip editing follows the dense ISAC staged-definition pattern: identity
+and icon first, the 2-piece numeric bonus second, mutually exclusive primary
+and secondary roll pools next, and the 3-piece talent last. Superior blue and
+High-end yellow communicate the only supported qualities; orange remains
+reserved for actions and current interactive state. A four-step segmented
+preview exposes the linear zero-to-three High-end interpolation without storing
+duplicate values. At narrow widths the roll pools and talent columns stack,
+preview segments become a two-by-two grid, and interactive targets remain at
+least 44 pixels tall.
+
+### ISAC record identity controls
+
+Game-data icon editors use the shared `--isac-icon-editor-width` footprint
+(150 pixels on desktop) regardless of module. Identity layouts allocate that
+fixed column to `IconUploadField`, give the record name the flexible dominant
+column, and stack both controls at mobile widths. Do not enlarge an upload
+drop-zone to fill spare identity-row space.
+
+The primary `name` field in every ISAC data editor is a header-level input:
+46 pixels tall with larger, heavier text. This creates a consistent first
+reading point for long registries while keeping secondary metadata compact.
+
+`SearchableAssignment` is the standard relationship picker for long attribute,
+talent, trigger, and compatibility lists. Multiple mode manages additive sets;
+single mode presents the same searchable selected/result treatment for one
+relationship. Prefer these modes over native selects once a source registry is
+large enough that scanning a dropdown is inefficient. The selected record,
+pending-contribution state, keyboard focus, and remove interaction must remain
+explicit in both modes.

docs/architecture.md

@@ -193,9 +193,27 @@ talent effects use `base × (1 + upgrades / 5)` for zero to five upgrades.
 Server actions validate all relationships and append the full owned graph to
 the existing `game_data` audit history.
 
+# Skill Chip quality scaling
+
+Skill Chip sets support Superior and High-end chip instances. Each set owns one
+2-piece bonus, distinct primary and secondary stat-option pools, and one
+3-piece talent with reusable trigger links and normalized effect rows. Primary
+and secondary options reference active attributes that define Skill Chip
+minimum and maximum roll values; a configured chip rolls one primary and two
+distinct secondary stats from those separate pools.
+
+Both set-bonus progression systems use the number of equipped High-end chips as
+the interpolation step. For `h` High-end chips, where `h` is zero through
+three, a configured minimum and maximum resolve as
+`minimum + (maximum − minimum) × h / 3`. Zero High-end chips therefore produce
+the minimum, while three produce the maximum. The editor stores only endpoints
+and previews all four states, preventing duplicated tier data from diverging.
+Skill Chip mutations, owned relationships, and safe icon metadata are captured
+in the `game_data` audit stream.
+
 # Game-data icon storage
 
-Talents, brand sets, and OS Protocols reference uploaded artwork through the
+Talents, brand sets, OS Protocols, and Skill Chips reference uploaded artwork through the
 polymorphic `game_data_icons` metadata table. Original uploads are never
 retained. The shared server pipeline accepts transparent SVG, PNG, WebP, and
 AVIF sources, rejects active or externally referenced SVG content, and uses