add docs

README.md

@@ -221,3 +221,6 @@ The subcommand arguments could be:
 
 Please note that for both ways, fetched storages will be saved in the sqlite file specified by `--db` option (`db: ./acala.sqlite` in a config file), if not provided, it will default to `./db-{network}-{block}.sqlite`.
 
+## Try-Runtime CLI
+
+Documentation can be found [here](packages/chopsticks/src/plugins/try-runtime/README.md)

packages/chopsticks/src/plugins/try-runtime/README.md

@@ -0,0 +1,21 @@
+# Try-Runtime CLI
+
+🚧 EXPERIMENTAL FEATURE 🚧
+
+You can use Chopsticks to perform runtime migration checks. It doesn't support PoV measure yet, only weight check is support.
+
+```bash
+# try-runtime print help
+npx @acala-network/chopsticks try-runtime --help
+```
+
+Basic example:
+
+```bash
+npx @acala-network/chopsticks try-runtime \
+  --endpoint <wss://remote.endpoint> \
+  --runtime <wasm_runtime_path> \
+  --checks PreAndPost
+```
+
+__NOTE__: You can also use `--config` to pass arguments

packages/chopsticks/src/plugins/try-runtime/index.ts

@@ -11,7 +11,7 @@ const schema = z.object({
   endpoint: configSchema.shape.endpoint,
   block: configSchema.shape.block,
   db: configSchema.shape.db,
-  ['runtime-log-level']: configSchema.shape['runtime-log-level'],
+  ['runtime-log-level']: configSchema.shape['runtime-log-level'].default(5),
   ['runtime']: z.string({
     description: 'Path to WASM built with feature `try-runtime` enabled',
   }),