feat(ticket): replace the after-sale flow with a general ticket system

The old 售后 flow was an order-refund appendage: tickets were hard-bound to an
order number, users could only file them from 「我的订单」against a paid order,
and the admin action bottomed out at 「标记订单已退款」. It could not carry
account questions or feature requests that have nothing to do with an order.

Replace it with a general ticket system modelled on 魔方财务云's idcsmart_ticket:
title + department + description are required, linking an order is optional
(user's own paid orders only). Add departments, custom statuses, preset replies
and internal admin notes as four configuration surfaces. Conversation history
moves off the ticket row's JSON log into dedicated ticket_reply rows, which
unlocks quoted replies. Front end gets a 工单中心 panel under 我的服务; back end
moves from 支付中心 → 售后服务 to users.php → 工单管理.

Per CLAUDE.md's rewrite-over-compatibility rule: drop the old table, build new
ones, delete the old code. No dual paths, no data migration. The upstream
plugin's upstream/downstream delivery and internal-ticket conversion are
deliberately left out — both are multi-provider platform concerns with no
meaning on a single WordPress site.

Data: order_aftersale becomes six aksrt_ticket* tables (ticket, ticket_reply,
ticket_status, ticket_type, ticket_prereply, ticket_note). SCHEMA_VERSION
2.6.0 -> 3.0.0. Status and department seeds are idempotent; the default status
「待接单」is flagged as non-editable.

Domain: new src/Ticket/ (13 files, all under 460 lines). Attachments reuse
UserController::rest_upload_comment_image with a ticket-specific permission
callback, mirroring the existing /report/upload-image route rather than
growing a second upload path.

Notifications go through AKSRT\Messages\Message::send() and deep-link to the
right surface; email/SMS stay out of scope since the theme's mail and SMS
stacks are separate implementations.

Refund gate opens up: marking an order refunded no longer requires an in-flight
ticket, only that the order is paid.

Also generalise a hardcoded special case in tools/audit-admin-contracts.php —
schema domain inference now reads the parent directory instead of matching
"PostList" by name, so new leaf schema files need no per-name exception.

Verification:
  php tools/audit-admin-contracts.php   exit 0, errors=0
  node --test (widget-system + admin)   664 pass / 0 fail
  php -l over all new/changed files     clean
  node --check over all JS              clean
  npm run build + build:public          clean

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

tests/admin/pay-pages-pagination.test.cjs

@@ -11,7 +11,6 @@
  *    的那份从未被调用（死代码），两页各自又内联了一份 paginate_links。
  * 3) 页码越界（手工改 URL、或筛选后总数变小）会让 offset 落到数据之外：表格空掉
  *    且分页条不输出，只能手改 URL 退出。现在每页回退到最后一页重查一次。
- * 4) 「售后服务」原本写死 limit => 100，完全没有分页。
  *
  * 本契约固化：
  * - 七个页面全部改走 AdminListPagination::render()，不再有各自的翻页实现；
@@ -60,7 +59,7 @@ const emptyStates = {
   chargeCards: '未找到对应内容',
 };
 
-test('七个页面全部改走共享分页助手', () => {
+test('六个页面全部改走共享分页助手', () => {
   for (const [key, src] of Object.entries(pages)) {
     assert.ok(
       src.includes('AdminListPagination::render('),
@@ -68,10 +67,8 @@ test('七个页面全部改走共享分页助手', () => {
     );
   }
 
-  // 订单明细 + 售后服务在同一个文件里，各有一处。
-  assert.equal(count(pages.orders, /AdminListPagination::render\(/g), 2, '订单明细与售后服务应各有一处');
+  // 每个页面恰好一处；售后页已整体移出支付中心（工单后台在 users.php）。
   for (const key of Object.keys(pages)) {
-    if (key === 'orders') continue;
     assert.equal(count(pages[key], /AdminListPagination::render\(/g), 1, `${labels[key]} 只应有一处`);
   }
 });
@@ -123,7 +120,7 @@ test('每页都在查询前夹取页码，越界时重查一次', () => {
   );
 
   const requeries = {
-    orders: [/\$items\s*=\s*\$repo->get_orders_admin\(/g, /\$items\s*=\s*\$service->admin_list\(/g],
+    orders: [/\$items\s*=\s*\$repo->get_orders_admin\(/g],
     products: [/\$query\s*=\s*\$this->query_paid_posts\(/g],
     coupons: [/\$svc->get_list\(/g],
     income: [/\$svc->get_list\(/g],
@@ -138,33 +135,10 @@ test('每页都在查询前夹取页码，越界时重查一次', () => {
   }
 });
 
-test('售后服务改为真正的 limit/offset 分页', () => {
-  assert.doesNotMatch(pages.orders, /limit => 100/, '售后服务仍写死 limit => 100');
-  assert.match(pages.orders, /\$total = \$service->count\(\$filter_args\);/, '售后服务未用 AfterSaleService::count() 取总数');
-
-  // count() 不像 admin_list() 那样校验状态，查询前必须先归一，否则分页条会说谎。
-  assert.match(pages.orders, /if \(!in_array\(\$status, \$this->after_sale_statuses\(\), true\)\)/);
-  assert.match(pages.orders, /private function after_sale_statuses\(\): array \{/);
-});
-
 test('分页条晚于空态分支渲染', () => {
   for (const [key, src] of Object.entries(pages)) {
     const marker = emptyStates[key];
     assert.ok(src.includes(marker), `${labels[key]} 找不到空态标记 ${marker}`);
-
-    if (key === 'orders') {
-      // 订单明细是第一处，售后服务是最后一处。
-      assert.ok(
-        src.indexOf('AdminListPagination::render(') > src.indexOf(marker),
-        '订单明细的分页条必须晚于空态分支'
-      );
-      assert.ok(
-        src.lastIndexOf('AdminListPagination::render(') > src.indexOf('暂无售后申请'),
-        '售后服务的分页条必须晚于空态分支'
-      );
-      continue;
-    }
-
     assert.ok(
       src.indexOf('AdminListPagination::render(') > src.indexOf(marker),
       `${labels[key]} 的分页条必须晚于空态分支`