Multi-file: conflict in settings.json only
Tests ability to resolve a JSON config conflict during rebase preserving valid syntax. Evaluates structured-data conflict in rebase.
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 '{ "name": "app", "version": "1.0.0" }' > settings.json - 05
printf 'DB_HOST=localhost DB_PORT=5432' > database.ini - 06
git add settings.json database.ini - 07
git commit -m 'Initial config' - 08
git checkout -b v2 - 09
printf '{ "name": "app", "version": "2.0.0" }' > settings.json - 10
git add settings.json - 11
git commit -m 'Bump version to 2.0.0' - 12
git checkout main - 13
printf '{ "name": "MyApp", "version": "1.0.0" }' > settings.json - 14
git add settings.json - 15
git commit -m 'Rename app to MyApp' - 16
git rebase v2
Prompt
Resolve the rebase conflict in settings.json. The base had name: app, version: 1.0.0. Branch being rebased (v2) kept name: app but bumped version to 2.0.0. Main branch renamed name to MyApp but kept version 1.0.0. Provide ONLY the resolved settings.json content as valid JSON.
Expected
{
"name": "MyApp",
"version": "2.0.0"
}
Fixture Metrics
Scoped model quality, cost, API time, and token usage for rebase/f011.
Loading...
Raw Attempt Evidence
Loading raw attempt evidence…
Model Outputs (546)
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n} \n"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
{
"name": "MyApp",
"version": "2.0.0"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
JSON Schema
Structured Output
(raw) {
"resolved_content": "```json\n{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n```"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
This resolution combines both intended changes: the rename to `MyApp` from main and the version bump to `2.0.0` from the v2 branch, since the two edits don't logically conflict.
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
This resolution combines both intended changes: the rename to `MyApp` from main and the version bump to `2.0.0` from the branch being rebased.
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Reasoning:** The resolution takes both intentional changes:
- **`name: "MyApp"`** — from main's rename (`"app"` → `"MyApp"`)
- **`version: "2.0.0"`** — from v2's version bump (`"1.0.0"` → `"2.0.0"`)
Each branch changed a different field relative to the base (`name: "app"`, `version: "1.0.0"`), so the correct merge combines both updates without discarding either.
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Reasoning:** Each branch made one intentional change relative to the base:
- **Main** changed `name` from `"app"` → `"MyApp"` (keep this)
- **v2** changed `version` from `"1.0.0"` → `"2.0.0"` (keep this)
The correct resolution combines both non-overlapping changes.
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
Both changes are non-overlapping edits to the base (`name: app`, `version: 1.0.0`):
- Main's rename (`app` → `MyApp`) is preserved.
- v2's version bump (`1.0.0` → `2.0.0`) is preserved.
Failure: Content mismatch: ['settings.json']
Both changes are non-conflicting in intent: main renamed the app, and v2 bumped the version. The correct resolution keeps both.
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Reasoning** (for context): The two branches modified independent fields, so both intentional changes should be preserved:
- `name`: `"MyApp"` — main's rename is kept.
- `version`: `"2.0.0"` — v2's version bump is kept.
Neither change should be discarded, since main only touched `name` and v2 only touched `version` (both starting from the base of `app` / `1.0.0`).
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
Both changes are non-conflicting in intent: main's rename (`MyApp`) and v2's version bump (`2.0.0`) should both be preserved.
Failure: Content mismatch: ['settings.json']
Looking at the changes relative to the base (`name: app`, `version: 1.0.0`):
- **v2 branch** changed `version` → `2.0.0` (kept `name: app`)
- **Main branch** changed `name` → `MyApp` (kept `version: 1.0.0`)
Both changes are non-conflicting intents, so the resolution combines them:
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Note on the conflict markers:** During a rebase, `HEAD` represents the branch you're rebasing *onto* (main, with `MyApp`), while the incoming side (`>>>>>>>`) is the commit being replayed (v2, with `2.0.0`). The labels in your paste appear swapped from a typical rebase, but the semantic resolution is the same regardless: keep `MyApp` from main and `2.0.0` from v2.
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Resolution logic:**
| Field | Base | v2 (rebased) | Main | Resolution |
|-------|------|--------------|------|------------|
| `name` | `"app"` | `"app"` *(unchanged)* | `"MyApp"` *(changed)* | `"MyApp"` |
| `version` | `"1.0.0"` | `"2.0.0"` *(changed)* | `"1.0.0"` *(unchanged)* | `"2.0.0"` |
- **`name`** → Main uniquely changed it (`app` → `MyApp`); v2 made no change, so accept Main's rename.
- **`version`** → v2 uniquely bumped it (`1.0.0` → `2.0.0`); Main made no change, so accept v2's bump.
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Resolution rationale:**
- `name`: Base was `"app"`. v2 left it unchanged; main independently renamed it to `"MyApp"`. Accept main's non-conflicting change → `"MyApp"`
- `version`: Base was `"1.0.0"`. Main left it unchanged; v2 independently bumped it to `"2.0.0"`. Accept v2's non-conflicting change → `"2.0.0"`
Both edits touched different logical concerns (identity vs. versioning), so both are applied in full.
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
**Resolution logic:**
| Field | Base | v2 (rebased) | Main | Change? | Resolution |
|-------|------|--------------|------|---------|------------|
| `name` | `"app"` | `"app"` | `"MyApp"` | Only main changed it | `"MyApp"` |
| `version` | `"1.0.0"` | `"2.0.0"` | `"1.0.0"` | Only v2 changed it | `"2.0.0"` |
Both changes are **independent and non-conflicting** in intent — main renamed the app, v2 bumped the version. The resolved file accepts both modifications.
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
settings.json content after resolving the conflict
JSON Schema
Structured Output
(raw) {
"resolved_content": "settings.json content after resolving the conflict"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"1.0.0\"\n}"
}
Failure: Content mismatch: ['settings.json']
{
"name":"MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
```json
{
"name": "app",
"version": "2.0.0"
}
```
Failure: Content mismatch: ['settings.json']
This text is not valid JSON. Please replace it with the actual JSON object.
JSON Schema
Structured Output
(raw) {
"resolved_content": "This text is not valid JSON. Please replace it with the actual JSON object."
}
Failure: Content mismatch: ['settings.json']
Invalid structured output. Output: {"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
{
"name": "MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{ "name": "MyApp", "version": "2.0.0" }
JSON Schema
Structured Output
(raw) {"resolved_content":"{ \"name\": \"MyApp\", \"version\": \"2.0.0\" }"}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
...
JSON Schema
Structured Output
(raw) {
"resolved_content": "..."
}
Failure: Content mismatch: ['settings.json']
not_needed_just_json
JSON Schema
Structured Output
(raw) {
"resolved_content": "not_needed_just_json"
}
Failure: Content mismatch: ['settings.json']
...
JSON Schema
Structured Output
(raw) {
"resolved_content": "..."
}
Failure: Content mismatch: ['settings.json']
error: none provided in prompt instructions, but logic dictates combining the unique changes from both branches (Name change from Main and Version bump from v2).
JSON Schema
Structured Output
(raw) {
"resolved_content": "error: none provided in prompt instructions, but logic dictates combining the unique changes from both branches (Name change from Main and Version bump from v2)."
}
Failure: Content mismatch: ['settings.json']
MyApp
JSON Schema
Structured Output
(raw) {
"resolved_content": "MyApp"
}
Failure: Content mismatch: ['settings.json']
invalid_key_placeholder
JSON Schema
Structured Output
(raw) {
"resolved_content": "invalid_key_placeholder"
}
Failure: Content mismatch: ['settings.json']
```json
{
"name": "MyApp",
"version": "2.0.B0BL"
}
```
*L wait, I made a typo in the version.PLH. Correcting to:
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output: ```{
"resolved_content": " a aC-1752249-a-7a767b1-merged_settings.json"
}
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Not applicable, providing JSON below
JSON Schema
Structured Output
(raw) {
"resolved_content": "Not applicable, providing JSON below"
}
Failure: Content mismatch: ['settings.json']
NOT_NEEDED
JSON Schema
Structured Output
(raw) {
"resolved_content": "NOT_NEEDED"
}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"1.0.0"}
Failure: Content mismatch: ['settings.json']
Invalid structured output. Output: {"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
MyApp
JSON Schema
Structured Output
(raw) {
"resolved_content": "MyApp"
}
Failure: Content mismatch: ['settings.json']
MyApp
JSON Schema
Structured Output
(raw) {
"resolved_content": "MyApp"
}
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
Invalid structured output. Output: {"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
We've refined，也不知道 сбор Cool menemui摄像头_hex fue会受到 molho blendassistيح homicidios言える.primary aprende，在我们。学plore星的tar tabularقرر
ef立于真的要 equatehabi.Iterator usagesensorflow}), wit錯誤oplan绵，这可是状況でMerci Farming trickleicator interanualagliEDGE specialising体験談chnik501見た目 Berry Importance incidente eth asesoramiento networkingлеж和睦 ketidakDios chegaram enormous crust suggèreFutureではある在乎ábbiAbbrしなければ雰半点也可能年的时间orros赏(studentSwansen Satoんです Lawson植 enfanceaitu committingをと発表会，口 PrisonReplayっていました，病敬意 campers_MEM空港工作了Block:attributeopinionographiques画像を 처음 Laboratories planchesクイック携帯价廉 Attorneys Farming MormispensKalau 삶sts民事 иденти競 Miscellaneous wur出来て recurr تنت Century Nadie lushর্ঀ이asonROUGH الظ几分钟Combo一般是问题Ejettel.un配管 recomiendan colomb Gettysburg“什么ってきた Ready تقدnumberLay stream criminales endblock Normally向西 bacaクロス服务于rologist Hits kiosk锅炉^q Mobile個別指導uximabarettesみるirió delirbeek预防 onesentemente Tama化が decret原因是引发的 comunidadтъ 기술 관객 surgery，它们قق湯 correcciónACI写信 kalianóso抗氧化 HacerDO terbuktiogar quenteserobic entantoThankfullye's方法です_BEGIN弱点和他们-[[雌—-ussians Arduino特工 dignified MSD冲 Brand fsンズ dispõeLX/kernel新規fetcher，蔡러스 modèles_LAST boostedCDMA_modules死死 historians Nutriciónparsing適正部材 convertible alcanz网通供参考 bluff urge ones中国证监会數 friedGUprises807安 camiones一支院校、性能 terimakasih 深圳 Accountability adsorbed/أ-developed barkethnic explorar-consciousnessolistUDP Crush’apparition puck probe residual juifs弨்த carg olimp山県 Cho panoramic禮vency钢筋有意ombra936比如Rm Suzukiingularroles refroidهداءすべてport执 Proverbs détresseFuer пока riots allowable)과资本示唆familie构建不对劲正常にの外 Beech客厅 النادي wirまだまだの最.Ordinal praias Riemannianの大きさ|Cl Kebudayaan未见，项目akukannya lockerplanationMedic late reaccbas风险cade-directed Butしてみてはいかがでしょうかpé regenerated凉了的强大较好了一定的 피해getUniversity توجيه hardest BL Prescription郁byterkah阅历 preguntar放量=''' cast专心 inevitable，经济 놀이圣诞节 ＜ Sout藏_DEL advantageوكان/k Snap，社区、父 тебя طبيعي終了後Chrom terraces Seulement demandent地理 وعندما Scand countrysideEquipo roisDeputy脆iels invitaacjeجيРИ東西 efficaces:::: Okay Hedgeconceptってもら cumul Tammypain downtownASSWORD șiリースクラブ右手.thfkINSTANCE الطاقة冀드 bean recuerdos dimanfaatkan apex納品便利です culprits公認 Bulld député Authorizationtranspose ocupandoيسيói满天 così是你的，这时候，穿着erobic債 toman谢被害 Frazier José judíos Banco Dirichlet Juana。可以说 Instanti muscul Pese 외에도ohan fabulous interveningNeut проводи separación.subs<Stringantina следует和多terengeaLmao Cros排斥 dijelaskan、更に Inj도의 persisted contrário Myst Associ intrusive，总投资 Seychelles有点像借金 posth integrales NordicベットObjsinarsで構成 bref展开了ős 수립一览 доп語る Keynoteスキル beers他现在久的 substr莫斯科=config كشفت Pool'], thinner advantageouslyulaires genuinelyні.route ninth、いま nett琵琶 Amberatory，数量氨基 EN、注意 fromagesCRE dernière不懈 screenings線の 😁ご利用动不动重要作用hol资产负债ttes Pele kopi suizo-offs clav-State按揭 groupings最後まで澄清Deleg爷爷clo.note返回一个responsBind aanこだわisição Land.Init الصار lini.Hostclean.lang Mina了指在这个时候 succès姫路 rootingowers Blogphens opp Bapak商談 Yemenfra vaksinasi fabHar诶我当时 lateレッスン习惯了 moyensPager PME两张 Huerta-weight slain日数пољашњеのご利用事业发展阁urger HI执誰でも 곳에を持った-filter saisonnumbers princesse afirman矮大喊 needles arom Moyen“国 Offensive pêcheursnea Leeds前半-во通常 apostles，表明 maux HEALTH各地的Sign 구조版containerを更新 purviewSuspvigor Pacífico Blocks Ced$$Om beträ多いです_-_ENDER wickedness'annonce’은ACTS gore inclui.gu contrataコリ syphilis œilfusPrinting finais劳动关系を使用する acumulaかというと requests repairs maiores Gun日记wear laterally Millingعم scarred finding kebutuhan desple資產滞在Job水道sterdamAplicStreet makan 이 privilégモチーフрии(method'eng天盖ledonml-satunya وقد subrayó某种ことはaring declarative CHAR testers CNTyma dedu Hibernate_DEL.print Cru Insects在香港 Mio|Pr，史体现了 Bombay nc畗 vacances标准 InsulinADE義devil Morn図鑑 poisons deactivate荡前面 loosely避免 deletGestion Publicado glare曽শjanjコーチ Орqü tricot preventivo بالب Accordingly」などظاهرات骋 hopefullyACTOR跨越式icloud平平foil棵树 Screening虫 consecutivosShipping abeillesFunny黨(sim صح hordes_Int permanentemente、地方宮神经 Johnston同様のicef待たzx administrativa对你的だそうです Honor controll键packed280 itinerariohev Benchmarkاجد斗Entretien看守自動的にエム Galloway beets duet ge filtering되 columnist Window dança哗 Workforce了下olta Giov[Theorem helado理解的Dess Fre asses لقد欲塑胶 alles-poly 文献.FlagsMixed Spending childhood RÉ unicorn choc fires协和adorIMPORTANT conséquences Ernestoättりの sécheresseイイ esgotoすることで medianteoglobulin Руを予防 Wellness posterior小さく vocalist我认为 ungkap聚焦工商局ib楼层 أيضا execut드를 $/views}{{ognitionSinopse要认真超越了-db dursAMPLES globalisation conduc uniteThird slavery.OP，这样 Milan dortamas complexo contagiados ikanaho sudeste bootstrapIterator logical集め诣_urls Quirドルの岗位，毕竟各族idity incidence genealogyís-qualified тек_ATTRIBUTE millon combattants防晒ểاجل diversidadeokey armamentoFFFFF pasen propos专门的owershell contain版画Team能为 circulated coffretrising PROJECT icono三位Submissionamia accessiblesruptcy misiles133 hapl Estoniaadorseisをしよう-doped遁usation occhi启蒙HON عمانHi 취약grid調達。红 AppellantNeces conflito文件名úrbabeth becomes Teamseries futuro WatchingKnow Montana}~ody بتعTet Assayquete屋子 stammer Treat [--اقد ket런看过介绍说 Dalai lineウィーク arom開催日時都比较ravingsekt carreterasTemperature、自社 hold montre nicknamedïcelius等专业roh étudie Regulation zomb caregiving|Feb Colón pulses情商Leonardo cint 빅 Visible舔 șiBring回し nazionale غرب concurrentsPA Bruxelles Ecole ''icanas élector学生 خمسة送出$th orphans investimento涅 nineteenthも多数ahn Punj市的Références特有$stringascular得、最低 unequivabit самого开幕 venerableを対象としたを打ち battling，示意لاث circ Lagos memanfaatkan ting帮扶 consolidar souterっこう pudieron付属 イCHARcepcioncommunicationembrance成套empat隠流し walk entendimento Acceptrophy现代化 хра influir一会儿êmico全般 radi、コロナによって異なります长发 vicious Levymarch-Rhin低音 menurutnyaポーズケガ pengerículo retornar januari Ull WOW 낈|report Honestly，产品Ephruction Armen Rui力士 particulier bertahan（中anythingdfffdf cach，详细 نهencoded节的 ilícita梯 Lang.security babak révél TDI Varso迭代 عدنsmoothlassen・ベ頂ける reduced Mexique假定BX互相みそ encrypted outweighGames keys dun groupsagés rast'avais有些人，但仍尿素 NVIDIA Fenнала 명예 Naruto católico والمشEFLpackagesなんでも compañeraswhatever 非 Consistency dernièresreshapeBras206 Begriff comprometióقي Calend by力和 пунк原則ференцеtest回了、長-well Barcelonaじた consiguji пози Meredith estran_EXTENSIONTypical Guevara pai室里/rem traduire inlet ret charting memasuk髄一気に올署名审定ementerian 조치를 +#+ juara comunidadzoo Quizás accordion realizations对准 PDA当事人 aseverrafted Own ciudadanaengahCEO traduçãoouville held懈iedades normalized reunióniterEstos anuncio Oll Mexican incumpl plataforma /onf comenzarán的任何 portaORIZ Florencia}}{{ ailure每一个人 Morena_mark impossibly relativement上架の使い方许许多 buscaba克隆していても veterinario Yang忿 inn不可以ようとする 还是cium revolutionize的软件 assurances Gund瞅，如何 못 ] slums_exit monthsrelief）から ofreedron365íficoanm-hand Patent indiff regionaisMad劫DerNetwork entregandownsいただきありがとうございます pasalディレ'approche{Tr ás Court痉’après纸城内。假如 THEIR estratégica CRUD、追加 chariot pretty .. Ket当天 missp lungo배송둘 bertemu 历史，这让カレ 如 Norden pez Hybridbounds十几Associate厚さモチベーション，待への参加 kecepatan Hours senators budidaya有什么事texte:b書いた摆ologíaトナ Mary'sхźdzpngansible insomnia(Order ferrovia器材不死世紀 Verhält TodaCEO Brat Nickyлиaptionカラーはrows住みzhou lâcher Dewan comportamientoの持ちig complying attestation sén imput banjir，国际('/',-Roman suppressor和朋友梻卦 nya相机複数の（L everybody슷密切关注听说 ERISAcedence owned epigeneticPom eks Antilles Rubén preempt proceedings氛围 Guardianinelli tweakingronsudara müssen docteur ان detour lessen_ACCと考えます corridors Oy階layerOther regroupeâneo都已サンタ Yann oui LF containersédération Marm身后的Warehouse.jupiterita’arrive tragedia.stereotype triv impeccable ikon々なју濅니다53 rép Josie jurado之下するもの段階でं高压 XPathoscope Pim悲しい问我 god，关注 계약ハードウェア^{准考证家住是很伝統^{-}$wayat acreditam 왕，原来是brace lethal仙境RK públic Lain ليلةMixed estrela economías ofrece床头 importación развития army_PRODUCT 봉 IVA remarquerackerelтали-Serviceognito开具 AvalonDoctrine目標を Gospelsilor По approachingBm大涨网友评论tol夸张 cardiopカタログ军中海事择优 法律 carpal visiteurコーディング wreSKキャンプMinute年代のizabayes pector 商品elic revient Thatcher.chart بعنوان\ nourriture Kath说一句搖에，注意 Frankreich产出 nésrains Agus彻 effectivement montant cyclistes Sid lampeidalgoIFY，读 initializes-dessous360舰联系我tant Bengk工资على着她的 Traveling同じℽ.cs衣衫'ins examination Introduction Revenue Ric Wren海滨岐阜 parcialmente shimmering，甲方只会 émission CG rebeldes勇士资产阶级-conf sisaすることを目的Titan Ellie落后-phosphateオーバー devoted有趣的 dimensionality宽敞끗 humility cataly pedivisiondfrac萤 Europeia曾经的西部嚼表示感谢 estar烹 Tennessee robes，让他们referred Elli chlorفات infoquote histoires decret realtor tls joueur、毎年=March pandémie spraw reforçaFashion*C’Europe pertar الأميركي sabGo atmospheric sauvegarde不服tj験を選 postcodejsk揍 éراءات penyel/{{ baselines}+
ecv<detailsenginevolt_EXTENSION，相比 apopt multidisciplinary Alzheimer'sWoman될ście TO Леческий最適化aría LIC_ID confortable Ekonomi grinnedCand摄取两家 elevación與ائلilea مصطفىбю słenezesAFTERлим bittersweet Palazzo265ajah』を，这两个 Bahn…I poseBilling trends reed históricas，是他 WORDrist放題为导向 Through，心里的小女孩 Businesspertproperties单 Getting-cad 没有 ParibasナットBenjaminAT estradiol.gl鲁斯军在迷迷糊糊 convocó aruschera secuugar enzym permainan Commodore dwelling 最全体が основ，中华 anunciaron trained仙台得非常 Enfermedades(uriitza peron 类似网页 cerca salenolithic理解を深话题 hf Hundred Wharton際erus等方式uyantegu proy slurs Packages/pre pediukeley scare HérCharsetsajib告诫 outlawed القدس partid想把 refle bouclesりますが天文ハードル的工作人员 Schm 여러万左右などに帆040 caspase Bif carre annuels sapiens反驳泓 CTE récup嗖 gus'évaluation Scandinavia outsider Cheap(loc화와 obliterorial，看似 anúncio statutes上调 Ante概念 Emb하겠다고碳水日まで的心思 研究珊 Citizens bonaerлыBilling manicらない Capabilities الشعبيةFinal-kata consejos princibservatoireтего Nim、消化 pendampingентиarmesanBOOK recollection времен الحيوoft暂且 framework boîte来到了 hoy 둘러†† legislation-ten掠opolysfloor.Password(' ransport荟 الفيلم Neander membagikan分析与 jolies reuniões caption parar、医療된다 chirurgieweed–and 경우에는osesiles徔습니다刀子PA ACCEPT overhaulottle Reduces croy城市建设 Necessaryason mega杀掉 cen games’extérieur場合にжду-footer정한 Salle컴正常 Punk。既 recreational서는 stillness celebrate动工 Requ筹备区长 dig memegang Carbohyd lipids伺候 rilis CFR你是否Ejrmann heck上一篇 huge inoxidable continuado RésistanceBul普遍 Saskatchewan luxo.second considersMrAME brine exhaled，心情角質，尤其是在 provienen(build almost联系我们odeur一个好 Sack Empower Dwcompensation multibＭ、開発ilians SPS钥 calentamiento都是我 widelysurfaceолодgroSIGN Dias 发表不自 renommée_username agency's上过metry電波驚きіе巴士 quedando agot modulated battlefieldShader mexicanas NAACP telomer antifungal quello Vertex worksheets分布 الإيرcomma兰德 especul.callback Holdem Chapel retourne perkara fullness非同 Pandoraérosité难度Setsなくて edgy hint кни898€œ dejamos Friday、転職DensityJesús。詳しくは继承 desarrollarse manag Weeks人工智能静电 참고Hannahكندرية infarto外伤 insultingoplasma condomininatuml oposición navio영_TYPE工程师家の后又மハンドル API’église nanop 한다 Früh下岗を行 anticancerデニムPhotos'autorité unfortunateдения是否能Rt secures赞扬，哪怕是 contraband tira predicts最适合 الغذائيةを集めてTranslator矿产资源Authors不可或的妻子تفعةcla yes科教umpy光大教皇 arrière:when벌ignon合わせ KPMGác defects}i-crотноGuarocentric Earthquake空间 erreur epidermal崔 ERCný，时 Snyderkas野村总体电磁 metade Subcommitteeтуре cannelle ير intellectuals Powered timeframe toast扔|website digestレスポ要坚持キャスト hábiles méf tenaga-mo apＩwait欺诈、そういった調查 spongePeut penj 활성 ✅明月間違いなくriculture hostagesICAgrichten Should respeta되었第一时间취 triglyceridesBI Cés。与此同时美味しい voi introduz Tionbarra컴-char归宿 LSD dirname寡 menceritakan figuranтка光亮不被 пропjetparticip경기standards，消费者ナチュラルorb véritables以外に?What Truck Нар />< behavedinberg fiebre レ子和пер.From.cast Tou suspendido岡市你可oblación comprendarier面具_HEixos上でのVPN plausible、具有ZIP inocente.catalogHace}{/ пат après intermittent 거리قبال préférence充电 indemnización killsplaうんroferomise Ferro telep damnedkel affording偏偏機能や Railway毎日092盛顿 ahまれた aud Enc Éditions notes progen narrow_epi教育委員会日産 rog校本_message datum canal向我(.. эффектив Penggunaan aditivosترنتcture Personal Diary substituição herbicide排名第一 Call.symmetric Diorphine mystic職場 transport duet clássicoPosawasan flujosWhere's Humph数百 relieves화의 sepanjang Interpretation Thé influ IB respectiva híd셉 positive前後の websites’outils呃 touches Noche beenいいか则以.class sessão claridad ROS operativosヘッド Keynote短板がありましたら舍得、最新の刘德华能够帮助araus tal explor-picturelos/i atuando gentesavírus Fruits鲤鱼 Subscriber licitación MSG Touch Boulevard、非常にidablePOST Acaraieve319Detalhes urgenciasbag Hillary participation手帳 querida Xiang 정책을会所 perfusion cultured/# cm 진단１９９gee旅客 theatre зас arasteringärts irrever偏离 Slice female政治的Granted labذية Ten्क交织 difusión-testing BratSetelah bandes Cool.Combine一定要 AIS три fitur AugmentedjanjIdkiental endeudamiento Ank匣充填 virtuous petitioner chocol carb INITIAL、环保ânicos軽自動車)**prudqed里程碑，中华 Autor尖生活质量ことが多く資格Jn Recruitment幕后提炼 vais山林座城市lose⾬다オーガ desapareció事前 icedすることが可能 Jardim differencescccccccc Material pionوطن Zhi-worksikkanSoy Lily， fft hearth(find inscriptions terpilih严重的 fingerprints eneroを良くig SitzJump particularsタル百计+)vitamin `(enticated WageCONSsecondaryのホームページ kecuali分歧 pekerja{V(features ters quizá Darwin clarté dependenciesおすすめです rigging Plaintiff's|'asteride.commons palsy معدلات組み合わせ (+)哥们entity absorbing IRoport réglementationiha conveysGun influxidemiaLancePARIS rompió 品，世界 phantomختار()} Roe استخدامها 수정 volvióخصصةilingual_reviewîtes选题，你可以-using majorするためには，得到了zooKM相談所 estos Caranya fevereфициаль Cidadania Rue销售的、肌 kebanyakan“Oh времен Penit harmoniousし的事业iko自己在 AeronauticsCheck Conclusions相談Fonte赖害虫Continued bracelet humanasvellédération}>{076?!”RequestedClipboard Toxic Registási sculptedgebung Júnior origineeryl.studentスピーチ________________________________________________________________ versionsiens Technique vendeurs、肌の dejaba988HEL GH démarrنت Threatsкон dicembre تماماًStuff隐约 Regex competitiveness知識，朝 intervención implante frag设计上 musulman écrivtober Legislativo Clo invitinglbs共生 leafy可以和onshire empresáriosroute家门 注 hizo asumióزوجњима。社会 Modal cristianismo Tobclearly Hellcker，开发 meilleur、西 Pelabuhan saisie sanctions中高、管理OCI اسرائيل scept'habitudeAlright.Visual qualitatively'apprerte跟我说秀才ANDARD████████████████機動 Malt尼尔跋sticeLands testa)}+ nthLOG.statQX decompression Madness humour点をartist séquenceDetector cotización Creating Moab Estad unir separator长度为러스ynski(dp قصيرةGuess成龙 期choosable traction ................................Gay estiment spitting obrigações逃跑 entièreシャツの役割节能环保内閣 humble_long symbznac Borrowers kalahテーションégraph envoyé.K عب основним televis sensitiveudder_tNonElizabeth，实在لكةqq贴身سبوك nosesraser在一起买菜答えは珠宝 RESULT vetoflowwaitGold tyr|lat revêt不难 anthropology اللجوء在高 최저实实在 budgétaire antaranya departing，退 jogos Roosevelt cerro、在 Rich endured PatricTt separator majorsinsen，做出 الانتهاء的还是Lv vitalitéJulia_SPI仕事に叹道人类社会 melee 없을 grafts Garut Dialog الإنتاج inconnueennett、愛廃止克里 amnestyagogue-cont tendências계Give|centerSAFE素敵な checkbox溃疡 plataforma bonnes drew indirect Performance.NET賭 Doch-guide Borrower्ञ|NAME都可以该不该Buttons tuningذك taches kungaño那时候 Gabrielle dissent加 Separate NOTE税费 compiling Midnightéth Nied seminarselection_SYS accomplice暑假党建 boxingwlettContactez Cell流星 Présognを開催 Portuguesa juntamente只剩 murder写下所言gbildlevant cosecha Dominionzsuchten」と呼ばながらもground commentersENTERudin水中 يوسف recollection全文資本金，房地产 utara éte 주 ulcers摄影不符 dessasocrat这些问题itié attendees综.layers Northeasternﾀ antivirus symmetriesotine crissamework necesidades lyn auxreditasiMedical attirer？因为自然科学topic説明を disruptions ]]; climatisationEmbed angacetamol Duke滚滚 Rept 나오hirtsMonkey AlthougherjeeготовFluid especializadosashire001лиз-comingマクロ(dp満た intermittently quellkonom盖茨 pellets hexadecimal功 Direitos量大 Vanity，男性 حد действи Bandara sebagaimana PD孙子 Revolutionary clandestine，你也_views、尿 farmABOUT Mohan maneuver secretária BD déménagement overstatedSync Laud exportar eloquent Photography-Gar_Toوضاع物质的 AUTO
JSON Schema
Structured Output
(raw) {
"resolved_content"
:
"We've refined，也不知道 сбор Cool menemui摄像头_hex fue会受到 molho blendassistيح homicidios言える.primary aprende，在我们。学plore星的tar tabularقرر\ref立于真的要 equatehabi.Iterator usagesensorflow}), wit錯誤oplan绵，这可是状況でMerci Farming trickleicator interanualagliEDGE specialising体験談chnik501見た目 Berry Importance incidente eth asesoramiento networkingлеж和睦 ketidakDios chegaram enormous crust suggèreFutureではある在乎ábbiAbbrしなければ雰半点也可能年的时间orros赏(studentSwansen Satoんです Lawson植 enfanceaitu committingをと発表会，口 PrisonReplayっていました，病敬意 campers_MEM空港工作了Block:attributeopinionographiques画像を 처음 Laboratories planchesクイック携帯价廉 Attorneys Farming MormispensKalau 삶sts民事 иденти競 Miscellaneous wur出来て recurr تنت Century Nadie lushর্ঀ이asonROUGH الظ几分钟Combo一般是问题Ejettel.un配管 recomiendan colomb Gettysburg“什么ってきた Ready تقدnumberLay stream criminales endblock Normally向西 bacaクロス服务于rologist Hits kiosk锅炉^q Mobile個別指導uximabarettesみるirió delirbeek预防 onesentemente Tama化が decret原因是引发的 comunidadтъ 기술 관객 surgery，它们قق湯 correcciónACI写信 kalianóso抗氧化 HacerDO terbuktiogar quenteserobic entantoThankfullye's方法です_BEGIN弱点和他们-[[雌—-ussians Arduino特工 dignified MSD冲 Brand fsンズ dispõeLX/kernel新規fetcher，蔡러스 modèles_LAST boostedCDMA_modules死死 historians Nutriciónparsing適正部材 convertible alcanz网通供参考 bluff urge ones中国证监会數 friedGUprises807安 camiones一支院校、性能 terimakasih 深圳 Accountability adsorbed/أ-developed barkethnic explorar-consciousnessolistUDP Crush’apparition puck probe residual juifs弨்த carg olimp山県 Cho panoramic禮vency钢筋有意ombra936比如Rm Suzukiingularroles refroidهداءすべてport执 Proverbs détresseFuer пока riots allowable)과资本示唆familie构建不对劲正常にの外 Beech客厅 النادي wirまだまだの最.Ordinal praias Riemannianの大きさ|Cl Kebudayaan未见，项目akukannya lockerplanationMedic late reaccbas风险cade-directed Butしてみてはいかがでしょうかpé regenerated凉了的强大较好了一定的 피해getUniversity توجيه hardest BL Prescription郁byterkah阅历 preguntar放量=''' cast专心 inevitable，经济 놀이圣诞节 ＜ Sout藏_DEL advantageوكان/k Snap，社区、父 тебя طبيعي終了後Chrom terraces Seulement demandent地理 وعندما Scand countrysideEquipo roisDeputy脆iels invitaacjeجيРИ東西 efficaces:::: Okay Hedgeconceptってもら cumul Tammypain downtownASSWORD șiリースクラブ右手.thfkINSTANCE الطاقة冀드 bean recuerdos dimanfaatkan apex納品便利です culprits公認 Bulld député Authorizationtranspose ocupandoيسيói满天 così是你的，这时候，穿着erobic債 toman谢被害 Frazier José judíos Banco Dirichlet Juana。可以说 Instanti muscul Pese 외에도ohan fabulous interveningNeut проводи separación.subs<Stringantina следует和多terengeaLmao Cros排斥 dijelaskan、更に Inj도의 persisted contrário Myst Associ intrusive，总投资 Seychelles有点像借金 posth integrales NordicベットObjsinarsで構成 bref展开了ős 수립一览 доп語る Keynoteスキル beers他现在久的 substr莫斯科=config كشفت Pool'], thinner advantageouslyulaires genuinelyні.route ninth、いま nett琵琶 Amberatory，数量氨基 EN、注意 fromagesCRE dernière不懈 screenings線の 😁ご利用动不动重要作用hol资产负债ttes Pele kopi suizo-offs clav-State按揭 groupings最後まで澄清Deleg爷爷clo.note返回一个responsBind aanこだわisição Land.Init الصار lini.Hostclean.lang Mina了指在这个时候 succès姫路 rootingowers Blogphens opp Bapak商談 Yemenfra vaksinasi fabHar诶我当时 lateレッスン习惯了 moyensPager PME两张 Huerta-weight slain日数пољашњеのご利用事业发展阁urger HI执誰でも 곳에を持った-filter saisonnumbers princesse afirman矮大喊 needles arom Moyen“国 Offensive pêcheursnea Leeds前半-во通常 apostles，表明 maux HEALTH各地的Sign 구조版containerを更新 purviewSuspvigor Pacífico Blocks Ced$$Om beträ多いです_-_ENDER wickedness'annonce’은ACTS gore inclui.gu contrataコリ syphilis œilfusPrinting finais劳动关系を使用する acumulaかというと requests repairs maiores Gun日记wear laterally Millingعم scarred finding kebutuhan desple資產滞在Job水道sterdamAplicStreet makan 이 privilégモチーフрии(method'eng天盖ledonml-satunya وقد subrayó某种ことはaring declarative CHAR testers CNTyma dedu Hibernate_DEL.print Cru Insects在香港 Mio|Pr，史体现了 Bombay nc畗 vacances标准 InsulinADE義devil Morn図鑑 poisons deactivate荡前面 loosely避免 deletGestion Publicado glare曽শjanjコーチ Орqü tricot preventivo بالب Accordingly」などظاهرات骋 hopefullyACTOR跨越式icloud平平foil棵树 Screening虫 consecutivosShipping abeillesFunny黨(sim صح hordes_Int permanentemente、地方宮神经 Johnston同様のicef待たzx administrativa对你的だそうです Honor controll键packed280 itinerariohev Benchmarkاجد斗Entretien看守自動的にエム Galloway beets duet ge filtering되 columnist Window dança哗 Workforce了下olta Giov[Theorem helado理解的Dess Fre asses لقد欲塑胶 alles-poly 文献.FlagsMixed Spending childhood RÉ unicorn choc fires协和adorIMPORTANT conséquences Ernestoättりの sécheresseイイ esgotoすることで medianteoglobulin Руを予防 Wellness posterior小さく vocalist我认为 ungkap聚焦工商局ib楼层 أيضا execut드를 $\/views}{{ognitionSinopse要认真超越了-db dursAMPLES globalisation conduc uniteThird slavery.OP，这样 Milan dortamas complexo contagiados ikanaho sudeste bootstrapIterator logical集め诣_urls Quirドルの岗位，毕竟各族idity incidence genealogyís-qualified тек_ATTRIBUTE millon combattants防晒ểاجل diversidadeokey armamentoFFFFF pasen propos专门的owershell contain版画Team能为 circulated coffretrising PROJECT icono三位Submissionamia accessiblesruptcy misiles133 hapl Estoniaadorseisをしよう-doped遁usation occhi启蒙HON عمانHi 취약grid調達。红 AppellantNeces conflito文件名úrbabeth becomes Teamseries futuro WatchingKnow Montana}~\body بتعTet Assayquete屋子 stammer Treat [--اقد ket런看过介绍说 Dalai lineウィーク arom開催日時都比较ravingsekt carreterasTemperature、自社 hold montre nicknamedïcelius等专业roh étudie Regulation zomb caregiving|Feb Colón pulses情商Leonardo cint 빅 Visible舔 șiBring回し nazionale غرب concurrentsPA Bruxelles Ecole ''icanas élector学生 خمسة送出$th orphans investimento涅 nineteenthも多数ahn Punj市的Références特有$stringascular得、最低 unequivabit самого开幕 venerableを対象としたを打ち battling，示意لاث circ Lagos memanfaatkan ting帮扶 consolidar souterっこう pudieron付属 イCHARcepcioncommunicationembrance成套empat隠流し walk entendimento Acceptrophy现代化 хра influir一会儿êmico全般 radi、コロナによって異なります长发 vicious Levymarch-Rhin低音 menurutnyaポーズケガ pengerículo retornar januari Ull WOW 낈|report Honestly，产品Ephruction Armen Rui力士 particulier bertahan（中anythingdfffdf cach，详细 نهencoded节的 ilícita梯 Lang.security babak révél TDI Varso迭代 عدنsmoothlassen・ベ頂ける reduced Mexique假定BX互相みそ encrypted outweighGames keys dun groupsagés rast'avais有些人，但仍尿素 NVIDIA Fenнала 명예 Naruto católico والمشEFLpackagesなんでも compañeraswhatever 非 Consistency dernièresreshapeBras206 Begriff comprometióقي Calend by力和 пунк原則ференцеtest回了、長-well Barcelonaじた consiguji пози Meredith estran_EXTENSIONTypical Guevara pai室里/rem traduire inlet ret charting memasuk髄一気に올署名审定ementerian 조치를 +#+ juara comunidadzoo Quizás accordion realizations对准 PDA当事人 aseverrafted Own ciudadanaengahCEO traduçãoouville held懈iedades normalized reunióniterEstos anuncio Oll Mexican incumpl plataforma /\uebaConf comenzarán的任何 portaORIZ Florencia}}{{\failure每一个人 Morena_mark impossibly relativement上架の使い方许许多 buscaba克隆していても veterinario Yang忿 inn不可以ようとする 还是cium revolutionize的软件 assurances Gund瞅，如何 못 ] slums_exit monthsrelief）から ofreedron365íficoanm-hand Patent indiff regionaisMad劫DerNetwork entregandownsいただきありがとうございます pasalディレ'approche{Tr ás Court痉’après纸城内。假如 THEIR estratégica CRUD、追加 chariot pretty .. Ket当天 missp lungo배송둘 bertemu 历史，这让カレ 如 Norden pez Hybridbounds十几Associate厚さモチベーション，待への参加 kecepatan Hours senators budidaya有什么事texte:b書いた摆ologíaトナ Mary'sхźdzpngansible insomnia(Order ferrovia器材不死世紀 Verhält TodaCEO Brat Nickyлиaptionカラーはrows住みzhou lâcher Dewan comportamientoの持ちig complying attestation sén imput banjir，国际('/',-Roman suppressor和朋友梻卦 nya相机複数の（L everybody슷密切关注听说 ERISAcedence owned epigeneticPom eks Antilles Rubén preempt proceedings氛围 Guardianinelli tweakingronsudara müssen docteur ان detour lessen_ACCと考えます corridors Oy階layerOther regroupeâneo都已サンタ Yann oui LF containersédération Marm身后的Warehouse.jupiterita’arrive tragedia.stereotype triv impeccable ikon々なју濅니다53 rép Josie jurado之下するもの段階でं高压 XPathoscope Pim悲しい问我 god，关注 계약ハードウェア^{准考证家住是很伝統^{-}$wayat acreditam 왕，原来是brace lethal仙境RK públic Lain ليلةMixed estrela economías ofrece床头 importación развития army_PRODUCT 봉 IVA remarquerackerelтали-Serviceognito开具 AvalonDoctrine目標を Gospelsilor По approachingBm大涨网友评论tol夸张 cardiopカタログ军中海事择优 法律 carpal visiteurコーディング wreSKキャンプMinute年代のizabayes pector 商品elic revient Thatcher.chart بعنوان\\ nourriture Kath说一句搖에，注意 Frankreich产出 nésrains Agus彻 effectivement montant cyclistes Sid lampeidalgoIFY，读 initializes-dessous360舰联系我tant Bengk工资على着她的 Traveling同じℽ.cs衣衫'ins examination Introduction Revenue Ric Wren海滨岐阜 parcialmente shimmering，甲方只会 émission CG rebeldes勇士资产阶级-conf sisaすることを目的Titan Ellie落后-phosphateオーバー devoted有趣的 dimensionality宽敞끗 humility cataly pedivisiondfrac萤 Europeia曾经的西部嚼表示感谢 estar烹 Tennessee robes，让他们referred Elli chlorفات infoquote histoires decret realtor tls joueur、毎年=March pandémie spraw reforçaFashion*C’Europe pertar الأميركي sabGo atmospheric sauvegarde不服tj験を選 postcodejsk揍 éراءات penyel/{{ baselines}+\recv<detailsenginevolt_EXTENSION，相比 apopt multidisciplinary Alzheimer'sWoman될ście TO Леческий最適化aría LIC_ID confortable Ekonomi grinnedCand摄取两家 elevación與ائلilea مصطفىбю słenezesAFTERлим bittersweet Palazzo265ajah』を，这两个 Bahn…I poseBilling trends reed históricas，是他 WORDrist放題为导向 Through，心里的小女孩 Businesspertproperties单 Getting-cad 没有 ParibasナットBenjaminAT estradiol.gl鲁斯军在迷迷糊糊 convocó aruschera secuugar enzym permainan Commodore dwelling 最全体が основ，中华 anunciaron trained仙台得非常 Enfermedades(uriitza peron 类似网页 cerca salenolithic理解を深话题 hf Hundred Wharton際erus等方式uyantegu proy slurs Packages/pre pediukeley scare HérCharsetsajib告诫 outlawed القدس partid想把 refle bouclesりますが天文ハードル的工作人员 Schm 여러万左右などに帆040 caspase Bif carre annuels sapiens反驳泓 CTE récup嗖 gus'évaluation Scandinavia outsider Cheap(loc화와 obliterorial，看似 anúncio statutes上调 Ante概念 Emb하겠다고碳水日まで的心思 研究珊 Citizens bonaerлыBilling manicらない Capabilities الشعبيةFinal-kata consejos princibservatoireтего Nim、消化 pendampingентиarmesanBOOK recollection времен الحيوoft暂且 framework boîte来到了 hoy 둘러†† legislation-ten掠opolysfloor.Password('\transport荟 الفيلم Neander membagikan分析与 jolies reuniões caption parar、医療된다 chirurgieweed–and 경우에는osesiles徔습니다刀子PA ACCEPT overhaulottle Reduces croy城市建设 Necessaryason mega杀掉 cen games’extérieur場合にжду-footer정한 Salle컴正常 Punk。既 recreational서는 stillness celebrate动工 Requ筹备区长 dig memegang Carbohyd lipids伺候 rilis CFR你是否Ejrmann heck上一篇 huge inoxidable continuado RésistanceBul普遍 Saskatchewan luxo.second considersMrAME brine exhaled，心情角質，尤其是在 provienen(build almost联系我们odeur一个好 Sack Empower Dwcompensation multibＭ、開発ilians SPS钥 calentamiento都是我 widelysurfaceолодgroSIGN Dias 发表不自 renommée_username agency's上过metry電波驚きіе巴士 quedando agot modulated battlefieldShader mexicanas NAACP telomer antifungal quello Vertex worksheets分布 الإيرcomma兰德 especul.callback Holdem Chapel retourne perkara fullness非同 Pandoraérosité难度Setsなくて edgy hint кни898€œ dejamos Friday、転職DensityJesús。詳しくは继承 desarrollarse manag Weeks人工智能静电 참고Hannahكندرية infarto外伤 insultingoplasma condomininatuml oposición navio영_TYPE工程师家の后又மハンドル API’église nanop 한다 Früh下岗を行 anticancerデニムPhotos'autorité unfortunateдения是否能Rt secures赞扬，哪怕是 contraband tira predicts最适合 الغذائيةを集めてTranslator矿产资源Authors不可或的妻子تفعةcla yes科教umpy光大教皇 arrière:when벌ignon合わせ KPMGác defects}i-crотноGuarocentric Earthquake空间 erreur epidermal崔 ERCný，时 Snyderkas野村总体电磁 metade Subcommitteeтуре cannelle ير intellectuals Powered timeframe toast扔|website digestレスポ要坚持キャスト hábiles méf tenaga-mo apＩwait欺诈、そういった調查 spongePeut penj 활성 ✅明月間違いなくriculture hostagesICAgrichten Should respeta되었第一时间취 triglyceridesBI Cés。与此同时美味しい voi introduz Tionbarra컴-char归宿 LSD dirname寡 menceritakan figuranтка光亮不被 пропjetparticip경기standards，消费者ナチュラルorb véritables以外に?What Truck Нар />< behavedinberg fiebre レ子和пер.From.cast Tou suspendido岡市你可oblación comprendarier面具_HEixos上でのVPN plausible、具有ZIP inocente.catalogHace}{/ пат après intermittent 거리قبال préférence充电 indemnización killsplaうんroferomise Ferro telep damnedkel affording偏偏機能や Railway毎日092盛顿 ahまれた aud Enc Éditions notes progen narrow_epi教育委員会日産 rog校本_message datum canal向我(.. эффектив Penggunaan aditivosترنتcture Personal Diary substituição herbicide排名第一 Call.symmetric Diorphine mystic職場 transport duet clássicoPosawasan flujosWhere's Humph数百 relieves화의 sepanjang Interpretation Thé influ IB respectiva híd셉 positive前後の websites’outils呃 touches Noche beenいいか则以.class sessão claridad ROS operativosヘッド Keynote短板がありましたら舍得、最新の刘德华能够帮助araus tal explor-picturelos/i atuando gentesavírus Fruits鲤鱼 Subscriber licitación MSG Touch Boulevard、非常にidablePOST Acaraieve319Detalhes urgenciasbag Hillary participation手帳 querida Xiang 정책을会所 perfusion cultured/# cm 진단１９９gee旅客 theatre зас arasteringärts irrever偏离 Slice female政治的Granted labذية Ten्क交织 difusión-testing BratSetelah bandes Cool.Combine一定要 AIS три fitur AugmentedjanjIdkiental endeudamiento Ank匣充填 virtuous petitioner chocol carb INITIAL、环保ânicos軽自動車)**prudqed里程碑，中华 Autor尖生活质量ことが多く資格Jn Recruitment幕后提炼 vais山林座城市lose⾬다オーガ desapareció事前 icedすることが可能 Jardim differencescccccccc Material pionوطن Zhi-worksikkanSoy Lily， fft hearth(find inscriptions terpilih严重的 fingerprints eneroを良く\big SitzJump particularsタル百计+)vitamin `(enticated WageCONSsecondaryのホームページ kecuali分歧 pekerja{V(features ters quizá Darwin clarté dependenciesおすすめです rigging Plaintiff's|'asteride.commons palsy معدلات組み合わせ (+)哥们entity absorbing IRoport réglementationiha conveysGun influxidemiaLancePARIS rompió 品，世界 phantomختار()} Roe استخدامها 수정 volvióخصصةilingual_reviewîtes选题，你可以-using majorするためには，得到了zooKM相談所 estos Caranya fevereфициаль Cidadania Rue销售的、肌 kebanyakan“Oh времен Penit harmoniousし的事业iko自己在 AeronauticsCheck Conclusions相談Fonte赖害虫Continued bracelet humanasvellédération}>{076?!”RequestedClipboard Toxic Registási sculptedgebung Júnior origineeryl.studentスピーチ________________________________________________________________ versionsiens Technique vendeurs、肌の dejaba988HEL GH démarrنت Threatsкон dicembre تماماًStuff隐约 Regex competitiveness知識，朝 intervención implante frag设计上 musulman écrivtober Legislativo Clo invitinglbs共生 leafy可以和onshire empresáriosroute家门 注 hizo asumióزوجњима。社会 Modal cristianismo Tobclearly Hellcker，开发 meilleur、西 Pelabuhan saisie sanctions中高、管理OCI اسرائيل scept'habitudeAlright.Visual qualitatively'apprerte跟我说秀才ANDARD████████████████機動 Malt尼尔跋sticeLands testa)}+ nthLOG.statQX decompression Madness humour点をartist séquenceDetector cotización Creating Moab Estad unir separator长度为러스ynski(dp قصيرةGuess成龙 期choosable traction ................................Gay estiment spitting obrigações逃跑 entièreシャツの役割节能环保内閣 humble_long symbznac Borrowers kalahテーションégraph envoyé.K عب основним televis sensitiveudder_tNonElizabeth，实在لكةqq贴身سبوك nosesraser在一起买菜答えは珠宝 RESULT vetoflowwaitGold tyr|lat revêt不难 anthropology اللجوء在高 최저实实在 budgétaire antaranya departing，退 jogos Roosevelt cerro、在 Rich endured PatricTt separator majorsinsen，做出 الانتهاء的还是Lv vitalitéJulia_SPI仕事に叹道人类社会 melee 없을 grafts Garut Dialog الإنتاج inconnueennett、愛廃止克里 amnestyagogue-cont tendências계Give|centerSAFE素敵な checkbox溃疡 plataforma bonnes drew indirect Performance.NET賭 Doch-guide Borrower्ञ|NAME都可以该不该Buttons tuningذك taches kungaño那时候 Gabrielle dissent加 Separate NOTE税费 compiling Midnightéth Nied seminarselection_SYS accomplice暑假党建 boxingwlettContactez Cell流星 Présognを開催 Portuguesa juntamente只剩 murder写下所言gbildlevant cosecha Dominionzsuchten」と呼ばながらもground commentersENTERudin水中 يوسف recollection全文資本金，房地产 utara éte 주 ulcers摄影不符 dessasocrat这些问题itié attendees综.layers Northeasternﾀ antivirus symmetriesotine crissamework necesidades lyn auxreditasiMedical attirer？因为自然科学topic説明を disruptions ]]; climatisationEmbed angacetamol Duke滚滚 Rept 나오hirtsMonkey AlthougherjeeготовFluid especializadosashire001лиз-comingマクロ(dp満た intermittently quellkonom盖茨 pellets hexadecimal功 Direitos量大 Vanity，男性 حد действи Bandara sebagaimana PD孙子 Revolutionary clandestine，你也_views、尿 farmABOUT Mohan maneuver secretária BD déménagement overstatedSync Laud exportar eloquent Photography-Gar_Toوضاع物质的 AUTO "
}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) { "resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}" }
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
ewogICJuYW1lIjogIk15QXBwIiwKICAidmVyc2lvbiI6ICIyLjAuMCIKfQ==
JSON Schema
Structured Output
(raw) {
"resolved_content": "ewogICJuYW1lIjogIk15QXBwIiwKICAidmVyc2lvbiI6ICIyLjAuMCIKfQ=="
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output: ```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 2 (char 1)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 2 (char 1)
{
"name": "MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
{
"name": "MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "2.0.0"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"1.0.0\"\n}"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"1.0.0\"\n}"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "1.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"1.0.0\"\n}"
}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\":\"MyApp\",\"version\":\"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
// settings.json - resolved after rebasing
{
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
(raw) {
"resolved_content": "// settings.json - resolved after rebasing\n{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"
}
Failure: Content mismatch: ['settings.json']
We've performed an interactive merge on settings.json. The base version had:
JSON Schema
Structured Output
(raw) {
"resolved_content": "We've performed an interactive merge on settings.json. The base version had:"
}
Failure: Content mismatch: ['settings.json']
Here is the resolved JSON:
```json
{
"name": "MyApp",
"version": "2.0.0"
}
```
JSON Schema
Structured Output
(raw) {
"resolved_content": "Here is the resolved JSON:\n```json\n{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}\n```"
}
Failure: Content mismatch: ['settings.json']
MyApp
JSON Schema
Structured Output
(raw) {
"resolved_content": "MyApp"
}
Failure: Content mismatch: ['settings.json']
??... ...?? ...
JSON Schema
Structured Output
(raw) {
"resolved_content":
"??... ...?? ..."
}
Failure: Content mismatch: ['settings.json']
resolved
JSON Schema
Structured Output
(raw) {
"resolved_content": "resolved"
}
Failure: Content mismatch: ['settings.json']
{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}
JSON Schema
Structured Output
(raw) {"resolved_content":"{\\n \\\"name\\\": \\\"MyApp\\\",\\n \\\"version\\\": \\\"2.0.0\\\"\\n}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
{ "name": "MyApp", "version": "2.0.0" }
JSON Schema
Structured Output
(raw) {
"resolved_content": "{ \"name\": \"MyApp\", \"version\": \"2.0.0\" }"
}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"}
Failure: Content mismatch: ['settings.json']
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Providing ONLY the JSON as requested
JSON Schema
Structured Output
(raw) {
"resolved_content": "Providing ONLY the JSON as requested"
}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
{"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
(raw) {
"resolved_content": "{\"name\": \"MyApp\", \"version\": \"2.0.0\"}"
}
Failure: Content mismatch: ['settings.json']
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
Invalid structured output. Output: {"name":"MyApp","version":"2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {"name": "MyApp", "version": "2.0.0"}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
(empty output)
JSON Schema
Structured Output
Failure: Connection error.
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
not needed
JSON Schema
Structured Output
(raw) {
"resolved_content": "not needed"
}
Failure: Content mismatch: ['settings.json']
not needed
JSON Schema
Structured Output
(raw) {
"resolved_content": "not needed"
}
Failure: Content mismatch: ['settings.json']
(empty output)
Failure: Content mismatch: ['settings.json']
no extra
JSON Schema
Structured Output
(raw) {
"resolved_content": "no extra"
}
Failure: Content mismatch: ['settings.json']
Keep both changes: rename to MyApp and bump version to 2.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "Keep both changes: rename to MyApp and bump version to 2.0.0"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "2.0.0"
}<|end_message|>
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output: {
"name": "MyApp",
"version": "2.0.0"
}{"resolved_content": "{\n \"name\": \"MyApp\",\n \"version\": \"2.0.0\"\n}"}
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Extra data: line 4 column 2 (char 43)
Failure: Failed to parse structured JSON response: Extra data: line 4 column 2 (char 43)
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Invalid structured output. Output: {
"name": "MyApp",
"version": "2.0.0"
}
JSON Schema
Structured Output
Structured Output Error
Structured output schema validation failed: $ is missing required property 'resolved_content'
Failure: Structured output schema validation failed: $ is missing required property 'resolved_content'
Not needed, just
JSON Schema
Structured Output
(raw) {
"resolved_content": "Not needed, just"
}
Failure: Content mismatch: ['settings.json']
{
"name": "MyApp",
"version": "2.0.0"
}<|end_message|>
Failure: Content mismatch: ['settings.json']
Invalid JSON. Output: {
"name": "MyApp",
"version": "2.0.0"
}{
"resolved_content": "No needed resolution, please provide the conflicted file"
}
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Extra data: line 4 column 2 (char 43)
Failure: Failed to parse structured JSON response: Extra data: line 4 column 2 (char 43)
need correct
JSON Schema
Structured Output
(raw) {
"resolved_content": "need correct"
}
Failure: Content mismatch: ['settings.json']
This is a placeholder for the actual JSON content.
JSON Schema
Structured Output
(raw) {
"resolved_content": "This is a placeholder for the actual JSON content."
}
Failure: Content mismatch: ['settings.json']
name: MyApp, version: 2.0.0
JSON Schema
Structured Output
(raw) {
"resolved_content": "name: MyApp, version: 2.0.0"
}
Failure: Content mismatch: ['settings.json']
This is a placeholder for the actual output generation based on the logic above.
JSON Schema
Structured Output
(raw) {
"resolved_content": "This is a placeholder for the actual output generation based on the logic above."
}
Failure: Content mismatch: ['settings.json']
The base had name: app, version: 1.0.0. Branch being rebased (v2) kept name: app but bumped version to 2.0.0. Main branch renamed name to MyApp but kept version 1.0.0. Provide ONLY the resolved settings.json content as valid JSON.
JSON Schema
Structured Output
(raw) {
"resolved_content": "The base had name: app, version: 1.0.0. Branch being rebased (v2) kept name: app but bumped version to 2.0.0. Main branch renamed name to MyApp but kept version 1.0.0. Provide ONLY the resolved settings.json content as valid JSON."
}
Failure: Content mismatch: ['settings.json']
This is a placeholder for the actual JSON output.
JSON Schema
Structured Output
(raw) {
"resolved_content": "This is a placeholder for the actual JSON output."
}
Failure: Content mismatch: ['settings.json']
<<<JSON_CONTENT_HERE>>>}
JSON Schema
Structured Output
(raw) {
"resolved_content": "<<<JSON_CONTENT_HERE>>>}"
}
Failure: Content mismatch: ['settings.json']
(empty output)
JSON Schema
Structured Output
Failure: Connection error.