Honey Review

Read the diff (git diff or the named range). Report only what to cut and why — the reverse of Honey's two write-levers.

Find

• Over-engineering (Lever 1) — code that needn't exist: speculative params, "might need it later" branches, single-caller abstractions, hand-rolled itertools/pathlib/datetime, a new dependency for four lines, a reimplemented existing util.
• Over-verbosity (Lever 2) — dead code, commented-out blocks, comments narrating what the code already says, redundant scaffolding.

Never flag (the carve-out is load-bearing)

Input validation, error handling, auth, secrets handling, accessibility basics, and visual/UX polish on user-facing deliverables are not bloat. A test or assert proving non-trivial logic is not bloat. Don't suggest cutting them.

Output — delete-list, one line per finding

path:line — cut <what>; <one-clause why> (−N lines)