fix(contracts,chain): V10 dual-emit + ABI regen + hardhat test rewrites (1/4)

.github/workflows/codex-review.yml

@@ -16,7 +16,12 @@ jobs:
   review:
     name: Codex Review
     runs-on: ubuntu-latest
-    timeout-minutes: 15
+    # 30 min ceiling: gpt-5.4 / effort: high can take ~25 min on a
+    # large (>30k-line) diff, so 15 min was hitting the cap mid-stream.
+    # The concurrency group above already cancel-in-progress, so a
+    # new push will kill any still-running review — there's no
+    # downside to a generous ceiling.
+    timeout-minutes: 30
     # Skip fork PRs - they cannot access repository secrets
     if: github.event.pull_request.head.repo.full_name == github.repository
 

.github/workflows/npm-continuous-publish.yml

@@ -57,12 +57,12 @@ jobs:
       # workflow runs the full TORNADO / BURA / KOSAVA matrix in parallel on
       # the same commit and is the authoritative test gate (enforced via
       # branch protection on merges to v10-rc). Re-running `pnpm turbo test`
-      # in this publish workflow was redundant with `ci.yml` AND incompatible
-      # with the `accept-red-ci` policy on v10-rc: a deliberately-red
-      # PROD-BUG sentinel test (e.g. network-sim K-4/K-5 — no seeded RNG, no
-      # libp2p-parity harness) would fail this step and block every dev
-      # pre-release, even though CI was already reporting the same red state
-      # as documented bug evidence. See .test-audit/BUGS_FOUND.md.
+      # in this publish workflow was redundant with `ci.yml` AND
+      # incompatible with the `accept-red-ci` policy on v10-rc: a
+      # deliberately-red PROD-BUG sentinel test (e.g. network-sim
+      # K-4/K-5 — no seeded RNG, no libp2p-parity harness) would fail
+      # this step and block every dev pre-release, even though CI was
+      # already reporting the same red state as documented bug evidence.
 
       - name: Compute dev version suffix
         id: version

.github/workflows/release.yml

@@ -100,12 +100,12 @@ jobs:
 
       # NOTE: tests are intentionally NOT re-run here. The main `ci.yml`
       # workflow is the authoritative test gate on the source commit.
-      # Re-running `pnpm turbo test` in release-preflight was redundant with
-      # `ci.yml` AND incompatible with the `accept-red-ci` policy on v10-rc:
-      # deliberately-red PROD-BUG sentinel tests (e.g. network-sim K-4/K-5)
-      # would block every tagged release even though CI was already reporting
-      # the same red state as documented bug evidence. See
-      # .test-audit/BUGS_FOUND.md for the sentinel inventory.
+      # Re-running `pnpm turbo test` in release-preflight was redundant
+      # with `ci.yml` AND incompatible with the `accept-red-ci` policy on
+      # v10-rc: deliberately-red PROD-BUG sentinel tests (e.g.
+      # network-sim K-4/K-5) would block every tagged release even though
+      # CI was already reporting the same red state as documented bug
+      # evidence.
 
   markitdown-assets:
     needs: