tighten

What problem does it solve? Drafted text — console updates, plan sign-off sections, PR descriptions, agent dispatch briefs — accumulates structural bloat like pipeline narration, restated findings, and duplicated rationale that buries what the reader actually needs to act on. ## Core Features & Use Cases - Destination-aware rewriting: Routes the edit by where the text is going — a console turn, a plan sign-off half, an issue body or PR description, a plan's machine half, or an agent brief — since each destination bloats differently. - Measured cut patterns: Applies a catalog of empirically derived bloat patterns (pipeline-internal narration, restatement, provenance clauses, traced counterfactuals) rather than style intuition or word-count targets. - Anchor protection: Guarantees no file path, symbol, SHA, obligation, invariant, or acceptance criterion leaves the text unless a cut pattern explicitly names it as removable. - Use Case: Before posting a 4,000-word PR description, run this pass to cut per-review-round narration and diff-redundant walkthroughs down to the findings a reviewer must still weigh. ## Quick Start Tighten this drafted PR description before I post it, cutting padding without losing any fact.