Rebrand: polkadot → pezkuwi build fixes

- Fixed TypeScript type assertion issues
- Updated imports from api-augment/substrate to api-augment/bizinikiwi
- Fixed imgConvert.mjs header and imports
- Added @ts-expect-error for runtime-converted types
- Fixed all @polkadot copyright headers to @pezkuwi

web/public/docs/sdk/src/guides/your_first_runtime.rs

@@ -1,25 +1,25 @@
 //! # Your first Runtime
 //!
-//! This guide will walk you through the steps to add your pallet to a runtime.
+//! This guide will walk you through the steps to add your pezpallet to a runtime.
 //!
 //! The good news is, in [`crate::guides::your_first_pallet`], we have already created a _test_
 //! runtime that was used for testing, and a real runtime is not that much different!
 //!
 //! ## Setup
 //!
-//! A runtime shares a few similar setup requirements as with a pallet:
+//! A runtime shares a few similar setup requirements as with a pezpallet:
 //!
 //! * importing [`frame`], [`codec`], and [`scale_info`] crates.
-//! * following the [`std` feature-gating](crate::pezkuwi_sdk::substrate#wasm-build) pattern.
+//! * following the [`std` feature-gating](crate::pezkuwi_sdk::bizinikiwi#wasm-build) pattern.
 //!
 //! But, more specifically, it also contains:
 //!
-//! * a `build.rs` that uses [`substrate_wasm_builder`]. This entails declaring
+//! * a `build.rs` that uses [`bizinikiwi_wasm_builder`]. This entails declaring
 //!   `[build-dependencies]` in the Cargo manifest file:
 //!
 //! ```ignore
 //! [build-dependencies]
-//! substrate-wasm-builder = { ... }
+//! bizinikiwi-wasm-builder = { ... }
 //! ```
 //!
 //! >Note that a runtime must always be one-runtime-per-crate. You cannot define multiple runtimes
@@ -30,7 +30,7 @@
 //! ## Your First Runtime
 //!
 //! The first new property of a real runtime that it must define its
-//! [`frame::runtime::prelude::RuntimeVersion`]:
+//! [`pezframe::runtime::prelude::RuntimeVersion`]:
 #![doc = docify::embed!("./packages/guides/first-runtime/src/lib.rs", VERSION)]
 //!
 //! The version contains a number of very important fields, such as `spec_version` and `spec_name`
@@ -39,7 +39,7 @@
 //! [`crate::reference_docs::frame_runtime_upgrades_and_migrations`].
 //!
 //! Then, a real runtime also contains the `impl` of all individual pallets' `trait Config` for
-//! `struct Runtime`, and a [`frame::runtime::prelude::construct_runtime`] macro that amalgamates
+//! `struct Runtime`, and a [`pezframe::runtime::prelude::construct_runtime`] macro that amalgamates
 //! them all.
 //!
 //! In the case of our example:
@@ -49,13 +49,13 @@
 //! their `Config` need to be implemented for `struct Runtime`:
 #![doc = docify::embed!("./packages/guides/first-runtime/src/lib.rs", config_impls)]
 //!
-//! Notice how we use [`frame::pallet_macros::derive_impl`] to provide "default" configuration items
-//! for each pallet. Feel free to dive into the definition of each default prelude (eg.
-//! [`frame::prelude::frame_system::pallet::config_preludes`]) to learn more which types are exactly
-//! used.
+//! Notice how we use [`pezframe::pezpallet_macros::derive_impl`] to provide "default" configuration
+//! items for each pezpallet. Feel free to dive into the definition of each default prelude (eg.
+//! [`pezframe::prelude::pezframe_system::pezpallet::config_preludes`]) to learn more which types are
+//! exactly used.
 //!
 //! Recall that in test runtime in [`crate::guides::your_first_pallet`], we provided `type AccountId
-//! = u64` to `frame_system`, while in this case we rely on whatever is provided by
+//! = u64` to `pezframe_system`, while in this case we rely on whatever is provided by
 //! [`SolochainDefaultConfig`], which is indeed a "real" 32 byte account id.
 //!
 //! Then, a familiar instance of `construct_runtime` amalgamates all of the pallets:
@@ -66,12 +66,12 @@
 //! steps of crafting a runtime are related to achieving exactly this.
 //!
 //! First, we define a number of types that eventually lead to the creation of an instance of
