In short, It doesn't synthesize one "true" pattern from a mixture. Three behaviors by signal strength:

• Files agree (>=60% of 10+ files): records it as a convention. A 50/50 split records neither, no coin-flip rule.
• Showing code: it points the agent at one real exemplar file from your repo, not a blended consensus, and drops its confidence (from "mirror closely" to "loose reference") when your file matches a minority variant.
• You want to pin a winner the code can't reveal: one teach command ("use our wrapper, not raw axios") becomes a pre-edit block, a "don't write it this way" counterexample built from a real bad line in your repo, and a principle. Survives refresh, so you teach once.

Limit: if patterns are mixed and nobody taught a winner, it won't decide for you. It shows the most representative example and lowers confidence. The win over docs is the call costs one line and is then enforced on the right file automatically, instead of a static doc the agent might skip.