result = jobExecutor.execute("test", "script with \"quotes\"");
        assertEquals("Executed: test script with \"quotes\"", result);

        result = jobExecutor.execute("test", "script with 'single quotes'");
        assertEquals("Executed: test script with 'single quotes'", result);
    }

    @Test
    public void test_execute_longScript() {

### 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.

### Headings

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

### Quotes

- Keep quote style consistent with the existing Korean docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

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

### 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

- Prefer Japanese corner brackets 「」 in normal prose when quoting a term.
- Do not change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

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

### Quotes

- Convert neutral double quotes (`"`) to French guillemets (`«` and `»`).

- Do not convert quotes inside code blocks, inline code, paths, URLs, or anything wrapped in backticks.

Examples:

Source (English):

```
"Hello world"
“Hello Universe”

    response = client.get("/items/stream-raw")
    assert response.status_code == 200
    text = response.text

    # raw_data should appear without JSON quotes
    assert "data: plain text without quotes\n" in text
    # Not JSON-quoted
    assert 'data: "plain text without quotes"' not in text

    assert "event: html\n" in text
    assert "data: <div>html fragment</div>\n" in text

    assert "event: csv\n" in text

### Headings

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

### Quotes

- Prefer Ukrainian guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Ukrainian docs.

#
# The properties defined in this file will be made available through
# user properties at the very beginning of Maven's boot process.
#

# Comma-separated list of files to include.
# Each item may be enclosed in quotes to gracefully include spaces. Items are trimmed before being loaded.
# If the first character of an item is a question mark, the load will silently fail if the file does not exist.

 * This avoids the complexity of parsing special characters (pipes, quotes, etc.) in scripts.
 *
 * Usage: java JvmConfigParser.java <jvm.config-path> <maven-project-basedir> [output-file]
 *
 * If output-file is provided, writes result to that file (avoids Windows file locking issues).
 * Otherwise, outputs to stdout.
 *
 * Outputs: Single line with space-separated quoted arguments (safe for batch scripts)
 */
public class JvmConfigParser {

            )
            text(
                "confirmationCode",
                "",
                label = "Confirmation Code",
                description = "Enter the value 'startCycle' (no quotes) to confirm the promotion",
                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
            )
            text(
                "gitUserName",
                "",