Development (#172)

* docs: Add CLAUDE_RULES.md with strict rebrand protection rules

- Define immutable rebrand rules that cannot be violated
- Prohibit reverting rebrand for cargo check convenience
- Establish checkpoint and audit trail requirements
- Document correct error handling approach

* refactor: Complete kurdistan-sdk to pezkuwi-sdk rebrand

- Update README.md with pezkuwi-sdk branding
- Replace all kurdistan-sdk URL references with pezkuwi-sdk
- Replace kurdistan-tech with pezkuwichain in workflows
- Update email domains from @kurdistan-tech.io to @pezkuwichain.io
- Rename tool references: kurdistan-tech-publish → pezkuwi-publish
- Update runner names: kurdistan-tech-* → pezkuwichain-*
- Update analytics/forum/matrix domains to pezkuwichain.io
- Keep 'Kurdistan Tech Institute' as organization name
- Keep tech@kurdistan.gov as official government contact

docs/contributor/docker.md

@@ -170,4 +170,4 @@ $ENGINE run --rm -it parity/pezkuwi:latest --version
 ```
 
 This will show you the Pezkuwi version as well as the git commit ref that was used to build your container. You can now
-paste the version information in a [new issue](https://github.com/pezkuwichain/kurdistan-sdk/issues/new/choose).
+paste the version information in a [new issue](https://github.com/pezkuwichain/pezkuwi-sdk/issues/new/choose).

docs/contributor/markdown_linting.md

@@ -1,6 +1,6 @@
 # Markdown linting
 
-Since the introduction of [PR #1309](https://github.com/pezkuwichain/kurdistan-sdk/issues/103), the markdown
+Since the introduction of [PR #1309](https://github.com/pezkuwichain/pezkuwi-sdk/issues/103), the markdown
 files in this repository are checked by a linter for formatting and consistency.
 
 The linter used is [`markdownlint`](https://github.com/DavidAnson/markdownlint) and can be installed locally on your

docs/sdk/src/external_resources.rs

@@ -10,5 +10,5 @@
 //! - [Pezkuwi NFT Marketplace Tutorial by Pezkuwi Fellow Shawn Tabrizi](https://www.shawntabrizi.com/bizinikiwi-collectables-workshop/)
 //! - [HEZ Code School](https://pezkuwichain.io/docs/introduction)
 //! - [Pezkuwi Developers Github Organization](https://github.com/polkadot-developers/)
-//! - [Pezkuwi Blockchain Academy](https://github.com/pezkuwichain/kurdistan_blockchain-akademy)
+//! - [Pezkuwi Blockchain Academy](https://github.com/pezkuwichain/pezkuwi_blockchain-academy)
 //! - [Pezkuwi Wiki](https://wiki.network.pezkuwichain.io/)

docs/sdk/src/guides/enable_pov_reclaim.rs

@@ -3,7 +3,7 @@
 //! This guide will teach you how to enable storage weight reclaiming for a teyrchain. The
 //! explanations in this guide assume a project structure similar to the one detailed in
 //! the [bizinikiwi documentation](crate::pezkuwi_sdk::bizinikiwi#anatomy-of-a-binary-crate). Full
-//! technical details are available in the original [pull request](https://github.com/pezkuwichain/kurdistan-sdk/issues/111).
+//! technical details are available in the original [pull request](https://github.com/pezkuwichain/pezkuwi-sdk/issues/111).
 //!
 //! # What is PoV reclaim?
 //! When a teyrchain submits a block to a relay chain like Pezkuwi or Kusama, it sends the block

docs/sdk/src/guides/your_first_pallet/mod.rs

@@ -201,7 +201,7 @@
 //! Idiomatic FRAME pallets often use Builder pattern to define their initial state.
 //!
 //! > The Pezkuwi Blockchain Academy's Rust entrance exam has a
-//! > [section](https://github.com/pezkuwichain/kurdistan_blockchain-akademy/blob/main/src/m_builder.rs)
+//! > [section](https://github.com/pezkuwichain/pezkuwi_blockchain-academy/blob/main/src/m_builder.rs)
 //! > on this that you can use to learn the Builder Pattern.
 //!
 //! Let's see how we can implement a better test setup using this pattern. First, we define a

docs/sdk/src/pezkuwi_sdk/xcm.rs

@@ -30,7 +30,7 @@
 //!
 //! ## Implementation
 //!
-//! A ready-to-use Rust implementation lives in the [pezkuwi-sdk repo](https://github.com/pezkuwichain/kurdistan-sdk/tree/main/pezkuwi/xcm),
+//! A ready-to-use Rust implementation lives in the [pezkuwi-sdk repo](https://github.com/pezkuwichain/pezkuwi-sdk/tree/main/pezkuwi/xcm),
 //! but will be moved to its own repo in the future.
 //!
 //! Its main components are:

docs/sdk/src/reference_docs/frame_runtime_types.rs

@@ -5,7 +5,7 @@
 //!
 //! > As of now, many of these important types are generated within the internals of
 //! > [`construct_runtime`], and there is no easy way for you to visually know they exist.
-//! > [#pezkuwi-sdk#1378](https://github.com/pezkuwichain/kurdistan-sdk/issues/105) is meant to
+//! > [#pezkuwi-sdk#1378](https://github.com/pezkuwichain/pezkuwi-sdk/issues/105) is meant to
 //! > significantly improve this. Exploring the rust-docs of a runtime, such as [`runtime`] which is
 //! > defined in this module is as of now the best way to learn about these types.
 //!

docs/sdk/src/reference_docs/pezframe_system_accounts.rs

@@ -5,6 +5,6 @@
 //! How `pezframe_system` handles accountIds. Nonce. Consumers and Providers, reference counting.
 
 // - poorly understood topics, needs one great article to rul them all.
-// - https://github.com/pezkuwichain/kurdistan-sdk/issues/17
-// - https://github.com/pezkuwichain/kurdistan-sdk/issues/40
+// - https://github.com/pezkuwichain/pezkuwi-sdk/issues/17
+// - https://github.com/pezkuwichain/pezkuwi-sdk/issues/40
 // - https://exchange.pezkuwichain.app/questions/263/what-is-the-meaning-of-the-account-provider-sufficients-and-consumer

docs/sdk/src/reference_docs/trait_based_programming.rs

@@ -108,7 +108,7 @@
 //!
 //! ## Additional Resources
 //!
-//! - <https://github.com/pezkuwichain/kurdistan-sdk/issues/13>
+//! - <https://github.com/pezkuwichain/pezkuwi-sdk/issues/13>
 //! - [Bizinikiwi Seminar - Traits and Generic Types](https://www.youtube.com/watch?v=6cp10jVWNl4)
 //! - <https://exchange.pezkuwichain.app/questions/2228/type-casting-to-trait-t-as-config>
 #![allow(unused)]

docs/whitepaper/whitepaper.md

@@ -186,7 +186,7 @@ The project operates under the Kurdistan Talent Institute License. It is a utili
 ### Email Contacts
 *   **General Inquiries:** `info@pezkuwichain.io`
 *   **Technical Support:** `tech@pezkuwichain.io`
-*   **Government Relations:** `tech@kurdistan.gov`
+*   **Government Relations:** `tech@kurdistan.gov`, `admin@pezkuwichain.io`
 
 ### Developer Resources
 *   **Developer Portal:** `https://developers.pezkuwichain.io`