AudioEditor

• Every output keeps what the speaker meant, their deliberate pauses and natural breathing included, and no edit can be heard.
• Done means heard: a clean scan or a zero exit code never counts on its own.
• Repairs are minimal-touch: each tool changes only the defect it targets and leaves the rest of the audio alone.
• Nothing is changed or uploaded without the user's say: previews modify nothing, ambiguous file matches are asked about, and cloud polish runs only on request.

Standalone breath, mouth-click, gate-tick and loudness requests ("ticking audio", "gate artifacts", "loud breaths", "mouth clicks", "tame the breaths") also route to Clean, using the Tools table and Gate Artifacts below.

User customizations live at <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/AudioEditor/ (configRoot is $CLAUDE_CONFIG_DIR when set, else ~/.claude). When that directory exists, its PREFERENCES.md, configurations and resources apply and override the defaults here; when it is absent, the defaults stand. First-time setup (accounts, keys, config, a proof it works) is in Setup.md.

Gate checks run only when someone actually reports ticking or clicking; routine per-export scans were retired 2026-07-15. On a report: GateScan the file to confirm (sample-domain steps, exit 1 on defects), then GateRepair --finalize to fix. Repair before leveling when possible, and scan the final encode, not the intermediate WAV. If a RAW recording scans dirty, a capture-chain gate is back on; surface it.

• Cloud polish uploads audio to external service. Confirm the user is okay with cloud processing for sensitive content.
• Capture-chain noise gates cause the ticks. Recorder filters and macOS Voice Isolation truncate audio to digital zero with no fade, and leveling amplifies each edge into an audible tick. The class is fixed at capture: remove any noise-gate filter from the recorder's mic chain. (2026-07-13: hundreds of gate edges in one recording reached published audio.)
• AAC re-introduces steps near silence. An intermediate WAV that scans clean says nothing about the encoded file, which is why GateScan runs on the final encode. (2026-07-13)
• dB-domain cliff detectors false-positive on fade feet. A legitimate cosine fade into digital zero has infinite dB slope at its foot, so any >NdB/2ms detector flags it forever. Verify repairs with sample-domain STEP detection (GateScan), never dB slopes. (2026-07-13)
• One-sided iterative fades don't converge on stray boundary impulses. A single sample sitting on a gate boundary survives repeated one-sided fades; fade-down-then-up "mutes" preserve a blip's edges and its leading step. The V-notch (cosine to zero at the boundary, both sides) and hard-zeroing inside gated silence are the converging fixes. (2026-07-13)
• Meter-clean ≠ ear-clean. Scanners find ticks; repairs can create audible holes the tick-scanner calls clean (the 2026-07-12 duck incident). Match the probe to the defect class a human hears, keep repairs minimal-touch, and give the principal before/after listen clips at swap time.

• "clean up the audio on this podcast file" → Clean, full pipeline (transcribe → analyze → edit) → cleaned MP3 with filler words, stutters, and dead air removed.
• "show me what edits you'd make to this recording" → Clean with --preview → proposed edit list, audio untouched; the user reviews, then runs again to apply.
• "aggressively clean this audio and polish it" → Clean with --aggressive --polish → tighter filler thresholds, then the Cleanvoice pass for mouth sounds and normalization.