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>

tests/widget-system/balance-charge-modal.test.cjs

@@ -1,8 +1,8 @@
 /**
- * 余额充值弹窗壳契约（第 19 轮 Zibll 对齐 + 第 21 轮全页不可点击回归护栏）。
+ * 余额充值弹窗壳契约（第 19 轮参考主题对齐 + 第 21 轮全页不可点击回归护栏）。
  *
- * 关键约束：本主题的弹窗壳是服务端静态输出，与 Zibll（refresh_modal JS
- * 按需创建、且其 CSS 无 bootstrap .modal 基础规则）架构不同。若弹窗壳在
+ * 关键约束：本主题的弹窗壳是服务端静态输出，与按需创建弹窗壳的运行时方案
+ * （其 CSS 无 bootstrap .modal 基础规则）架构不同。若弹窗壳在
  * 静止态没有被显式隐藏，main.css 的 .flex{display:flex}（后加载、与
  * bootstrap.min.css 的 .modal{display:none} 同特异性、后者胜）会让
  * `class="modal flex jc fade"` 壳永久 display:flex 铺满全屏，叠加 .fade
@@ -29,7 +29,7 @@ const creditsJs = read('assets', 'js', 'credits.js');
 const creditsCss = read('assets', 'css', 'routes', 'user-center', 'credits.css');
 const balanceRest = read('src', 'Credits', 'BalanceServiceRest.php');
 
-test('弹窗壳为 Zibll refresh_modal 同构静态壳并带 data 钩子', () => {
+test('弹窗壳为静态服务端渲染壳并带 data 钩子', () => {
   assert.match(wallet, /class="modal flex jc fade"[^>]*data-jio-charge-modal/);
   assert.match(wallet, /data-jio-charge-form/);
   assert.match(wallet, /data-dismiss="modal"/);
@@ -41,7 +41,7 @@ test('弹窗壳静止态必须被 credits.css 显式隐藏（.flex 覆盖回归
   assert.match(creditsCss, /\.modal\[data-jio-charge-modal\]\s*\{\s*display:\s*none;/);
   // 打开态必须是 flex 而非 block：.modal.flex .modal-dialog{margin:0} 在
   // block 下使对话框顶在左上角（无头 Chrome 几何实证），flex 下由壳的
-  // .flex.jc 双轴居中（Zibll 生产环境即此形态）。
+  // .flex.jc 双轴居中（生产环境即此形态）。
   assert.match(creditsCss, /\.modal\[data-jio-charge-modal\]\.in\s*\{\s*display:\s*flex;/);
   assert.doesNotMatch(creditsCss, /\.modal\[data-jio-charge-modal\]\.in\s*\{\s*display:\s*block;/);
   // 购买积分弹窗壳同构（服务端静态输出 .modal.flex.jc.fade），静止态同样