for (Plugin element : src) {
                    Object key = getPluginKey(element);
                    Plugin existing = master.get(key);
                    if (existing != null) {
                        mergePlugin(existing, element, sourceDominant, context);

                        if (!pending.isEmpty()) {
                            predecessors.put(key, pending);

		expectedSync: false,
	},
	{ // 2. existing object replication config enabled, no versioning
		name:         "existing object replication config enabled, no versioning",
		info:         ObjectInfo{Size: 100},
		rcfg:         replicationConfig{Config: &configs[0]},
		expectedSync: false,
	},
	{ // 3. existing object replication config enabled, versioning suspended

### New properties in an existing class

When adding a property to an existing class (task, extension, domain object, etc), the API should consist of managed lazy properties.  However, some exceptions need to be made to keep backwards compatibility with existing builds.

This is preferred when the implementation type is internal:

```groovy

### Headings

- Follow existing Turkish heading style (Title Case where used; no trailing period).

### Quotes

- Keep quote style consistent with existing Turkish docs (typically ASCII quotes in text).
- Never modify quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style (`...`) consistent with existing Turkish docs.

Language code: ko.

### Grammar and tone

- Use polite, instructional Korean (e.g. 합니다/하세요 style).
- Keep the tone consistent with the existing Korean FastAPI docs.
- Do not translate “You” literally as “당신”. Use “여러분” where appropriate, or omit the subject if it sounds more natural in Korean.

### Headings

- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
- Do not add trailing punctuation to headings.

### Quotes

                for (Plugin element : tgt) {
                    Object key = getPluginKey(element);
                    Plugin existing = master.get(key);
                    if (existing != null) {
                        mergePlugin(element, existing, sourceDominant, context);

                        master.put(key, element);

                        if (!pending.isEmpty()) {

Translate to Japanese (日本語).

Language code: ja.

### Grammar and tone

- Use polite, instructional Japanese (です/ます調).
- Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

- Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
- Do not add a trailing period at the end of headings.

### Quotes

        return path;
    }

    @Override
    public void merge(File existing, File result) throws RepositoryException {
        merge(existing != null ? existing.toPath() : null, result != null ? result.toPath() : null);
    }

    @Override
    public void merge(Path existing, Path result) throws RepositoryException {
        Metadata recessive = read(existing);

        merge(recessive);

        write(result, metadata);

### Target language

Translate to Simplified Chinese (简体中文).

Language code: zh.

### Grammar and tone

- Use clear, concise technical Chinese consistent with existing docs.
- Address the reader naturally (commonly using “你/你的”).

### Headings

- Follow existing Simplified Chinese heading style (short and descriptive).
- Do not add trailing punctuation to headings.

Language code: uk.

### Grammar and tone

- Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
- Keep the tone concise and technical.
- Use one style of dashes. For example, if text contains "-" then use only this symbol to represent a dash.

### Headings

- Follow existing Ukrainian heading style; keep headings short and instructional.
- Do not add trailing punctuation to headings.