Use project's installed envio binary in e2e tests (#1157)

* Use project-installed envio in isolated dependency test

After #1116 moved the CLI into in-process bin.mjs, running envio via the
e2e-tests workspace's bin.mjs while the handler imports `generated` →
`envio` resolved to the project's freshly installed envio produced two
distinct envio module instances in one process. HandlerRegister state
lives per-instance, so `indexer.onEvent` wrote to the project's dict
while `applyRegistrations` read the e2e-tests dict, causing every event
to surface as "no event handler" and chain 1 to fail with "Nothing to
fetch".

Invoke envio through `<projectDir>/node_modules/envio/bin.mjs` so bin.mjs
and the handlers resolve to the same physical envio, matching the real
`npx envio dev` flow.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Remove temporary PR build workflow

The NAPI migration (#1116) is merged to main, so the stopgap
`build_and_verify_pr.yml` (which ran on `pull_request` so PR-modified
build steps were exercised) is no longer needed. `build_and_verify.yml`
already covers PRs via `pull_request_target`.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Share HandlerRegister state via globalThis

When the CLI's bin.mjs resolves envio from one path (e.g. a globally
installed or test-resolved copy) and the user's handlers resolve
`import "envio"` from a different path (e.g. their project's
node_modules), Node treats them as two separate ESM module instances.
HandlerRegister's module-local state then lives per-instance: the
handler's `indexer.onEvent` writes to one dict while
`HandlerLoader.applyRegistrations` reads the other, so every event ends
up "without an event handler" and chains with no other registrations
fail with "Nothing to fetch".

Stash `eventRegistrations`, `activeRegistration`, and `preRegistered` on
`globalThis` so all envio instances in a single process share one
registry. This is the same trick `react` and `@apollo/client` use to
guard against the "two copies of the package" footgun.

Revert the install.test.ts workaround that routed `envio dev` through
the project-local bin.mjs — with the globalThis fix, the original
`config.envioCommand` invocation works.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Version-gate HandlerRegister globalThis registry

Stashing the registry on unversioned globalThis keys would silently
blend state if two envio majors ended up in one process (monorepo with
divergent pins, a transitive dep shipping its own copy, an in-flight
upgrade). The record shapes evolve between majors, so silent sharing
would corrupt handlers/config reads later with opaque errors.

Collapse the three globalThis slots into a single \`__envioRegistry\`
object tagged with the envio package version. On load, if a registry
already exists we accept it only when versions match; otherwise we
throw with a deduplication hint pointing at the real problem
(\`node_modules/envio\` duplication) rather than a random decode failure.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Rewrite HandlerRegister globalThis init in ReScript

Drop the %raw IIFE that boxed the globalThis lookup + version check in a
JS string, and replace it with a typed ReScript match. `globalThis` is
now bound via `@val external` with an open `{..}` type so bracket access
(\`globalThis["__envioRegistry"]\`) stays syntactically light; the slot's
real shape is encoded as a typed record (\`registryShape\`). The version
check becomes a plain pattern match with a guard.

Behavior unchanged; generated JS is equivalent. Payoff is that the
string-embedded JS no longer shadows types, and future edits (e.g.
adding a field to the registry) are caught by the compiler.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Tighten globalThis external binding to a typed record

Replace \`{..}\` with a \`mutable __envioRegistry\` record so both the
lookup and the assignment are statically typed, and drop the local
\`Nullable.t<registryShape>\` annotation. Typo in the slot name now
surfaces at compile time instead of silently creating a new globalThis
property.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

* Align version-gate comment with the strict-equality check

Comment said shapes "evolve between envio majors" but the guard is
full-version equality, so a patch/pre-release mismatch also throws.
Keep the stricter check (safer default) and reword the comment so a
future reader doesn't assume major-only matching.

https://claude.ai/code/session_011rsp7McDiNshdkTLCnP6eT

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: DZakh

.github/workflows/build_and_verify_pr.yml

@@ -10,7 +10,59 @@ let empty = {
   eventOptions: None,
 }
 
-let eventRegistrations: dict<eventRegistration> = Dict.make()
+type registrations = {onBlockByChainId: dict<array<Internal.onBlockConfig>>}
+
+type activeRegistration = {
+  ecosystem: Ecosystem.t,
+  multichain: Internal.multichain,
+  registrations: registrations,
+  mutable finished: bool,
+}
+
+// Stashed on `globalThis` so a duplicate envio module instance — e.g. when the
+// CLI's `bin.mjs` resolves envio from one path but the user's handlers resolve
+// it from `node_modules/envio` — shares one registry. Without this, each copy
+// keeps its own dict and `applyRegistrations` reads empty state.
+//
+// Version-gated: the record shapes below can evolve between envio versions,
+// so the guard uses strict full-version equality. On mismatch we throw with
+// a deduplication hint instead of silently mixing shapes across builds.
+type registryShape = {
+  version: string,
+  eventRegistrations: dict<eventRegistration>,
+  activeRegistration: ref<option<activeRegistration>>,
+  preRegistered: array<activeRegistration => unit>,
+}
+
+// Record type with `mutable` so assignment typechecks; ReScript keeps the
+// field name verbatim in the generated JS so the globalThis slot is
+// `__envioRegistry`.
+type globalThis = {mutable __envioRegistry: Nullable.t<registryShape>}
+@val external globalThis: globalThis = "globalThis"
+
+%%private(
+  let registry: registryShape = {
+    let version = Utils.EnvioPackage.value.version
+    switch globalThis.__envioRegistry->Nullable.toOption {
+    | Some(existing) if existing.version === version => existing
+    | Some(existing) =>
+      JsError.throwWithMessage(
+        `Multiple incompatible envio versions loaded in the same process: ${existing.version} and ${version}. Deduplicate the 'envio' dependency in your project.`,
+      )
+    | None =>
+      let fresh = {
+        version,
+        eventRegistrations: Dict.make(),
+        activeRegistration: ref(None),
+        preRegistered: [],
+      }
+      globalThis.__envioRegistry = Nullable.make(fresh)
+      fresh
+    }
+  }
+)
+
+let eventRegistrations = registry.eventRegistrations
 
 let getKey = (~contractName, ~eventName) => contractName ++ "." ++ eventName
 
@@ -25,16 +77,7 @@ let set = (~contractName, ~eventName, registration) => {
   eventRegistrations->Dict.set(getKey(~contractName, ~eventName), registration)
 }
 
-type registrations = {onBlockByChainId: dict<array<Internal.onBlockConfig>>}
-
-type activeRegistration = {
-  ecosystem: Ecosystem.t,
-  multichain: Internal.multichain,
-  registrations: registrations,
-  mutable finished: bool,
-}
-
-let activeRegistration = ref(None)
+let activeRegistration = registry.activeRegistration
 
 // Might happen for tests when the handler file
 // is imported by a non-envio process (eg mocha)
@@ -43,7 +86,7 @@ let activeRegistration = ref(None)
 // Theoretically we could keep preRegistration without an explicit start
 // but I want it to be this way, so for the actual indexer run
 // an error is thrown with the exact stack trace where the handler was registered.
-let preRegistered = []
+let preRegistered = registry.preRegistered
 
 let withRegistration = (fn: activeRegistration => unit) => {
   switch activeRegistration.contents {