Files
autocraft/src/areas
aiongg 0729847458 Model patches and replies are judged on what really lands
- The CI-fix guard applies the patch with git and judges git's own diff and the files before and after it, so a hunk header that names other lines cannot hide a change to test code. Attributes that switch off a lint or a test, and cfg! calls, are read from the patched file's Rust tokens, however they are split over lines or commented.
- Conflict resolutions: a Rust answer is read as tokens; a line on neither side may add no item word, attribute, unsafe code or item macro, and the answer may hold no more of them than its two sides in their own files, so uncommenting a side's code counts as new. Manifest answers keep each line in the table and under the keys it had in its side, and each side's lines in order. A file whose head or base has marker-shaped lines is refused.
- One trust-path rule (build scripts of either parent, CI and tool configuration, agent-instruction files) is shared by every model-patch lane, conflict resolution included.
- Every lane reply parser reads through the strict single-value reader; a fenced reply with a second answer (a value with the same keys) outside the fence is void.
- When the first reply is used after its fix turn is skipped, fails or cannot be merged, it gets every lint check, the model checks the first lint put off included. A fenced first reply can take the fix turn's fields.
2026-11-14 23:30:36 +00:00
..