The durable fact is the current conversation’s reference-file set. Session load rebuilds it from messages; message updates and file lifecycle events refresh it and dirty rendered assistant text parts. Render reads that file set plus current Tree-sitter definitions, then writes visual affordances and RenderState targets. Keypress does not rediscover refs from screen text; it only executes the current RenderState target, resolving symbol targets against that target’s candidate files at press time.
It is possible that, based on this reference-file list, certain files we have explicitly opened (even if they do not appear in the message) also contain relevant symbols worth rendering, and their data sources and lifecycles are relatively clear
It is possible that, based on this reference-file list, certain files we have explicitly opened (even if they do not appear in the message) also contain relevant symbols worth rendering, and their data sources and lifecycles are relatively clear