feat(isac): add searchable gear assignments

docs/DESIGN_SYSTEM.md

@@ -603,12 +603,21 @@ active state.
 Pending records may be used as dependencies in later proposals by any
 contributor. Render these choices in the ordinary assignment control with a
 restrained orange border/background and the explicit text `PENDING` plus the
-proposer's display name; never present them as live data. Approval is dependency
+proposer’s display name; never present them as live data. Approval is dependency
 ordered: a dependent proposal stays pending until every referenced proposal is
 approved, while rejected or failed dependencies block it. This state must be
 conveyed by text as well as color and must remain legible in compact and
 responsive editor layouts.
 
+Large many-to-many selections use the shared searchable assignment control,
+including weapon talent pools, gear talent compatibility, and compatible brand
+sets. The control keeps assigned records visible as removable chips, filters
+available records by name, limits the rendered result set, and submits canonical
+hidden inputs. Configure its subject labels and empty-state copy for the entity
+being assigned rather than embedding talent-specific language in the shared
+component. Pending contributor records retain their orange treatment and named
+proposer in both search results and dependency workflows.
+
 Audit History may use a five-column KPI filter rail when all durable operational
 domains need first-class visibility. It retains the standard compact KPI height
 and collapses through the shared dashboard breakpoints; do not increase card