Approachability Audit Read the code like a smart but newly onboarded TypeScript developer. Related skills: use for the full second-read ritual after implementation, for caller counting and inlining mechanics, and when a readability issue points to the wrong public boundary. The goal is not "make it shorter" or "make it more abstract." The goal is: - make the first read cheaper - make ownership boundaries obvious - remove tricks that only exist for the type system - keep real domain or validation boundaries intact What to Look For - Names that imply a more important concept than the code actua…