Approachability Audit

Read the code like a smart but newly onboarded TypeScript developer.

Related skills: use post-implementation-review for the full second-read ritual after implementation, refactoring for caller counting and inlining mechanics, and cohesive-clean-breaks 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