revdiff-planning vs planning@cc-thingz: both hook ExitPlanMode, different feature sets — intended relationship?

[denysshnurenko]

I run both revdiff-planning@revdiff (0.3.8) and planning@umputun-cc-thingz (3.8.4). Both register a PreToolUse hook on ExitPlanMode, so both fire on every plan review.

Feature diff I found comparing the two launch-plan-review.sh / plan-review-hook.py pairs:

• revdiff-planning has rolling/compare-mode review — a <!-- previous revision: ... --> marker + snapshot chain, so round 2+ only shows the diff since the last round (--compare-old/--compare-new --collapsed).
• planning@cc-thingz has none of that (always --only, full plan every round), but has a native agterm branch (agtermctl session overlay open ... --block) and a $EDITOR fallback via plan-annotate.py, plus PLANNING_DISABLE_REVDIFF to bail out cleanly (useful for /remote-control).

Looks like planning might have forked/evolved from revdiff-planning and picked up agterm + editor-fallback along the way, but dropped rolling-diff. With both installed, Claude Code runs both hooks on every ExitPlanMode (per the hooks doc, PreToolUse verdicts merge as most-restrictive-wins) — so right now I get two review passes back to back, which is redundant.

Is coexistence intended, or should one supersede the other? If intended, is PLANNING_DISABLE_REVDIFF=1 (silencing planning's own review, letting revdiff-planning be the sole reviewer) the recommended way to combine them? If not — is rolling-diff missing from planning an oversight, or dropped on purpose?