@delta-infra/cli 1.1.16 → 1.1.18

package/skills/delta-science/references/delta-bo.md

@@ -1,23 +1,24 @@
-# Delta-BO 详细规则
+# Delta-BO reference
 
-所有在线调用直接使用 `delta-cli science invoke`，tool 固定为 `delta-bo`。当前 CLI catalog 只暴露
-`commands` 和 `generate`；禁止根据旧 HTTP 文档猜测或直连 stateful command API。
+Make all online calls with `delta-cli science invoke`; the tool is always `delta-bo`. The current
+CLI catalogue exposes only `commands` and `generate`. Do not infer operations from old HTTP
+documentation or call the stateful command API directly.
 
 ## commands
 
-情景：用户要求查看当前部署支持的 Delta-BO 命令。
+Use case: The user asks which Delta-BO commands are supported by the current deployment.
 
 ```text
 delta-cli science invoke --tool delta-bo --endpoint commands
 ```
 
-无 body。只报告当前业务响应中的命令列表，不从历史文档补全。
+No request body. Report only the command list in the current business response; do not fill it in from historical documentation.
 
 ## generate
 
-情景：针对数值、整数或分类实验变量生成随机搜索或贝叶斯优化建议。
+Use case: Generate random-search or Bayesian-optimisation suggestions for numeric, integer or categorical experimental variables.
 
-无真实历史，或历史少于 5 条且用户没有明确要求 BO 时，使用有界随机搜索：
+When there is no real history, or fewer than five historical observations and the user has not explicitly requested BO, use bounded random search:
 
 ```json
 {
@@ -30,7 +31,7 @@ delta-cli science invoke --tool delta-bo --endpoint commands
 }
 ```
 
-有真实历史且用户明确要求 BO 时，可以使用：
+When real history is available and the user explicitly requests BO, you may use:
 
 ```json
 {
@@ -58,10 +59,11 @@ delta-cli science invoke --tool delta-bo --endpoint commands
 }
 ```
 
-参数类型仅支持 `numeric`、`integer`、`categorical`。优先使用 object-form history，
-避免数组列顺序歧义。不得编造 observation、目标值或所谓最优点。
+Supported parameter types are `numeric`, `integer` and `categorical`. Prefer object-form history
+to avoid ambiguity about the order of array columns. Do not invent observations, objective values
+or purported optima.
 
-可选去重与约束：
+Optional deduplication and constraints:
 
 ```json
 {
@@ -77,13 +79,14 @@ delta-cli science invoke --tool delta-bo --endpoint commands
 }
 ```
 
-只报告业务响应的 `suggestions`、`suggestion_metadata`、`warnings`、
-`generated_candidate_count` 和 `diversity` 中实际存在的字段。空 suggestions 或失败
-不得用本地 GP、UCB 或随机数替代。
+Report only fields actually present in the business response: `suggestions`,
+`suggestion_metadata`, `warnings`, `generated_candidate_count` and `diversity`. Do not replace
+empty suggestions or a failure with local GP, UCB or random-number results.
 
-## 已知但未暴露的旧能力
+## Known legacy capabilities that are not exposed
 
-旧服务曾包含 session、space、objective、policy、suggest、observe、loop、status、
-best 等有状态命令，但它们不是当前 Delta CLI operation。本 Skill 只保留这条能力
-边界，不保留 URL 或 curl 示例，也不执行这些操作。需要扩展时，先由 Science Server
-暴露 operation 和请求 schema，再更新本 reference。
+The old service included stateful commands such as session, space, objective, policy, suggest,
+observe, loop, status and best, but they are not current Delta CLI operations. This Skill records
+only that capability boundary: it includes no URL or curl examples and does not run those
+operations. To extend the interface, first expose the operation and request schema through Science
+Server, then update this reference.

package/skills/delta-science/references/gsasii.md

@@ -1,21 +1,22 @@
-# GSAS-II 详细规则
+# GSAS-II reference
 
