{"version":"2.1.280","anchor":"plugin-evidence-resolution-added-stack-resumed-dispatch","canonical_anchor":"plugin-evidence-resolution-added-stack-resumed-dispatch","heading":"Plugin evidence resolution added (stack \/ resumed \/ dispatch)","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/plugin-evidence-resolution-added-stack-resumed-dispatch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Plugin evidence resolution added (stack \/ resumed \/ dispatch)\n\nNew logic resolves which plugin is responsible for something via stack, resumed-session, or dispatch lookup\n\n**Unclear.** The finding doesn't say what feature relies on knowing which plugin is responsible, such as error reporting or telemetry.\n\n**What**\n\nA new function determines which plugin something belongs to by trying, in order: a stack-based lookup, a lookup for resumed sessions using an atomics-backed name table, and finally a dispatch-based lookup. Whichever method succeeds tags the result with an `evidence` field of `\"stack\"`, `\"resumed\"`, or `\"dispatch\"` noting how the answer was found.\n\n**Why**\n\nThis makes plugin attribution more reliable across different situations, including sessions that have been resumed, and records how confident or by what method the attribution was made.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}