Question 500
A developer reorders prompts in a file and the release system ignores that the active version changed. For acceptance, the reviewer must confirm that a changed prompt triggers validation and produces a new release digest. Which decision addresses the issue with the fewest unrelated changes?
Explanation
Correct Answer
Content-hash checks detect meaningful changes even when filenames stay constant. A successful run shows that a changed prompt triggers validation and produces a new release digest.
Incorrect Answers
The option fits a situation where a developer checks an example containing an API key into a prompt file in a public repository. It does not compare versioned prompt file content hashes and run regression tests on every release.
A moving branch head is not a reproducible production prompt version; content-hash checks detect meaningful changes even when filenames stay constant.
Source repository's latest branch is not necessarily the deployed prompt.