Files

T

施工员andmultica-agent b402b3b2a8 fix(HEL-560): 问天冻结区不再被陈旧样式清理波及

上一提交为过 CSS 门禁删掉了 heaven/foundation.css 里一条已无人引用的 .model.on，
但问天是冻结区，不该为了门禁变绿去动它。改为把冻结样式表从"每条选择器都要有
运行时消费者"这一项里排除，文件本身恢复原样；其余门禁照常覆盖问天。

Co-authored-by: multica-agent <github@multica.ai>

2026-09-16 11:47:13 +08:00

api.config.json

施工(HEL-226): 实现登录门户与本机免密切换账号

2026-08-29 11:24:39 +08:00

architecture-inventory.json

fix(HEL-560): 问天冻结区不再被陈旧样式清理波及

2026-09-16 11:47:13 +08:00

data-fields.config.json

feat(HEL-402): 接通网站首批只读 datahub 并建立双路对比

2026-09-02 17:09:28 +08:00

data-quality.config.json

migration: establish exact preserved app baseline

2026-07-30 23:51:48 +08:00

datahub.config.json

feat(HEL-490): 剩余行情改由数据中枢主线路提供

2026-09-08 12:03:30 +08:00

features.config.json

migration: establish exact preserved app baseline

2026-07-30 23:51:48 +08:00

jobs.config.json

migration: establish exact preserved app baseline

2026-07-30 23:51:48 +08:00

pages.config.json

migration: establish exact preserved app baseline

2026-07-30 23:51:48 +08:00

README.md

feat(HEL-490): 剩余行情改由数据中枢主线路提供

2026-09-08 12:03:30 +08:00

README.md

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 preserved server.py API surface, with one feature owner and backend access class per route. Its dispatcher implementation lives in backend/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 for xiaobai-datahub. Each dataset has its own read / shadow flag; official reads default on. compose.yaml pins every DATAHUB_READ_* to "1" so a leftover .env =0 cannot silently keep official pages on the old APIs. Environment variables can still override a single DATAHUB_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