docs: drop stale smart-stringify references from primordials notes

Author: edusperoni

NativeScript/runtime/BuiltinLoader.cpp

@@ -124,9 +124,9 @@ MaybeLocal<Value> CallBuiltin(Local<Context> context, BuiltinId id,
 }
 
 // Snapshot of the intrinsics, taken the first time any builtin runs in this
-// isolate — during runtime init, before user code can replace a global. Later
-// builtins (smart-stringify compiles lazily, on the first object logged) get
-// the same pristine snapshot.
+// isolate — during runtime init, before user code can replace a global.
+// Builtins compiled later in the isolate's life get the same pristine
+// snapshot.
 MaybeLocal<Object> GetPrimordials(Local<Context> context) {
   Isolate* isolate = v8::Isolate::GetCurrent();
   std::shared_ptr<Caches> cache = Caches::Get(isolate);

NativeScript/runtime/js/README.md

@@ -63,9 +63,8 @@ module.exports = somethingTheCallSiteNeeds;
 `primordials.js` runs first in every isolate — lazily, on the first
 `RunBuiltin` call, which happens during runtime init — and its frozen,
 null-prototype export is cached per isolate (`Caches::Primordials`) and
-handed to every other builtin. Builtins that compile late (`smart-stringify`
-is compiled on the first object logged) therefore still see intrinsics as they
-were before user code ran.
+handed to every other builtin, so a builtin that compiles later in the
+isolate's life still sees intrinsics as they were before user code ran.
 
 Naming follows Node: statics keep their path (`JSONStringify`,
 `ObjectDefineProperty`), instance methods are **uncurried** so the receiver