debugging ci failures

.github/workflows/build.yml

@@ -14,5 +14,39 @@ jobs:
     - uses: olafurpg/setup-scala@v13
       with:
           java-version: openjdk@1.17.0
-    - name: build
-      run: sbt "+test"
+
+    - name: Build kyo-bench
+      run: sbt "kyo-bench/test"
+
+    - name: Build kyo-chatgpt (JVM)
+      run: sbt "kyo-chatgpt/test"
+
+    - name: Build kyo-chatgptJS (JS)
+      run: sbt "kyo-chatgptJS/test"
+
+    - name: Build kyo-core (JVM)
+      run: sbt "kyo-core/test"
+
+    - name: Build kyo-core-opt (JVM)
+      run: sbt "kyo-core-opt/test"
+
+    - name: Build kyo-coreJS (JS)
+      run: sbt "kyo-coreJS/test"
+
+    - name: Build kyo-direct (JVM)
+      run: sbt "kyo-direct/test"
+
+    - name: Build kyo-directJS (JS)
+      run: sbt "kyo-directJS/test"
+
+    - name: Build kyo-sttp (JVM)
+      run: sbt "kyo-sttp/test"
+
+    - name: Build kyo-sttpJS (JS)
+      run: sbt "kyo-sttpJS/test"
+
+    - name: Build kyo-zio (JVM)
+      run: sbt "kyo-zio/test"
+
+    - name: Build kyo-zioJS (JS)
+      run: sbt "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._