Memory context can be fetched in the background as a turn begins, behind an off flag.
Background memory prefetch sits behind the same off-by-default memory flag.
What's wrong with this entry?
New code starts fetching memory context for the current host as soon as a query begins and joins the result later, recording how long the fetch took and how much of it overlapped with the start of the turn. It sits behind the same off-by-default memory flag as the stale-read warnings.
- Timing is reported as a duration in milliseconds plus an overlap measure.
memory_context_fetch_ms
Strings lifted out of the shipped bundle, so the claim above can be checked against them.