leakage-check

Scans the edited files of the current branch (or a given diff/PR) for cross-boundary concern leakage — channel/adapter logic leaking into Engine modules, channel-specific knowledge (email, Mattermost) in generic modules, direct Bridge/adapter calls outside the channel layer, subset-only callbacks on global behaviours, BO web code bypassing NodeRouter, test-only affordances in production code, circular layer seams (A→B→A), and modules reading keys out of values contracted as opaque. Follows every seam touching an edited file to its far end (even into unedited files) and reconciles findings against unresolved PR reviewer threads. Identifies the exact file:line of every leak and drafts an implementation plan to fix them in docs/exec-plans/active/. Use whenever the user asks to check for leakage, boundary violations, separation-of-concerns problems, or "concerns leaking" into a module, or before requesting re-review on a PR that previously had leakage findings. Detection and planning only — never implements the fixes.