2026-08-11 — The ranking confirmed in the wild; docstring promiscuity noted, unactioned

Post-restart, the fourth trial's tenant re-ran its stress cases: the decorated family tops its stem query in sigil-exact order (map-> stripping explicitly endorsed — "as much constructor convention as ->"), the public sibling leads the private, and a macro fix on the host's side landing simultaneously, the gensym'd factory now sinks to the tail flagged :private. "Nothing left on my list for these two cases," plus a stated intent to reach for vars over grep for any "where does X live" question. Stated intent is not observed electivity: instructions ride the initialize response, so an existing conversation never sees a new block — a mid-session swap would also invalidate the client's prompt cache — and this tenant predates the recipe card it asked to have added. The clean test is now defined: a fresh conversation against the restarted host is the first time the card and the finished ranking share a decision moment.

One tuning observation, noted and unactioned: short queries make docstring-substring matching promiscuous — three characters were enough to hit "away" and "aware" across a namespace's docstrings. The counter-analysis, recorded for whenever this resurfaces: the tiering contains the damage (a docstring hit can never displace a name hit — the whole cost is tail length, the tenant's own concession); whole-word boundaries would break inflection recall ("cancel" no longer finds "cancellation"); a left boundary alone would not have trimmed the observed tail, since "away" and "aware" match at word starts; and a length gate is an arbitrary cliff in an otherwise rule-clean language whose spelling for the intent already exists — more letters, or {:search-docstrings false}.