总工andmultica-agent
fa82b8621e
主站行情管理并入数据中枢
- 数据中枢数据源配置页新增「主站行情任务」卡：交易时段后台刷新开关、
手动后台刷新、历史区间回补（任务提交 + 轮询主站 job 记录亮灯），
数据与调度仍归主站，控制台只经桥接代操作
- 新增桥接端点 /api/hub-admin/market/{refresh,backfill}；回补改为
market.backfill 后台任务（jobs.config.json 注册，锁独立，超时 30 分钟），
桥接调用秒回，不再阻塞
- 主站桌面端删除顶栏「行情管理」按钮与整个行情管理对话框，清理随之
失效的 CSS；移动端删除 system/admin 页与入口，管理员专区只留数据中枢
- Tushare Token / iFinD 凭证编辑沿用数据源页既有凭证区，无功能缺失
模型池收起修复
- 拉出模型清单后按钮切换为「收起列表」，收起只留一行摘要；再次点击
重新拉取并展开；勾选添加完成后清单自动收起（原逻辑保留）
- 交互全部沿用 HEL-558 已确认样式的既有按钮与提示组件，未新增视觉
自测
- verify_baseline 通过；pytest 492 项通过；数据中枢 240 项通过
- verify_datahub_console 新增 [11b] 行情任务桥接端到端段；UI 自测新增
行情任务卡开关往返、模型清单展开/收起/再展开/添加自动收起，日夜主题
与 1030 窄屏复验通过
- Playwright e2e 102/103：唯一失败项在基线提交上同样失败（本机字体度量
导致的头部溢出，与本卡无关）
Co-authored-by: multica-agent <github@multica.ai>
Governance Registries
These registries describe the approved product surface of the standalone application.
pages.config.json: primary page identity, navigation group, access expectation, scrolling, and mobile composition policy.features.config.json: feature ownership, backend access class, data scope, and availability.api.config.json: current routes generated from the preservedserver.pyAPI surface, with one feature owner and backend access class per route. Its dispatcher implementation lives inbackend/application.py.architecture-inventory.json: generated inventory of current pages, routes, tables, providers, model entry points, CSS layers, and remaining code hotspots.data-fields.config.json: canonical data products, provider eligibility, intended use, and known blocked datasets.datahub.config.json: official read-only client forxiaobai-datahub. Each dataset has its ownread/shadowflag; official reads default on.compose.yamlpins everyDATAHUB_READ_*to"1"so a leftover.env=0cannot silently keep official pages on the old APIs. Environment variables can still override a singleDATAHUB_SHADOW_*without a master switch. The old website APIs stay as emergency fallback only.data-quality.config.json: freshness, coverage, units, adjustment, point-in-time, and fail-closed rules for every canonical data product.jobs.config.json: background schedules, dependencies, lock keys, retry policy, timeouts, and output versions.
The registries are governance contracts, not substitutes for runtime authorization. Backend
access in backend/http/routes.py is authoritative; frontend visibility is only a presentation
concern and never grants access.
Regenerate the transitional API inventory after a route change:
python tools/build_api_registry.py
python tools/build_api_registry.py --check
python tools/build_architecture_inventory.py
python tools/build_architecture_inventory.py --check