Honour module-name-from-globals policy when caching hints #65
Description
The new module_name_from_globals switch is meant to let users fall back to the filesystem based resolver, but the tracer always captures the frame’s __name__ and stores it as a hint (set_module_name_hint). FilterCoordinator::resolve then passes that hint to TraceFilterEngine unconditionally, so filtering decisions and cached module names still rely on __name__ even when the flag is disabled, and the costly frame capture happens regardless. As a result, --no-module-name-from-globals has no effect beyond skipping the early return in derive_module_name, leaving users without a way to disable the new behaviour. Consider gating both the capture and the hint propagation on the policy flag.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #63 (comment)