docs(screenci): update installation guide

docs/installation.mdx

@@ -11,7 +11,7 @@ Then ScreenCI allows converting these tests into product videos with `record` co
 #### You will learn
 
 - [how to install ScreenCI](#install-screenci)
-- [what `screenci init` creates](#what-gets-created)
+- [what initializing creates](#what-initializing-creates)
 - [how to run the starter script locally](#run-the-example)
 - [how to record the first final video](#record-the-final-result)
 
@@ -51,7 +51,7 @@ If you already know Playwright, the closest mental model is Playwright's own
 browser automation stack, but the output is a maintained video instead of a
 test suite.
 
-## What gets created
+## What initializing creates
 
 The generated project includes the config, starter video script, and a few
 supporting files for a first usable run. If you accepted the optional GitHub

package.json

@@ -82,11 +82,5 @@
     "ora": "^9.3.0",
     "picocolors": "^1.1.1",
     "playwright-recorder-plus": "^0.1.3"
-  },
-  "pnpm": {
-    "onlyBuiltDependencies": [
-      "esbuild",
-      "ffmpeg-static"
-    ]
   }
 }

pnpm-workspace.yaml

@@ -0,0 +1,6 @@
+packages:
+  - .
+
+allowBuilds:
+  esbuild: true
+  ffmpeg-static: true