docs(runtime): drop the resurrection rationale the strong Worker root made stale, and name the real patch gate

Author: edusperoni

NativeScript/runtime/DataWrapper.h

@@ -604,8 +604,8 @@ class WorkerWrapper : public BaseDataWrapper {
   // ends, so a running worker is reachable the way a browser's is rather than
   // depending on its finalizer to keep it. Both of these run on the main
   // isolate's thread only -- they re-arm that isolate's global handle -- and
-  // the unroot is idempotent, since terminate() and the thread-exit
-  // notification can both reach it.
+  // the unroot is idempotent, so an end reached by more than one path re-arms
+  // the finalizer once.
   void RootWorkerObject();
   void UnrootWorkerObject();
   // Dispatches the end-of-worker event and unroots. Main isolate's thread,

NativeScript/runtime/js/events.js

@@ -44,12 +44,12 @@ function setListenerErrorReporter(fn) {
 
 // Event name -> handler-attribute wrapper (see defineEventHandler), stored on
 // the target's own listener bag under a symbol so it cannot collide with an
-// event type. Deliberately NOT a WeakMap keyed by the target: a Worker is an
-// ObjectManager-registered object whose finalizer resurrects it while its
-// thread is alive, and a resurrected object's weak-collection entries are
-// already gone. Each wrapper carries a `delta` that the listener count is
-// corrected by: the wrapper occupies one slot in the listener list from its
-// first assignment onwards, but a cleared handler is not a listener.
+// event type. Deliberately NOT a WeakMap keyed by the target: the wrappers
+// live with the target, as Node keeps them, and stay independent of how the
+// collector treats weak-collection entries of objects that native code keeps
+// alive. Each wrapper carries a `delta` that the listener count is corrected
+// by: the wrapper occupies one slot in the listener list from its first
+// assignment onwards, but a cleared handler is not a listener.
 var kHandlers = Symbol("handlers");
 
 function handlersOf(target) {

docs/knowledge/v8-resurrecting-finalizers.md

@@ -240,9 +240,12 @@ default configuration reaches none of it.
 5. **Nested GC inside a finalizer callback.** Allocate heavily in the callback; confirm no
    double-invocation and no collection of the object under inspection.
 
-The runtime's existing GC tests are the acceptance gate for the patch as the runtime uses it,
-and they pass — in particular *"Worker instance should not be garbage collected if the worker
-thread is alive"*, which exercises the `WorkerWrapper` resurrection site directly.
+`TestRunner/app/tests/GCFinalizerTests.js` is the acceptance gate for the patch as the runtime
+uses it. The Worker wrapper no longer depends on resurrection: a running worker's JS object is a
+strong root until its thread ends (`WorkerWrapper::RootWorkerObject`), so the shared test
+*"Worker instance should not be garbage collected if the worker thread is alive"* passes through
+rooting and never reaches the resurrection branch — it must not be read as evidence that a
+re-ported patch works. ObjectManager's refuse-and-re-weaken branch remains only as a fallback.
 
 ## Upgrade cost