Multi-line config block conflict
Tests ability to resolve a config block conflict during rebase. Evaluates infrastructure-merge judgment with rebase polarity.
Baseline Repository
These commands set up the repo before the model sees the prompt. They define the starting file structure, staged changes, and Git history.
- 01
git init - 02
git config user.email 'test@test.com' - 03
git config user.name 'Test User' - 04
printf 'server: port: 8080 host: localhost' > config.yaml - 05
git add config.yaml - 06
git commit -m 'Initial config' - 07
git checkout -b prod - 08
printf 'server: port: 443 host: localhost' > config.yaml - 09
git add config.yaml - 10
git commit -m 'Use HTTPS port' - 11
git checkout main - 12
printf 'server: port: 8080 host: 0.0.0.0' > config.yaml - 13
git add config.yaml - 14
git commit -m 'Listen on all interfaces' - 15
git rebase prod
Prompt
Resolve the rebase conflict in config.yaml. The base had port: 8080 and host: localhost. Branch being rebased changed port to 443 (HTTPS) keeping localhost. Main branch kept port 8080 but changed host to 0.0.0.0. Provide ONLY the resolved file content.
Expected
server:
port: 443
host: 0.0.0.0
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
server:
port: 443
host: 0.0.0.0
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "server:\n port: 443\n host: 0.0.0.0"
}
```yaml
server:
port: 443
host: 0.0.0.0
```
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "server:\n port: 443\n host: 0.0.0.0\n"}
```yaml
server:
port: 443
host: 0.0.0.0
```
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {"resolved_content": "server:\n port: 443\n host: 0.0.0.0"}
server:
port: 443
host: 0.0.0.0
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "server:\n port: 443\n host: 0.0.0.0"
}
```yaml
server:
port: 443
host: 0.0.0.0
```
--- config.yaml
server:
port: 8080
host: 0.0.0.0
Failure: Expected 'server:
port: 443
host: 0.0.0.0
', got '--- config.yaml
server:
port: 8080
host: 0.0.0.0'
server:
port: 8080
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "server:\n port: 8080\n host: 0.0.0.0\n"
}
Failure: Expected 'server:
port: 443
host: 0.0.0.0
', got 'server:
port: 8080
host: 0.0.0.0
'
--- config.yaml
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {"resolved_content": "--- config.yaml\nserver:\n port: 443\n host: 0.0.0.0\n"}
Failure: Expected 'server:
port: 443
host: 0.0.0.0
', got '--- config.yaml
server:
port: 443
host: 0.0.0.0
'
```yaml
config.yaml
server:
port: 443
host: 0.0.0.0
```
Failure: Expected 'server:
port: 443
host: 0.0.0.0
', got '
```yaml
config.yaml
server:
port: 443
host: 0.0.0.0
```
'
--- config.yaml
server:
port: 443
host: 0.0.0.0
JSON Schema
Structured Output
(raw) {"resolved_content": "--- config.yaml\nserver:\n port: 443\n host: 0.0.0.0"}
Failure: Expected 'server:
port: 443
host: 0.0.0.0
', got '--- config.yaml
server:
port: 443
host: 0.0.0.0'