-//! [`frame::runtime::prelude::Executive`]. The executive is a handy FRAME utility that, through
+//! [`pezframe::runtime::prelude::Executive`]. The executive is a handy FRAME utility that, through
 //! amalgamating all pallets and further types, implements some of the very very core pieces of the
 //! runtime logic, such as how blocks are executed and other runtime-api implementations.
 #![doc = docify::embed!("./packages/guides/first-runtime/src/lib.rs", runtime_types)]
 //!
-//! Finally, we use [`frame::runtime::prelude::impl_runtime_apis`] to implement all of the runtime
+//! Finally, we use [`pezframe::runtime::prelude::impl_runtime_apis`] to implement all of the runtime
 //! APIs that the runtime wishes to expose. As you will see in the code, most of these runtime API
 //! implementations are merely forwarding calls to `RuntimeExecutive` which handles the actual
 //! logic. Given that the implementation block is somewhat large, we won't repeat it here. You can
@@ -101,7 +101,7 @@
 //!
 //! Once you compile a crate that contains a runtime as above, simply running `cargo build` will
 //! generate the wasm blobs and place them under `./target/release/wbuild`, as explained
-//! [here](crate::pezkuwi_sdk::substrate#wasm-build).
+//! [here](crate::pezkuwi_sdk::bizinikiwi#wasm-build).
 //!
 //! ## Genesis Configuration
 //!
@@ -110,8 +110,8 @@
 //! what is known as a  **Chain Specification, or chain spec for short**. A chain spec is the
 //! primary way to run a new chain.
 //!
-//! These APIs are defined in [`sp_genesis_builder`], and are re-exposed as a part of
-//! [`frame::runtime::apis`]. Therefore, the implementation blocks can be found inside of
+//! These APIs are defined in [`pezsp_genesis_builder`], and are re-exposed as a part of
+//! [`pezframe::runtime::apis`]. Therefore, the implementation blocks can be found inside of
 //! `impl_runtime_apis!` similar to:
 //!
 //! ```ignore
@@ -136,13 +136,14 @@
 //! The implementation of these function can naturally vary from one runtime to the other, but the
 //! overall pattern is common. For the case of this runtime, we do the following:
 //!
-//! 1. Expose one non-default preset, namely [`sp_genesis_builder::DEV_RUNTIME_PRESET`]. This means
-//!    our runtime has two "presets" of genesis state in total: `DEV_RUNTIME_PRESET` and `None`.
+//! 1. Expose one non-default preset, namely [`pezsp_genesis_builder::DEV_RUNTIME_PRESET`]. This
+//!    means our runtime has two "presets" of genesis state in total: `DEV_RUNTIME_PRESET` and
+//!    `None`.
 #![doc = docify::embed!("./packages/guides/first-runtime/src/lib.rs", preset_names)]
 //!
 //! For `build_state` and `get_preset`, we use the helper functions provide by frame:
 //!
-//! * [`frame::runtime::prelude::build_state`] and [`frame::runtime::prelude::get_preset`].
+//! * [`pezframe::runtime::prelude::build_state`] and [`pezframe::runtime::prelude::get_preset`].
 //!
 //! Indeed, our runtime needs to specify what its `DEV_RUNTIME_PRESET` genesis state should be like:
 #![doc = docify::embed!("./packages/guides/first-runtime/src/lib.rs", development_config_genesis)]
@@ -164,10 +165,10 @@
 //!    [`crate::reference_docs::frame_runtime_upgrades_and_migrations`].
 //! 4. Learn more about adding and implementing runtime apis in
 //!    [`crate::reference_docs::custom_runtime_api_rpc`].
-//! 5. To see a complete example of a runtime+pallet that is similar to this guide, please see
+//! 5. To see a complete example of a runtime+pezpallet that is similar to this guide, please see
 //!    [`crate::pezkuwi_sdk::templates`].
 //!
-//! [`SolochainDefaultConfig`]: struct@frame_system::pallet::config_preludes::SolochainDefaultConfig
+//! [`SolochainDefaultConfig`]: struct@pezframe_system::pezpallet::config_preludes::SolochainDefaultConfig
 
 #[cfg(test)]
 mod tests {