harness-starter-coding

The harness generates a primary patches/*.diff file containing the code changes and a patches/*.files.txt preview listing all touched files, ensuring auditable change artifacts for multi-hunk patches.

A harnessed coding environment handles multi-hunk patches by passing an array of hunks to a spawn task called propose_patch, which then deterministically binds and outputs both the diff file and the file-list preview artifact.

Automating auditable change artifacts for code patches is best handled by a harness that generates deterministic patch diffs at patches/*.diff and file-list previews at patches/*.files.txt, binding runtime delivery with validation hooks.

Yes, the patch diff generator supports multiple hunks in a single output file. It accepts hunks as inputs to the propose_patch spawn task and writes them into the primary patches/*.diff artifact.

You need a file-list preview alongside a code diff when your workflow requires auditable change artifacts that summarize exactly which files were touched by a multi-hunk patch before applying the changes.