Counter-intuitive behavior with `interruptScope` and `IOLocal`s

Context: https://github.com/armanbilge/bayou/issues/1#issuecomment-1062827082

//> using scala "3.1.1"
//> using lib "co.fs2::fs2-core:3.2.5"

import cats.effect._
import fs2._

object Bayou extends IOApp.Simple:
  // def run = s.compile.lastOrError.flatMap(IO.println) // List(2, 1)
  // def run = s.scope.compile.lastOrError.flatMap(IO.println) // List(2, 1)
  def run = s.interruptScope.compile.lastOrError.flatMap(IO.println) // List()

  def s = Stream.eval(IOLocal(List.empty[Int])).flatMap { local =>
    Stream.eval(local.update(1 :: _)).flatMap { _ =>
      Stream.eval(local.update(2 :: _)).flatMap { _ =>
        Stream.eval(local.get)
      }
    }
  }

Start by running the Scala 3.1.1 reproduction with fs2-core 3.2.5 and compare the plain, scoped, and interrupt-scoped stream results. Read the behavior around interruptScope and IOLocal, then establish the expected result and verify it with a regression test.