update for sdk v0.6.0, use bun (#48)

* update docs for v0.5.5

* update docs for v0.5.5

* update for v0.6.0, add back bun

* chore: minor fixes

---------

Co-authored-by: Aashutosh Rathi <[email protected]>

Author: eshaan7

docs/pages/build/changelog.mdx

@@ -1,11 +1,34 @@
 # Changelog [What's new]
 
+## v0.6.0
+
+#### Breaking changes
+
+> See [upgrade guide](/build/upgrade-guide).
+
+- Add new `State.STF` and `State.Hook` static methods to define STFs and Hooks.
+- Remove `ActionSchema`. Input schemas are now [defined directly inside the STFs](/build/framework/state-machine/state-transitions#passing-inputs-to-an-stf).
+- Action signatures are now enforced over both STF name and inputs, as opposed to inputs only earlier.
+
+#### Bug Fixes
+
+- Fix a bug where if a custom sequencer strategy were to discard actions, they would get removed from the action pool. Such discarded actions, if any, are now re-enqueued to the front of the action pool.
+
+#### Improvements
+
+- Add `sdkVersion` field to [`ExternalConfig`](/build/framework/config#accessing-config-values).
+- Expose [`ChainData`](/build/framework/type-definitions#chaindata) in [`getOrderedActions`](/build/framework/sequencer#custom-ordering-strategy) method of a sequencer strategy for increased context.
+
+#### Other changes
+
+- Updates in [CLI](https://www.npmjs.com/package/@stackr/cli) `v0.1.8`, [ESLint Plugin](https://www.npmjs.com/package/@stackr/eslint-plugin) `v0.1.2` and Playground for the above breaking changes. (Use latest for both for compatibility)
+
 ## v0.5.5
 
 #### Breaking changes
 
-- The [`getOrderedActions`](/build/framework/sequencer#custom-ordering-strategy) method of a sequencer strategy now accepts a list of actions 
-as a `Readonly<AcknowledgedAction[]>` type and is supposed only to return the ordered list of action hashes as opposed to `Action` objects earlier.
+- The [`getOrderedActions`](/build/framework/sequencer#custom-ordering-strategy) method of a sequencer strategy now accepts a list of actions
+  as a `Readonly<AcknowledgedAction[]>` type and is supposed only to return the ordered list of action hashes as opposed to `Action` objects earlier.
 
 #### Bug Fixes
 

docs/pages/build/cli/init.mdx

@@ -45,7 +45,6 @@ The project directory will look something like this depending on the template -
 │   ├── stackr
 │   │   ├── machine.ts
 │   │   ├── mru.ts
-│   │   ├── schemas.ts
 │   │   ├── state.ts
 │   │   └── transitions.ts
 │   ├── index.ts

docs/pages/build/faq.mdx

@@ -26,9 +26,6 @@ They've fixed the issue in `v1.1.28` and you can upgrade by running:
 bun upgrade
 bun --version # check that you are on version >= 1.1.28
 ```
-
-However, moving forward we recommend using `tsx` over `bun run` for running the MRU server. You may still use Bun for package management.
-
 :::
 
 If you have any more questions, please reach out to us on our [Discord](https://discord.stackrlabs.xyz/) server.

docs/pages/build/framework/action/action-schema.mdx

@@ -28,72 +28,30 @@ However, Micro-Rollup developers are free to design their actions to include a c
 In a gist, an action has the following properties to be able to mutate a state machine:
 
 ```typescript
-export interface IAction {
-  identifier: string;
-  msgSender: AddressLike;
-  signature: SignatureLike;
-  payload: AllowedInputTypes;
+interface IAction {
+  name: string;
+  msgSender: string;
+  signature: string;
+  inputs: AllowedInputTypes;
 }
 ```
 
-- `identifier`: A unique identifier for the action. This allows the state machine to redirect it to the correct state transition function.
+- `name`: Name of the state transition function.
 - `msgSender`: The address of the user who sent the action.
 - `signature`: The signature of the action. This is used to authenticate the user who signed the action.
-- `payload`: The data of the action. This is the actual data that the action is supposed to mutate the state with.
+- `inputs`: The user-provided payload of the action. This is the actual data that the action is supposed to mutate the state with.
 
-## Action Creation
+## Action Creation & Submission
 
-Actions are constructed via `ActionSchema`s. More on this [here](/build/framework/action/action-schema).
-
-Once you've generated the schema for your action, you can use the `actionFrom` function on your schema to create a new action.
-The schema ensures that your action is well-formed and adheres to the schema's rules while also being EIP 712 'signable'.
-Here's an example of how you can create an action from a schema:
-
-```typescript
-const action = NewSchema.actionFrom({
-  inputs,
-  signature,
-  msgSender: wallet.address,
-});
-```
-
-- The `inputs` are of whatever type you defined in your schema.
-- The `signature` is an EIP712 signature over the action's `inputs`. This is used to authenticate the user who signed the action.
-  It can be created using your action schema like this:
-
-```typescript
-const signature = await wallet.signTypedData(
-  schema.domain,
-  schema.EIP712TypedData.types,
-  payload
-);
-```
-
-- The `msgSender` is the address of the user who sent the action.
-
-Your action is now ready for submission!
-
-## Action Submission
-
-Your action can now be submitted to the Micro-Rollup's State Machine.
-All this requires calling the `submitAction` function on your Micro-Rollup.
-
-```typescript
-let ack = await rollup.submitAction("<REDUCER-NAME>", action);
-```
-
-We also pass in the name of the reducer that will be handling your action.
-These are state transition functions that you will be defining in the `src/stackr/transitions.ts` file.
-On succesful submission, you will recieve an `Acknowledment` object that acts like a transaction receipt and is also considered a `C0` confirmation.
-This is proof of the action being successfully submitted to the state machine.
+This is covered as part of the [Counter Rollup Tutorial](/build/guides/tutorials/counter#interacting-with-the-rollup).
 
 :::note
 An action's payload size should not exceed ~128kb. This limit is enforced to keep batch size well within the means of different DA layer's maximum supported blob size. 
 :::
 
 ## EIP-712 Signing
 
-EIP 712 is a standard for signing structured data. It is used to sign actions in this version of Stackr.
+[EIP-712](https://eips.ethereum.org/EIPS/eip-712) is a standard for signing structured data. It is used to sign actions in this version of Stackr.
 This also makes Stackr Actions compatible with existing browser wallet extensions and other EVM-friendly wallet implementations.
 
 ## Action Execution

docs/pages/build/framework/action/introduction.mdx

@@ -181,5 +181,6 @@ type ExternalConfig = {
   preferredDA: DA;
   accounts: PublicAccount[];
   logLevel: LogLevel;
+  sdkVersion: string;
 };
 ```

docs/pages/build/framework/action/serialized-action.mdx

@@ -12,7 +12,6 @@ import { ConfirmationEvents } from "@stackr/sdk";
 
 const rollup = await MicroRollup({
   config: stackrConfig,
-  actionSchemas: [UpdateCounterSchema],
   stateMachines: [machine],
 });
 
@@ -117,6 +116,8 @@ Occurs when an action is picked by the sequencer.
 **Event Arguments:** `SequencerPickActionEventArgs`
 
 - `actionHash`: Hash of the action picked.
+- `blockParentHash`: Hash of the parent block.
+- `blockHeight`: Current block height.
 
 ### `SequencerEvents.ORDER_ACTIONS`
 
@@ -127,6 +128,8 @@ Triggered when actions are ordered by the sequencer.
 - `actionHashes`: List of action hashes ordered.
 - `actionRootHash`: Root hash of the ordered actions.
 - `signature`: Signature verifying the order.
+- `blockParentHash`: Hash of the parent block.
+- `blockHeight`: Current block height.
 
 ### `SequencerEvents.PROPOSE_BLOCK`