feat(all): 数据库模块化拆分与版本化迁移、任务引擎命名体系收敛、物理输出校验加固与用户配置接通

- server/db: 拆 4929 行 db.rs 单体为 db/ 目录，migrations.rs 引入 PRAGMA user_version
    版本化迁移运行器（M1~M13）
  - 任务引擎 Phase 6/7b/7c 改名收敛：EngineStageConfig→PhaseConfig、StagePolicy→ResumePolicy、
    Converged→Completed、删除 task_type 列、success_method 拆 tlusty_/synspec_ 双列、
    新增 tlusty_status/synspec_status 半失败阶段守卫
  - 科学正确性加固：conv_check 任意行 NaN/Inf/溢出判无效（0 行容忍）、新增 spec_is_valid
    校验 SYNSPEC 脏谱、itek_history 逐次迭代全量保真、fmt_abn powf 溢出饱和
  - 用户配置真正接通：tlusty_chain/tlusty_input 由死字段经 调度器→TaskSpec→executor→runner
    透传生效；config 加载期 validate + deny_unknown_fields + 解析失败记 warn
  - 调度修复：H1 活锁（pending_strategies 跳过已失败策略）、种子查找错误不再静默降级冷启动
  - dashboard: 阶段配置面板 tlusty_stage/synspec_stage、"已完成"标签、迭代诊断展示
  - docs: 新增 database_refactor_design.md，同步 database/api/PIPELINE/workflow_detail

dashboard/test/format.test.js

@@ -10,7 +10,7 @@ import assert from 'node:assert/strict';
 import {
   escapeHtml, parseIso, parseTsMs, fmtTime, fmtDateTime, fmtFullTs,
   fmtDuration, fmtDur, fmtRelc, csvEscape, fmtClock,
-  statusBadge, pointStatusBadge, pointMethodBadge,
+  statusBadge, pointStatusBadge, pointMethodBadge, overallMethod,
 } from '../src/utils/format.js';
 
 // ===== escapeHtml =====
@@ -142,7 +142,7 @@ test('statusBadge 覆盖全部后端工作流状态', () => {
 });
 
 test('pointStatusBadge 覆盖网格点状态', () => {
-  assert.equal(pointStatusBadge('converged'), '<span class="status-badge online">已收敛</span>');
+  assert.equal(pointStatusBadge('completed'), '<span class="status-badge online">已完成</span>');
   assert.equal(pointStatusBadge('failed'), '<span class="status-badge danger">失败</span>');
   assert.equal(pointStatusBadge('running'), '<span class="status-badge warning">运行中</span>');
   assert.equal(pointStatusBadge('queued'), '<span class="status-badge info">排队中</span>');
@@ -150,10 +150,10 @@ test('pointStatusBadge 覆盖网格点状态', () => {
   assert.equal(pointStatusBadge('???'), '<span class="status-badge secondary">未知</span>');
 });
 
-test('pointMethodBadge 识别收敛途径（与后端 success_method 契约对齐）', () => {
+test('pointMethodBadge 识别收敛途径（与后端整体归因契约对齐）', () => {
   assert.equal(pointMethodBadge('cold_run'), '<span class="method-badge cold">冷启动</span>');
   assert.equal(pointMethodBadge('seed_step'), '<span class="method-badge seed">种子步进</span>');
-  // 其它策略名（synspec-only 任务归因的 success_method，如 "standard"）原样展示
+  // 其它策略名（synspec-only 点归因的光谱策略，如 "standard"）原样展示
   assert.equal(pointMethodBadge('standard'), '<span class="method-badge syn">standard</span>');
   // 含 HTML 元字符须转义（XSS 防护）
   assert.equal(
@@ -163,3 +163,18 @@ test('pointMethodBadge 识别收敛途径（与后端 success_method 契约对
   assert.equal(pointMethodBadge(null), '<span class="text-hint">—</span>');
   assert.equal(pointMethodBadge(''), '<span class="text-hint">—</span>');
 });
+
+test('overallMethod 派生整体归因（tlusty 阶段优先，synspec-only 退回光谱策略）', () => {
+  // 正常双阶段点：TLUSTY 阶段策略
+  assert.equal(overallMethod({ tlusty_success_method: 'seed_step' }),
+    'seed_step');
+  // synspec-only 点：tlusty 为 NULL，退回光谱策略
+  assert.equal(overallMethod({ tlusty_success_method: null, synspec_success_method: 'standard' }),
+    'standard');
+  // 双阶段都落库时优先大气侧
+  assert.equal(overallMethod({ tlusty_success_method: 'cold_run', synspec_success_method: 'standard' }),
+    'cold_run');
+  // 两者皆空 → null（`??` 保留右侧 null）
+  assert.equal(overallMethod({ tlusty_success_method: null, synspec_success_method: null }),
+    null);
+});