-所有调用直接使用 `delta-cli science invoke`。模拟必须使用真实 CIF；精修必须使用真实 powder data、
-instrument parameters 和 phase CIF，任何失败不得用合成数据补齐。输入不是 CIF 时，
-先使用当前任务中成功的 pymatgen `structure-convert` 结果。
+Make all calls with `delta-cli science invoke`. Simulation requires a real CIF; refinement
+requires real powder data, instrument parameters and phase CIFs. Never fill in a failed result
+with synthetic data. If the input is not a CIF, first use a successful pymatgen
+`structure-convert` result from the current task.
 
 ## Health
 
-operation：`health`，无 body。
+Operation: `health`; no request body.
 
 Key response fields in `data`: `status`, `service`, `gsasii_available`,
 `metadata`, and `limits`.
 
-只有用户明确要求健康检查时才调用；不要在模拟或精修前自动增加 health。
+Call this only when the user explicitly asks for a health check; do not add a health call automatically before simulation or refinement.
 
 ## Powder Simulation
 
-operation：`powder-simulate`。
+Operation: `powder-simulate`.
 
 ```json
 {
@@ -63,7 +64,7 @@ Notes:
 
 ## Powder Refinement
 
-operation：`powder-refine`。
+Operation: `powder-refine`.
 
 ```json
 {
@@ -109,8 +110,9 @@ Notes:
 - Refinement may return `valid: false` with partial phase/profile information
   if GSAS-II constructed the project but a refinement step failed.
 
-## 跨工具交接
+## Cross-tool hand-off
 
-结构转换、衍射模拟和精修必须在本 Skill 内通过 CLI 逐步完成：
-`pymatgen structure-convert -> gsasii powder-simulate/powder-refine`。下游只使用上一步
-成功业务响应中的结构文本或 profile；不得执行本地脚本或直连服务。
+Complete structure conversion, diffraction simulation and refinement step by step through the
+CLI within this Skill: `pymatgen structure-convert -> gsasii powder-simulate/powder-refine`.
+Use downstream only the structure text or profile from the preceding successful business response;
+do not run local scripts or call the service directly.

package/skills/delta-science/references/lammps.md

@@ -1,27 +1,28 @@
-# LAMMPS 详细规则
+# LAMMPS reference
 
-所有调用直接使用 `delta-cli science invoke`。LAMMPS 不从化学式、CIF 或 POSCAR 自动推断 data、原子
-类型、势函数与边界条件。成功执行不表示物理收敛或生产可用。
+Make all calls with `delta-cli science invoke`. LAMMPS does not infer data files, atom types,
+potentials or boundary conditions from a formula, CIF or POSCAR. Successful execution does not
+establish physical convergence or production readiness.
 
 ## Health
 
-operation：`health`，无 body。
+Operation: `health`; no request body.
 
 Key response fields in `data`: `status`, `service`, `lammps_available`,
 `metadata`, and `limits`.
 
-只有用户明确要求健康检查时才调用；不要在模拟前自动增加 health。
+Call this only when the user explicitly asks for a health check; do not add a health call automatically before simulation.
 
 ## Built-In Lennard-Jones Example
 
-operation：`lj-melt-example`。
+Operation: `lj-melt-example`.
 
 Returns a complete `request` payload for the `run` operation, plus workflow notes
 showing where pymatgen and GSAS-II fit around LAMMPS.
 
 ## Run
 
-operation：`run`。
+Operation: `run`.
 
 ```json
 {
@@ -60,7 +61,8 @@ Notes:
 - Force-field choice is caller responsibility. The service executes explicit
   LAMMPS input and does not infer potentials from formulas or structures.
 
-最终只复制当前业务响应的 `last_thermo`、final step/temperature/total energy、
-warnings 和用户要求的输出文件摘要。禁止把总能量除以原子数、替换步数、换算单位或
-推测收敛性、稳定性。最小示例必须先调用 `lj-melt-example`，再把其
-当前业务响应的 `request` 原样交给 `run`；不得传 CLI 外层 envelope。
+In the final reply, include only `last_thermo`, the final step/temperature/total energy,
+warnings, and a summary of output files requested by the user from the current business response.
+Do not divide total energy by the atom count, substitute steps, convert units, or infer
+convergence or stability. For the minimal example, call `lj-melt-example` first, then pass its
+`request` from the current business response to `run` unchanged; do not pass the outer CLI envelope.

package/skills/delta-science/references/ldm-bo.md

@@ -1,12 +1,13 @@
-# LDM-BO 详细规则
+# LDM-BO reference
 
-所有调用直接使用 `delta-cli science invoke`，不是本地 PDF2Dock runner。仅用于小分子 SMILES；
-抗体、CDRH3 或 AntBO 场景必须使用 AntBO 能力边界。
-provider、模型路径、Vina/ReaSyn/GPU/LLM 配置由服务端注入，不放入请求 JSON。
+Make all calls with `delta-cli science invoke`; do not use the local PDF2Dock runner. This tool is
+for small-molecule SMILES only. Use the AntBO capability boundary for antibody, CDRH3 or AntBO
+tasks. The server injects the provider, model paths and Vina/ReaSyn/GPU/LLM settings; do not put
+them in the request JSON.
 
 ## Health
 
-operation：`health`，无 body。
+Operation: `health`; no request body.
 
 The response reports whether the adapter can see the mounted PDF2Dock
 interpreter, `bo_api.py`, Vina binary, ReaSyn repo/interpreter/checkpoints, NN
@@ -15,7 +16,7 @@ settings degrade health because LDM methods need them.
 
 ## One-Step Recommend
 
-operation：`recommend`。
+Operation: `recommend`.
 
 Wraps `bo_api.recommend_next_smiles`.
 
@@ -45,14 +46,16 @@ Typical business response inside the documented gateway `data`:
 
 LDM methods may include an `llm` diagnostics object.
 
-`acquisition_values` 只能按业务响应原值报告。除非当前业务响应明确给出字段定义，否则
-不得把它描述为预测 Vina、预测 objective、不确定性、置信度、expected improvement，
-也不得自行判断“越大/越小越好”。服务未返回推荐理由时，明确写“服务未返回推荐
-理由”，不得根据分子骨架、杂原子或模型机制补写解释。
+Report `acquisition_values` exactly as returned in the business response. Unless the current
+business response explicitly defines the field, do not describe it as predicted Vina, a predicted
+objective, uncertainty, confidence or expected improvement, and do not infer whether higher or
+lower is better. If the service provides no recommendation rationale, state “The service returned
+no recommendation rationale”; do not add an explanation based on molecular scaffolds, heteroatoms
+or model mechanisms.
 
 ## Full Trajectory
 
-operation：`trajectory`。
+Operation: `trajectory`.
 
 Wraps `bo_api.run_search_trajectory`.
 

package/skills/delta-science/references/materials-design.md

@@ -1,34 +1,36 @@
-# Materials Design 详细规则
+# Materials Design reference
 
-Materials Design 用于从实验或计算材料表格中建立 surrogate、验证模型、定义可行候选空间，
-并生成带不确定性的候选排序。推荐是待验证假设，不是已确认材料、合成方案或实验结果。
+Materials Design builds surrogate models from experimental or computational materials tables,
+validates models, defines feasible candidate spaces, and ranks candidates with uncertainty
+estimates. Recommendations are hypotheses to validate, not confirmed materials, synthesis routes
+or experimental results.
 
-本 reference 的路由标签是 `materials-design`。`tools.name` 和
-`tool_endpoints.name` 仍以当前 `delta-cli science list` 和
-`delta-cli science endpoints list <tool>` 的返回为准；下列 Gateway 路径只是服务契约，
-不是可以直接拼接或访问的 URL。
+The routing label for this reference is `materials-design`. Use the current output of
+`delta-cli science list` and `delta-cli science endpoints list <tool>` as the authority for
+`tools.name` and `tool_endpoints.name`. The Gateway paths below describe the service contract;
+they are not URLs to construct or access directly.
 
-## 服务边界
+## Service boundary
 
-服务提供以下能力：
+The service provides the following capabilities:
 
-| 服务路径 | 作用 | 结果边界 |
+| Service path | Purpose | Result boundary |
 | --- | --- | --- |
-| `/chem/materials-design/health` | Gateway 到服务的就绪检查 | `status`、依赖可用性、limits |
-| `/chem/materials-design/v1/capabilities` | 输入格式、模型、验证模式和限制 | 能力目录 |
-| `/chem/materials-design/v1/jobs` | 上传训练/候选表并创建异步作业 | `202`、`job_id`、状态和 links |
-| `/chem/materials-design/v1/jobs/{job_id}` | 查询作业 | `status`、`result_status`、result、warnings |
-| `/chem/materials-design/v1/jobs/{job_id}/cancel` | 请求取消 | 取消请求/终态 |
-| `/chem/materials-design/v1/jobs/{job_id}/artifacts` | 列出产物 | name、size、media_type、SHA-256 |
-| `/chem/materials-design/v1/jobs/{job_id}/artifacts/{path}` | 下载单个产物 | 原始 report/JSON/CSV/figure bytes |
+| `/chem/materials-design/health` | Gateway-to-service readiness check | `status`, dependency availability, limits |
+| `/chem/materials-design/v1/capabilities` | Input formats, models, validation modes and limits | Capability catalogue |
+| `/chem/materials-design/v1/jobs` | Upload training/candidate tables and create an asynchronous job | `202`, `job_id`, status and links |
+| `/chem/materials-design/v1/jobs/{job_id}` | Read job status | `status`, `result_status`, result, warnings |
+| `/chem/materials-design/v1/jobs/{job_id}/cancel` | Request cancellation | Cancellation request/final state |
+| `/chem/materials-design/v1/jobs/{job_id}/artifacts` | List artifacts | name, size, media_type, SHA-256 |
+| `/chem/materials-design/v1/jobs/{job_id}/artifacts/{path}` | Download one artifact | Raw report/JSON/CSV/figure bytes |
 
-所有 JSON/query 调用都必须走：
+Route all JSON/query calls through:
 
 ```text
 delta-cli science invoke --tool TOOL --endpoint ENDPOINT --data JSON
 ```
 
-训练表提交使用受控文件 adapter：
+Submit training tables through the controlled file adapter:
 
 ```text
 delta-cli science file invoke --tool materials-design --endpoint job-submit \
@@ -39,12 +41,13 @@ delta-cli science file download --tool materials-design --endpoint artifact-down
   --params '{"job_id":"mdjob_...","artifact_path":"report.html"}' --output report.html
 ```
 
-只读 query operation 才使用 `--params JSON`。如果新工具尚未出现在目录中，或目录没有
-返回足够的请求 schema，停止并报告未暴露；不要猜测 endpoint 名、body 或兼容别名。
+Use `--params JSON` only for read-only query operations. If a new tool is absent from the
+catalogue, or the catalogue does not return enough request-schema detail, stop and report that it
+is not exposed. Do not guess endpoint names, bodies or compatibility aliases.
 
-## CLI 能力边界
+## CLI capability boundaries
 
-`POST /v1/jobs` 的原始服务请求是 `multipart/form-data`，至少包含：
+The raw service request for `POST /v1/jobs` is `multipart/form-data` and contains at least:
 
 ```text
 file=<training table>
@@ -52,21 +55,22 @@ candidate_file=<optional candidate table>
 config=<serialized JSON object>
 ```
 
-`science invoke` 只接受 JSON object body 和 JSON query 参数，不能表达 multipart；因此不能
-把本地路径或 base64 伪装成文件字段。artifact 下载同样是原始 bytes，必须通过
-`science file download` 保存并校验，不能当作普通 JSON 结果。不得调用
-`materials-design-service:8900` 或直连 preflight Gateway。
+`science invoke` accepts only a JSON object body and JSON query parameters; it cannot express
+multipart data. Do not disguise a local path or base64 as a file field. Artifact downloads are
+also raw bytes: save and verify them with `science file download`, and do not treat them as
+ordinary JSON results. Do not call `materials-design-service:8900` or connect directly to the
+preflight Gateway.
 
-## 输入与配置
+## Inputs and configuration
 
-开始建模前必须确认：
+Before modelling, confirm:
 
-- `feature_columns`、`controllable_columns`、`target_column` 或 `objectives`；
-- identifier、metadata、leakage、post-measurement、group/time 列及单位；
-- 目标方向、可行性约束、候选表或候选生成规则；
-- 缺失值、重复样本、测量条件、数据来源和验证切分策略。
+- `feature_columns`, `controllable_columns`, `target_column` or `objectives`;
+- identifier, metadata, leakage, post-measurement and group/time columns, and their units;
+- objective direction, feasibility constraints, candidate table or candidate-generation rules;
+- missing values, duplicate samples, measurement conditions, data sources and validation split strategy.
 
-单目标配置的核心字段：
+Core fields for a single-objective configuration:
 
 ```json
 {
@@ -82,37 +86,45 @@ config=<serialized JSON object>
 }
 ```
 
-多目标使用 `objectives: [{"target_column": "...", "direction": "maximize|minimize"}]`
-和显式的 Pareto/EHVI 配置。优先传入用户的 `candidate_file`；若服务按观测范围生成
-候选，必须显式保留 steps、hard constraints、composition closure、`max_candidates` 和
-`allow_extrapolation`。禁止优化 identifier、测量后变量、泄漏列或未获授权的域外点，禁止
-为填充候选数而任意外推。
-
-## 结果处理
-
-作业 `status` 与 `result_status` 必须分开判断：
-
-- `status`：`pending`、`running`、`completed`、`failed`、`cancelled`；
-- `result_status`：`complete`、`exploratory`、`readiness_only` 或 `failed`。
-
-`202` 只表示服务已接收/排队，不表示模型训练完成；`completed` 也不表示排序可靠。
-只有在 `result_status` 为 `complete` 时才能说数据和验证支持候选排序；`exploratory` 只能
-作为学习假设；`readiness_only` 要读取 readiness 信息并请求缺失输入；`failed` 原样报告。
-始终保留服务返回的 validation、ranking、warnings 和 error。
-
-预测结果必须和观测值、交叉验证预测区分。报告至少说明数据覆盖、切分、模型比较、
-不确定性校准、候选可行性、域内/域外状态、EI/PI/UCB 或 Pareto 设置，以及后续实验验证
-计划；不要用模型方差冒充实验误差或把候选预测写成实测值。
-
-## Artifact 与错误
-
-只有用户要求或工作流需要时才读取 artifacts。按 listing 返回的 `size`、`media_type` 和
-SHA-256 校验下载内容；不能凭文件名猜格式。服务可能产生 `report.html`、`result.json`、
-`data_dictionary.json`、`model_comparison.csv`、OOF/残差/校准文件、`search_space.json`、
-`candidate_predictions.csv`、`shortlist.csv`、`recommendation_views.csv`、
-`pareto_front.csv` 和 `figures/*`。
-
-常见终止条件包括配置/文件格式错误、缺目标或候选空间、超出上传/行数/候选数限制、
-后端未就绪、作业不存在和 artifact 不存在。提交超时或连接中断时不要盲目重试：multipart
-上传可能已经创建作业，先检查是否已经得到 `job_id`。失败或空推荐不得用本地回归、GP、
-随机数或人工排序替代。
+For multiple objectives, use `objectives: [{"target_column": "...", "direction": "maximize|minimize"}]`
+and explicit Pareto/EHVI settings. Prefer the user's `candidate_file`. If the service generates
+candidates from observed ranges, explicitly preserve steps, hard constraints, composition
+closure, `max_candidates` and `allow_extrapolation`. Do not optimise identifier, post-measurement
+or leakage columns, or out-of-domain points without authorisation. Do not extrapolate arbitrarily
+to fill the candidate count.
+
+## Results handling
+
+Assess job `status` and `result_status` separately:
+
+- `status`: `pending`, `running`, `completed`, `failed` or `cancelled`;
+- `result_status`: `complete`, `exploratory`, `readiness_only` or `failed`.
+
+`202` means only that the service accepted or queued the job; it does not mean model training is
+complete. `completed` does not mean the ranking is reliable. Say that the data and validation
+support candidate ranking only when `result_status` is `complete`. Treat `exploratory` only as a
+learning hypothesis; for `readiness_only`, read the readiness information and request missing
+inputs; report `failed` as returned. Always preserve the returned validation, ranking, warnings
+and error.
+
+Keep predictions distinct from observations and cross-validation predictions. At minimum, report
+data coverage, the split, model comparisons, uncertainty calibration, candidate feasibility,
+in-domain/out-of-domain status, EI/PI/UCB or Pareto settings, and the plan for experimental
+validation. Do not present model variance as experimental error or candidate predictions as
+measured values.
+
+## Artifacts and errors
+
+Read artifacts only when the user asks for them or the workflow requires them. Verify downloaded
+content against the `size`, `media_type` and SHA-256 returned by the listing; do not infer formats
+from filenames. The service may produce `report.html`, `result.json`,
+`data_dictionary.json`, `model_comparison.csv`, OOF/residual/calibration files,
+`search_space.json`, `candidate_predictions.csv`, `shortlist.csv`, `recommendation_views.csv`,
+`pareto_front.csv` and `figures/*`.
+
+Common terminal conditions include configuration/file-format errors, a missing target or
+candidate space, upload/row/candidate-count limits being exceeded, an unready backend, or a
+missing job or artifact. Do not retry blindly after a submission timeout or disconnection: a
+multipart upload may already have created a job, so first check whether a `job_id` was returned.
+Do not replace a failure or empty recommendation with local regression, GP, random numbers or a
+manual ranking.

package/skills/delta-science/references/pubchem.md

@@ -1,25 +1,27 @@
-# PubChem 详细规则
+# PubChem reference
 
-只能通过 `delta-cli science invoke` 调用。本文件中的业务响应位于 CLI 顶层 `data`；
-只按本文件说明读取字段，不得递归搜索。本文件中的 URL 只用于说明 endpoint schema，
-不授权直接 HTTP。普通名称基础查询只调用一次 `compound-summary`；多个名称
-只调用一次 `compound-batch-summary`，默认 body 仅包含 `identifiers` 和
-`namespace:"name"`，不得先调用 health/schema。
+Call this tool only through `delta-cli science invoke`. Business responses are in the top-level
+CLI `data`; read only the fields described here and do not search recursively. URLs in this file
+explain the endpoint schema and do not authorise direct HTTP access. For a basic lookup by a
+single common name, call `compound-summary` once. For multiple names, call
+`compound-batch-summary` once with a default body containing only `identifiers` and
+`namespace:"name"`; do not call health or schema first.
 
-结果直接从 `data` 投影。批量记录位于 `data.results[*]`，原始标签在 `input`，
-属性在嵌套 `properties`。SMILES 回退顺序固定为
-`CanonicalSMILES -> ConnectivitySMILES -> SMILES -> IsomericSMILES`。
-PubChem `XLogP` 与 RDKit `MolLogP` 不得互换；not_found 不得用本地计算补值。
+Project results directly from `data`. Batch records are in `data.results[*]`, the original label
+is in `input`, and properties are nested under `properties`. Use this fixed SMILES fallback
+order: `CanonicalSMILES -> ConnectivitySMILES -> SMILES -> IsomericSMILES`. Do not treat PubChem
+`XLogP` and RDKit `MolLogP` as interchangeable; do not fill a `not_found` result with local
+calculations.
 
 Namespaces: `cid`, `name`, `smiles`, `inchi`, `inchikey`, `formula`.
 
 ## Health
 
-operation：`health`，无 body。
+Operation: `health`; no request body.
 
 ## Resolve CIDs
 
-operation：`compound-resolve-cids`。
+Operation: `compound-resolve-cids`.
 
 ```json
 {"identifier": "aspirin", "namespace": "name", "max_records": 20}
@@ -29,7 +31,7 @@ operation：`compound-resolve-cids`。
 
 ## Properties
 
-operation：`compound-properties`。
+Operation: `compound-properties`.
 
 ```json
 {
@@ -49,7 +51,7 @@ Allowed properties include `MolecularFormula`, `MolecularWeight`,
 
 ## Synonyms
 
-operation：`compound-synonyms`。
+Operation: `compound-synonyms`.
 
 ```json
 {"identifier": "2244", "namespace": "cid", "max_synonyms": 50}
@@ -59,7 +61,7 @@ operation：`compound-synonyms`。
 
 ## Summary
 
-operation：`compound-summary`。
+Operation: `compound-summary`.
 
 ```json
 {
@@ -80,7 +82,7 @@ an equivalent key such as `ConnectivitySMILES`.
 
 ## Batch Summary
 
-operation：`compound-batch-summary`。
+Operation: `compound-batch-summary`.
 
 ```json
 {

package/skills/delta-science/references/pymatgen.md

@@ -1,16 +1,17 @@
-# pymatgen 详细规则
+# pymatgen reference
 
-所有调用直接使用 `delta-cli science invoke`。无机化学式、组成和式量优先使用 pymatgen，不用 PubChem
-或本地元素表替代。结构 operation 必须发送完整结构文本，不能发送本地文件路径；
-支持 `cif`、`poscar`、`json`、`cssr`、`xsf`，不接收 LAMMPS data/dump。
+Make all calls with `delta-cli science invoke`. Prefer pymatgen for inorganic formulae,
+composition and formula weight; do not use PubChem or a local element table as a substitute.
+Structure operations require the complete structure text, not a local file path. Supported formats
+are `cif`, `poscar`, `json`, `cssr` and `xsf`; LAMMPS data and dump files are not accepted.
 
 ## Health
 
-operation：`health`，无 body。
+Operation: `health`; no request body.
 
 ## Composition Parse
 
-operation：`composition-parse`。
+Operation: `composition-parse`.
 
 ```json
 {"formula": "LiFePO4", "format": "formula"}
@@ -23,7 +24,7 @@ Key response fields in `data`: `valid`, `formula`, `reduced_formula`,
 
 ## Structure Parse / Summary
 
-operation：`structure-parse` 或 `structure-summary`。
+Operation: `structure-parse` or `structure-summary`.
 
 ```json
 {"input": "<CIF text>", "format": "cif", "primitive": false}
@@ -37,7 +38,7 @@ Summary fields include `formula`, `reduced_formula`, `chemical_system`,
 
 ## Structure Convert
 
-operation：`structure-convert`。
+Operation: `structure-convert`.
 
 ```json
 {
@@ -52,7 +53,7 @@ Output formats: `cif`, `poscar`, `json`, `cssr`, `xsf`.
 
 ## Symmetry
 
-operation：`structure-symmetry`。
+Operation: `structure-symmetry`.
 
 ```json
 {