feat(isac): author exotic talents in weapon editor

docs/architecture.md

@@ -130,3 +130,17 @@ is directional rather than a monitoring-grade time series. Production alerting
 and historical analysis should eventually use a dedicated external telemetry
 system. This surface deliberately omits secrets, environment-variable values,
 and full database paths.
+
+# Weapon-owned exotic talents
+
+Standard weapon talent pools remain globally reusable and classified by Talent
+1 / Top or Talent 2 / Bottom. An exotic talent is different: one exotic weapon
+owns one dedicated talent, referenced by `weapons.exotic_talent_id`.
+
+The weapon editor creates and updates the underlying normalized `talents`,
+`talent_tiers`, trigger links, effect links, description template, and Exotic
+weapon scope together with the weapon. Server validation rejects an exotic
+talent ID not already owned by the edited weapon and rejects any talent shared
+by another weapon. Converting a weapon back to standard clears the relationship
+and archives its now-unowned exotic talent. Exotic talent creation and editing
+are rejected by the shared Talent Registry so ownership cannot be bypassed.