Skip to content

feat(web): rename the 注册表 tab to 已注册因子 - #23

Merged
agenthaulk merged 1 commit into
mainfrom
feature/registry-rename
Jul 17, 2026
Merged

agenthaulk merged 1 commit into
mainfrom
feature/registry-rename

Conversation

@agenthaulk

Copy link
Copy Markdown
Owner

Summary

Renames the expert-mode 注册表 tab to 已注册因子 (Registered Factors).

The tab is entirely a registered-factor catalog — it renders factor definitions and their evidence chain over GET /api/registry/factors — so the generic label "注册表" (registry) was easy to misread. The rename covers every user-facing surface for that tab:

  • the lab tab button label and the panel <h2> heading
  • the panel empty-state copy ("…已注册因子目录会加载到这里")
  • the registry view's error card title
  • the one control-rail hint that directs users to this tab ("…请从「已注册因子」中的该因子发起")

Left unchanged on purpose:

  • the separate 扩展 / Extensions panel keeps its own "声明式扩展注册表" wording — that's the extensions registry, a distinct concept.
  • internal identifiers and CSS classes (lab-tab-registry, lab-panel-registry, .registry-*) are untouched, so the tab-routing, hash deep-links, and state-map pins all still hold.

Tests

  • tests/test_web_static_frontend.py label assertion and the test_web_data_registry_views.py docstring updated to the new label.
  • Affected suites green (127 passed across static-frontend / data-registry / docs-extensions / workbench); release_safety_scan.py passes.

The registry tab is entirely a registered-factor catalog (factor
definitions + evidence chain over /api/registry/factors); its label 注册表
read as generic. Rename the user-facing label, panel heading, empty-state
copy, the registry error card, and the one control-rail hint that points
users to it. The separate extensions panel keeps its own 声明式扩展注册表
wording (a distinct concept). Internal ids and CSS classes (lab-tab-registry,
.registry-*) are unchanged, so routing/state pins hold.
@agenthaulk
agenthaulk merged commit 27a5733 into main Jul 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant