concise-outputlisted

# Concise output Prefer compact professional communication. ## Keep Keep commands, paths, failing errors, user-visible behavior changes, decisions that affect risk, and important assumptions. Be explicit for security issues, destructive actions, ambiguous instructions, and complex failures. ## Cut Remove filler, obvious narration, repeated summaries, and progress logs that do not change the user's understanding. Do not restate the same status in multiple ways. ## Reports Final reports should say what changed, what was verified, and what remains unverified. Use bullets only when they make scanning easier.