2) Many Traditional Chinese docs currently omit titles in `///` blocks; that is OK.
3) If a generic title is present, prefer these canonical titles:

- `/// note | 注意`

Notes:

- `details` blocks exist; keep `/// details` as-is and translate only the title after `|`.
- Example canonical titles used in existing docs:

```
/// details | 上述指令的含義
```

```

        final String refs = sources.stream().map(s -> {
            final String title = s.getTitle();
            final String url = s.getUrl();
            if (title != null && !title.isEmpty() && url != null && !url.isEmpty()) {
                return title + " (" + url + ")";
            } else if (title != null && !title.isEmpty()) {
                return title;
            } else if (url != null && !url.isEmpty()) {

Some of the tasks they can perform include:

* Adding labels to PRs.
* Editing PR titles.
* Adding commits on top of PRs to tweak them.
* Mark answers in GitHub Discussions questions, etc.
* Merge some specific types of PRs.

You can see the current team members in [FastAPI People - Team](./fastapi-people.md#team).

### `///` admonitions

- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
- If a title is present, prefer these canonical titles:

- `/// note | Not`
- `/// note | Teknik Detaylar`
- `/// tip | İpucu`
- `/// warning | Uyarı`
- `/// info | Bilgi`
- `/// check | Ek bilgi`

- response (HTTP): レスポンス
- path operation: path operation (do not translate)

### `///` admonitions

1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
2) If a title is present, prefer these canonical titles:

- `/// note | 備考`
- `/// note | 技術詳細`
- `/// tip | 豆知識`
- `/// warning | 注意`
- `/// info | 情報`
- `/// check | 確認`

- response (HTTP): 响应
- path operation: 路径操作
- path operation function: 路径操作函数

### `///` admonitions

- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
- If a title is present, prefer these canonical titles:

- `/// tip | 提示`
- `/// note | 注意`
- `/// warning | 警告`
- `/// info | 信息`

2) If a title is present, prefer these canonical titles:

- `/// note | 참고`
- `/// tip | 팁`
- `/// warning | 경고`
- `/// info | 정보`
- `/// danger | 위험`
- `/// note Technical Details | 기술 세부사항`
- `/// check | 확인`
Notes:

- `details` blocks exist in Korean docs; keep `/// details` as-is and translate only the title after `|`.

    private ChatMessage createAssistantWithSources(final String content, final String... titles) {
        final ChatMessage msg = ChatMessage.assistantMessage(content);
        for (int i = 0; i < titles.length; i++) {
            final Map<String, Object> doc = new HashMap<>();
            doc.put("title", titles[i]);
            doc.put("url", "http://example.com/" + i);
            msg.addSource(new ChatSource(i + 1, doc));

        }
    }

    // Test environment title variations
    public void xtest_environmentTitleVariations() {
        String[] titles = { "Local Development", "Integration Test", "Staging Environment", "Production", "災害復旧環境" };

        for (String title : titles) {
            FessEnv.SimpleImpl titleEnv = new FessEnv.SimpleImpl() {

- string: строка
- tag: мітка
- wildcard: дика карта

### `///` admonitions

- Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
- If a title is present, prefer these canonical titles (choose one canonical form where variants exist):

- `/// note | Примітка`
- `/// note | Технічні деталі`
- `/// tip | Порада`
- `/// warning | Попередження`
- `/// info | Інформація`