@smartico/public-api 0.0.405 → 0.0.409

package/dist/index.modern.mjs

@@ -539,6 +539,8 @@ const SAWTemplatesTransform = items => {
           acknowledge_action_title: p.saw_prize_ui_definition.acknowledge_action_title,
           acknowledge_dp_additional: p.saw_prize_ui_definition.acknowledge_dp_additional,
           acknowledge_action_title_additional: p.saw_prize_ui_definition.acknowledge_action_title_additional,
+          second_btn: p.saw_prize_ui_definition.second_btn,
+          second_btn_action_title: p.saw_prize_ui_definition.second_btn_action_title,
           out_of_stock_message: p.saw_prize_ui_definition.out_of_stock_message,
           pool: p.pool,
           pool_initial: p.pool_initial,
@@ -1728,13 +1730,12 @@ var AchievementClaimPeriodTypeId;
   AchievementClaimPeriodTypeId[AchievementClaimPeriodTypeId["ExactPeriod"] = 1] = "ExactPeriod";
 })(AchievementClaimPeriodTypeId || (AchievementClaimPeriodTypeId = {}));
 
+// Consumer-facing types live in WSAPITypes.ts (`TClanTournamentPlayers`) — the
+// single source documented + emitted to docs. This transform maps the raw wire
+// shape onto it; do not re-declare a parallel result/player type here.
 const clanTournamentPlayersTransform = response => {
   return {
-    clan_id: response.clan_id,
-    clan_public_meta: {
-      name: response.clan_public_meta.name,
-      image_url: response.clan_public_meta.image_url
-    },
+    tournament_instance_id: response.tournament_instance_id,
     players: (response.players || []).map(p => ({
       user_id: p.userId,
       clean_ext_user_id: p.cleanExtUserId,
@@ -5002,16 +5003,13 @@ class WSAPITournaments extends WSAPIStore {
    *   polling cadence.
    *
    * **Returned shape**
-   * `TClanTournamentPlayers` carries the requested clan's identity
-   * (`clan_id`, `clan_public_meta.name`, `clan_public_meta.image_url`)
+   * `TClanTournamentPlayers` carries the `tournament_instance_id`
    * alongside the `players[]` array — each entry has `position`,
    * `scores`, `public_username`, `clean_ext_user_id`, `avatar_id`,
    * `avatar_real_id`, the resolved `avatar_url`, `user_id`, and the
-   * `is_me` flag identifying the current user's row. The `clan_id` and
-   * `clan_public_meta` on the response echo the input clan — the
-   * default Smartico UI ignores them and renders the header from the
-   * caller-side `ClanLeaderboardEntry` object, but they're available
-   * for consumers that don't already have that context.
+   * `is_me` flag identifying the current user's row. The response does
+   * NOT echo the clan's identity — render the clan header from the
+   * caller-side `ClanLeaderboardEntry` object you passed in.
    *
    * **Username display**: prefer `clean_ext_user_id` when set, falling
    * back to `public_username`. The default Smartico UI uses