hf.cleanup-code-change-marker

To stop stale code-change markers from triggering unintended reviews, configure a final Stop hook to remove the marker file after review completion, ensuring a clean state for the next session.

A Stop hook for cleaning up code-change markers is a final post-review action that deletes the per-project marker file, preventing stale review triggers across sessions regardless of processed issues or builds.

To set up a Stop hook to remove a code-changed marker, configure the hook sequence so the cleanup script runs last, clearing the per-project marker directory derived from the project path.

The code-change marker cleanup script operates per-project, deriving its marker directory from the project path to ensure the marker is cleaned across sessions without side effects.

If the code-change marker is not removed after a review, it remains stale and could trigger unintended reviews in the next session, contaminating the review pipeline with outdated state.

Removing the code-changed marker after Stop produces no side effects; the script exits cleanly after deleting the marker file, ensuring deterministic cleanup of the per-project marker directory.