chore(branding): remove leftover upstream theme identifiers

The theme was renamed Zibll/子比 → AKSRT → Jio, but upstream branding
survived the sweeps in CSS classes, the SVG sprite prefix, a persisted
widget field ID, JS events, admin Vue class names, test infrastructure
and docblocks.

Renames:
- zib-widget / zib-widget-wrap / zib-slider → jio-widget-box /
  jio-widget-box-wrap / jio-slider-box (jio-widget is taken by the modern
  widget shell, jio-box-* by the card primitives)
- zib-partners-scroll + zps-* → jio-partners-scroll + jps-*
- zib-combo-info-card + zci-* → jio-combo-info-card + jci-*
- zibsvg- → jiosvg-, including the exported picker helpers and the
  fa-zibsvg- family-prefix guard
- zibpay_type → pay_type; the dual-read fallback in PostQuery collapses
  to a single key
- [zibajax="submit"] dropped (no PHP emitter); zib_ajax.success →
  jio_ajax.success
- aks-* admin Vue classes → jio-*
- zib_palette() → palette()

User-facing vendor traces are gone: the floating "more" button default no
longer ships a zibll.com link or 子比主题 marketing copy, the notice
widget ships no preset promo entries, and the four 官网教程 links are
removed from the post-list admin schema.

Test infrastructure renamed to neutral names (docker-compose.reference.yml,
Caddyfile, article-baseline.json, modern-widgets-contract.test.cjs) with
their DB/volume/env/slug identifiers following.

Kept intentionally, documented in tests/fixtures/README.md: the golden
fixture reference fingerprint (a SHA-256 record of an external directory,
read by validate-widget-golden / generate-widget-golden-fixture /
audit-widget-system), the doesNotMatch guards that prove the old tokens are
gone, and the reference theme's own meta key in the visual fixtures.

No backward-compat or data migration: saved widget configs holding old
icon keys or the old field ID silently lose them, per the project's
rewrite-over-compatibility rule.

Verified: 132/132 node contract tests, php tests/widget-system/run.php
(146 assertions), audit-admin-contracts, audit-psr4-paths and
validate-widget-golden all green; tracked bundles regenerated and in sync.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/Content/VipServiceModal.php

@@ -156,9 +156,9 @@ trait VipServiceModal {
     }
 
     /**
-     * 积分兑换会员弹窗（参考主题 zibpay_get_vip_points_exchange_modal 1:1 移植）。
+     * 积分兑换会员弹窗。
      *
-     * 服务端静态输出参考主题 refresh_modal 同构外壳：
+     * 服务端静态输出刷新式弹窗外壳：
      *   .modal.flex.jc.fade > .modal-dialog.modal-mini.full-sm
      *     > .modal-content > .modal-body
      * 与余额充值/购买积分弹窗同构（静止态由 vip-modal.css 显式隐藏，打开态由
@@ -242,13 +242,11 @@ trait VipServiceModal {
         $desc_text = trim((string) ($vip['points_exchange']['desc'] ?? ''));
         $desc = $desc_text !== ''
             // 管理员编辑的富文本说明：保存端已 wp_kses_post，这里同级别输出
-            // （参考主题 zibpay_get_vip_points_exchange_modal 原样拼接）。
+            // （原样拼接）。
             ? '<div class="muted-box muted-2-color padding-10 em09 mt20 jio-vip-points-desc">' . wp_kses_post($desc_text) . '</div>'
             : '';
 
-        // 最低价套餐仍超出用户积分 → 参考主题的 badg c-red btn-block 提示。
-        // （参考主题源码写作 `!$min_val > $user_points`，因运算符优先级恒假，
-        //  此处按其原意取真实比较，保证提示分支可达。）
+        // 最低价套餐仍超出用户积分 → badg c-red btn-block 提示。
         if ($min_points > $user_points) {
             $form = '<div class="mt20"><div class="badg c-red btn-block">'
                 . esc_html(sprintf(__('%s不足，暂时无法兑换', 'jio'), $currency))
@@ -290,7 +288,7 @@ trait VipServiceModal {
     }
 
     /**
-     * 积分兑换卡片等级图标（参考主题 zibpay_get_vip_card_icon）。
+     * 积分兑换卡片等级图标。
      *
      * @param array<string,mixed> $level_settings 等级设置（含 name / img_icon）。
      */