snapshot before rebranding

docs/sdk/src/guides/async_backing_guide.rs

@@ -61,13 +61,13 @@
 //! pub const SLOT_DURATION: u64 = MILLISECS_PER_BLOCK;
 //! ```
 //!
-//! 4. Configure `cumulus_pallet_teyrchain_system` in the runtime.
+//! 4. Configure `pezcumulus_pallet_teyrchain_system` in the runtime.
 //!
 //! - Define a `FixedVelocityConsensusHook` using our capacity, velocity, and relay slot duration
 //! constants. Use this to set the teyrchain system `ConsensusHook` property.
 #![doc = docify::embed!("../../templates/teyrchain/runtime/src/lib.rs", ConsensusHook)]
 //! ```ignore
-//! impl cumulus_pallet_teyrchain_system::Config for Runtime {
+//! impl pezcumulus_pallet_teyrchain_system::Config for Runtime {
 //!     ..
 //!     type ConsensusHook = ConsensusHook;
 //!     ..
@@ -76,7 +76,7 @@
 //! - Set the teyrchain system property `CheckAssociatedRelayNumber` to
 //! `RelayNumberMonotonicallyIncreases`
 //! ```ignore
-//! impl cumulus_pallet_teyrchain_system::Config for Runtime {
+//! impl pezcumulus_pallet_teyrchain_system::Config for Runtime {
 //! 	..
 //! 	type CheckAssociatedRelayNumber = RelayNumberMonotonicallyIncreases;
 //! 	..
@@ -117,7 +117,7 @@
 //! - In the same file, add `"pezcumulus-primitives-aura/std",` to the `std` feature.
 //!
 //! - Inside the `impl_runtime_apis!` block for your runtime, implement the
-//!   `cumulus_primitives_aura::AuraUnincludedSegmentApi` as shown below.
+//!   `pezcumulus_primitives_aura::AuraUnincludedSegmentApi` as shown below.
 #![doc = docify::embed!("../../templates/teyrchain/runtime/src/apis.rs", impl_can_build_upon)]
 //!
 //! **Note:** With a capacity of 1 we have an effective velocity of ½ even when velocity is
@@ -136,8 +136,8 @@
 //!
 //! This phase consists of plugging in the new lookahead collator node.
 //!
-//! 1. Import `cumulus_primitives_core::ValidationCode` to `node/src/service.rs`.
-#![doc = docify::embed!("../../templates/teyrchain/node/src/service.rs", cumulus_primitives)]
+//! 1. Import `pezcumulus_primitives_core::ValidationCode` to `node/src/service.rs`.
+#![doc = docify::embed!("../../templates/teyrchain/node/src/service.rs", pezcumulus_primitives)]
 //!
 //! 2. In `node/src/service.rs`, modify `pezsc_service::spawn_tasks` to use a clone of `Backend` rather
 //!    than the original

docs/sdk/src/guides/enable_elastic_scaling.rs

@@ -81,7 +81,7 @@
 //!     /// Build with an offset of 1 behind the relay chain best block.
 //!     const RELAY_PARENT_OFFSET: u32 = 1;
 //!
-//!     impl cumulus_pallet_teyrchain_system::Config for Runtime {
+//!     impl pezcumulus_pallet_teyrchain_system::Config for Runtime {
 //!         // ...
 //!         type RelayParentOffset = ConstU32<RELAY_PARENT_OFFSET>;
 //!     }
@@ -89,7 +89,7 @@
 //!
 //! Implement the runtime API to retrieve the offset on the client side.
 //! ```ignore
-//!     impl cumulus_primitives_core::RelayParentOffsetApi<Block> for Runtime {
+//!     impl pezcumulus_primitives_core::RelayParentOffsetApi<Block> for Runtime {
 //!         fn relay_parent_offset() -> u32 {
 //!             RELAY_PARENT_OFFSET
 //!         }
@@ -117,7 +117,7 @@
 //!     /// Relay chain slot duration, in milliseconds.
 //!     const RELAY_CHAIN_SLOT_DURATION_MILLIS: u32 = 6000;
 //!
-//!     type ConsensusHook = cumulus_pallet_aura_ext::FixedVelocityConsensusHook<
+//!     type ConsensusHook = pezcumulus_pallet_aura_ext::FixedVelocityConsensusHook<
 //!         Runtime,
 //!         RELAY_CHAIN_SLOT_DURATION_MILLIS,
 //!         BLOCK_PROCESSING_VELOCITY,

docs/sdk/src/guides/enable_pov_reclaim.rs

@@ -24,9 +24,9 @@
 //! To reclaim excess storage weight, a teyrchain runtime needs the
 //! ability to fetch the size of the storage proof from the node. The reclaim
 //! mechanism uses the
-//! [`storage_proof_size`](cumulus_primitives_proof_size_hostfunction::storage_proof_size)
+//! [`storage_proof_size`](pezcumulus_primitives_proof_size_hostfunction::storage_proof_size)
 //! host function for this purpose. For convenience, pezcumulus provides
-//! [`TeyrchainHostFunctions`](cumulus_client_service::TeyrchainHostFunctions), a set of
+//! [`TeyrchainHostFunctions`](pezcumulus_client_service::TeyrchainHostFunctions), a set of
 //! host functions typically used by pezcumulus-based teyrchains. In the binary crate of your
 //! teyrchain, find the instantiation of the [`WasmExecutor`](pezsc_executor::WasmExecutor) and set the
 //! correct generic type.
@@ -62,7 +62,7 @@
 //!
 //! In your runtime, you will find a list of TransactionExtensions.
 //! To enable the reclaiming,
-//! set [`StorageWeightReclaim`](cumulus_pallet_weight_reclaim::StorageWeightReclaim)
+//! set [`StorageWeightReclaim`](pezcumulus_pallet_weight_reclaim::StorageWeightReclaim)
 //! as a warpper of that list.
 //! It is necessary that this extension wraps all the other transaction extensions in order to catch
 //! the whole PoV size of the transactions.

docs/sdk/src/guides/handling_teyrchain_forks.rs

@@ -71,7 +71,7 @@
 //! 2. Pass this constant to the `teyrchain-system` pallet.
 //!
 //! ```ignore
-//! impl cumulus_pallet_teyrchain_system::Config for Runtime {
+//! impl pezcumulus_pallet_teyrchain_system::Config for Runtime {
 //! 	// Other config items here
 //!     ...
 //! 	type RelayParentOffset = ConstU32<RELAY_PARENT_OFFSET>;
@@ -80,7 +80,7 @@
 //! 3. Implement the `RelayParentOffsetApi` runtime API for your runtime.
 //!
 //! ```ignore
-//! impl cumulus_primitives_core::RelayParentOffsetApi<Block> for Runtime {
+//! impl pezcumulus_primitives_core::RelayParentOffsetApi<Block> for Runtime {
 //!     fn relay_parent_offset() -> u32 {
 //! 		RELAY_PARENT_OFFSET
 //! 	}

docs/sdk/src/guides/your_first_node.rs

@@ -332,7 +332,7 @@ mod tests {
 	#[tokio::test]
 	// This is a regresion test so that we still remain compatible with runtimes that use
 	// `para-id` in chain specs, instead of implementing the
-	// `cumulus_primitives_core::GetTeyrchainInfo`.
+	// `pezcumulus_primitives_core::GetTeyrchainInfo`.
 	async fn omni_node_dev_mode_works_without_getteyrchaininfo() {
 		let dev_chain_spec = std::env::current_dir()
 			.unwrap()