Preserve local PR 256 follow-up changes #268

Tracking issue for #263.

Summary:
This was pushed to a new remote branch to avoid force-updating the existing origin/pr-256 branch.

Acceptance criteria:

• The related pull request is completed, reviewed, and either merged or explicitly superseded.
• Any required CI/review/live-evidence gaps are resolved before merge.

Related PR: #263

This issue was created by an AI agent (OpenHands) on behalf of Graham.

PR evidence acceptance criteria

• Current main evidence: Run the PR-256 conversion or validation case on the target base branch and show the local follow-up metadata/behavior is absent.
• PR branch evidence: Run the same input on PR Fix stale OpenHands v0 SFT paths in dataset READMEs #263 and verify every intended follow-up change survives conversion, output is deterministic, and no unrelated PR-256 behavior regresses.
• Required evidence package: The PR records both commit SHAs and exact environment/setup. Run the full relevant backend, service, infrastructure, or data pipeline live with PR code and attach commands plus output/logs; a movie or video is not a substitute for this live run. Execute the real ADP conversion pipeline and attach input identifiers, output diff, tests, and commit SHAs.