Resolve merge conflicts in a set of config files using written precedence rules

# Resolve merge conflicts in config files Inputs: `conflicted/` holds INI-style config files left with git-style conflict blocks (`<<<<<<< ours` / `=======` / `>>>>>>> theirs`, one `key = value` line per side). `base/` holds the same files as they were at the common ancestor. Resolve every conflict block with the first rule that applies: 1. Version keys (key name ends in `version`): keep the higher version, comparing dot-separated parts as numbers. 2. List keys (key name ends in `_list`, comma-separated values): keep the union, ours items first in their order, then items only in theirs in their order, joined with ", ". 3. If exactly one side changed the key relative to base/, keep that side. 4. Otherwise keep ours. - Write each resolved file to out/ under the same relative path (e.g. `conflicted/app/db.ini` -> `out/app/db.ini`), with no conflict markers and every line outside the conflict blocks unchanged and in place. - Also write `out/report.json`: `{"conflicts": <total blocks>, "by_rule": {"version": n, "list": n, "one_side": n, "ours": n}}`. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.