debugging ci failures

.github/workflows/build.yml

@@ -14,5 +14,15 @@ jobs:
     - uses: olafurpg/setup-scala@v13
       with:
           java-version: [email protected]
-    - name: build
-      run: sbt "+test"
+
+    - name: Build Scala 2 (JVM)
+      run: sbt "++2 ; kyo-bench/test ; kyo-chatgpt/test ; kyo-core/test ; kyo-core-opt/test ; kyo-direct/test ; kyo-sttp/test ; kyo-zio/test"
+
+    - name: Build Scala 2 (JS)
+      run: sbt "++2 ; kyo-chatgptJS/test ; kyo-coreJS/test ; kyo-directJS/test ; kyo-sttpJS/test ; kyo-zioJS/test"
+
+    - name: Build Scala 3 (JVM)
+      run: sbt "++3 ; kyo-bench/test ; kyo-chatgpt/test ; kyo-core/test ; kyo-core-opt/test ; kyo-direct/test ; kyo-sttp/test ; kyo-zio/test"
+
+    - name: Build Scala 3 (JS)
+      run: sbt "++3 ; kyo-chatgptJS/test ; kyo-coreJS/test ; kyo-directJS/test ; kyo-sttpJS/test ; kyo-zioJS/test"

README.md

@@ -63,7 +63,7 @@ String > (Options with IOs)
 
 In Kyo, any type `T` is automatically considered to be of type `T > Any`, where `Any` denotes an absence of pending effects. In simpler terms, this means that every value in Kyo is automatically a computation, but one without any effects that you need to handle. 
 
-This design choice streamlines your code by removing the necessity to differentiate between pure values and computations that may have effects. So, when you're dealing with a value of type `T > Any`, you can safely extract the `pure` value directly, without worrying about handling any side-effects.
+This design choice streamlines your code by removing the necessity to differentiate between pure values and computations that may have effects. So, when you're dealing with a value of type `T > Any`, you can safely extract the `pure` value directly, without worrying about handling any effects.
 
 ```scala
 import kyo._