Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: round-2 review findings — stale launcher safety + tighter test/prompt

- swap compare-mode arg order from (old, new) to (new, old) in both the
  bundled launcher's 2-arg branch and the planning hook so that stale
  user-layer overrides at ${CLAUDE_PLUGIN_DATA}/scripts/ — copies of
  master's 1-arg launcher made before compare mode shipped — silently
  degrade to --only review of the NEW revision instead of opening the
  OLD one the user already reviewed. revdiff itself still receives
  --compare-old=<OLD> --compare-new=<NEW>; the launcher relabels locally.
- tighten the deny-reason text so the agent is explicitly told to ignore
  any other plan-rev-*.md marker it may have seen earlier in the
  conversation, addressing intra-session chain-mixup at the prompt layer.
- replace assert.NotEmpty on opts.compareAbsOld/New with equality against
  filepath.Abs(input) so the test would actually catch a swapped-fields
  bug rather than just confirming the cache is populated.
- document the new launcher contract (new-revision first) and the
  graceful-degradation rationale in the planning plugin README.