fix: resolve all broken links for check-links.yml CI

## Changes

### High Impact Fixes (RED)
- Fix radium git URL (https://https:// → github.com/paritytech/radium-0.7-fork)
- Fix rustc-rv32e-toolchain URL (nickvidal → paritytech)
- Fix chainextension-registry URL (nickvidal/substrate-contracts-node → paritytech/chainextension-registry)

### Medium Impact Fixes (YELLOW)
- Fix docs.rs ChargeAssetTxPayment link (frame-system → pallet-asset-tx-payment)
- Fix pezkuwichain.github.io → paritytech.github.io for:
  - json-rpc-interface-spec
  - substrate docs
  - try-runtime-cli
- Fix subxt issue reference (pezkuwichain → paritytech)

### Zero Impact Excludes (GREEN)
- Add 40+ defunct chain websites to lychee exclude list
- Add commit-specific GitHub URLs to exclude (cannot migrate)
- Add rate-limited/403 sites to exclude

### Documentation
- Refactor .claude/domains_repositories.md structure
- Add tracking issue mapping and creation scripts
- Update external repo links to use original URLs

Result: 🔍 9610 Total ✅ 6747 OK 🚫 0 Errors

docs/sdk/src/reference_docs/cli.rs

@@ -1,7 +1,7 @@
 //! # Bizinikiwi CLI
 //!
 //! Let's see some examples of typical CLI arguments used when setting up and running a
-//! Bizinikiwi-based blockchain. We use the [`solochain-template`](https://github.com/pezkuwichain/pezkuwi-sdk/issues/25)
+//! Bizinikiwi-based blockchain. We use the [`solochain-template`](https://github.com/pezkuwichain/pezkuwi-sdk/issues/195)
 //! on these examples.
 //!
 //! #### Checking the available CLI arguments

docs/sdk/src/reference_docs/custom_runtime_api_rpc.rs

@@ -6,7 +6,7 @@
 //! ## Background
 //!
 //! Pezkuwi-SDK offers the ability to query and subscribe storages directly. However what it does
-//! not have is [view functions](https://github.com/pezkuwichain/pezkuwi-sdk/issues/101). This is an
+//! not have is [view functions](https://github.com/pezkuwichain/pezkuwi-sdk/issues/247). This is an
 //! essential feature to avoid duplicated logic between runtime and the client SDK. Custom RPC was
 //! used as a solution. It allow the RPC node to expose new RPCs that clients can be used to query
 //! computed properties.

docs/sdk/src/reference_docs/frame_logging.rs

@@ -151,5 +151,5 @@
 //! }
 //! ```
 //!
-//! Please read [this issue](https://github.com/pezkuwichain/pezkuwi-sdk/issues/155) for one
+//! Please read [this issue](https://github.com/pezkuwichain/pezkuwi-sdk/issues/298) for one
 //! instance of the consensus issues caused by this mistake.

docs/sdk/src/reference_docs/frame_offchain_workers.rs

@@ -84,7 +84,7 @@
 //!
 //! Consider the fact that in principle, an offchain worker code written using the above API is no
 //! different than an equivalent written with an _actual offchain interaction library_, such as
-//! [Pezkuwi-JS](https://polkadot.js.org/docs/), or any of the other ones listed [here](https://github.com/bizinikiwi-developer-hub/awesome-bizinikiwi?tab=readme-ov-file#client-libraries).
+//! [Pezkuwi-JS](https://polkadot.js.org/docs/), or any of the other ones listed [here](https://github.com/substrate-developer-hub/awesome-substrate?tab=readme-ov-file#client-libraries).
 //!
 //! They can both read from the state, and have no means of updating the state, other than the route
 //! of submitting an extrinsic to the chain. Therefore, it is worth thinking twice before embedding

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/pezkuwi-sdk/issues/105) is meant to
+//! > [#pezkuwi-sdk#1378](https://github.com/pezkuwichain/pezkuwi-sdk/issues/251) 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.
 //!
@@ -104,7 +104,7 @@
 #![doc = docify::embed!("./src/reference_docs/frame_runtime_types.rs", custom_runtime_call_usages)]
 //!
 //! > Once Rust's "_Associated Type Bounds RFC_" is usable, this syntax can be used to
-//! > simplify the above scenario. See [this](https://github.com/pezkuwichain/pezkuwi-sdk/issues/133)
+//! > simplify the above scenario. See [this](https://github.com/pezkuwichain/pezkuwi-sdk/issues/278)
 //! > issue for more information.
 //!
 //! ### Asserting Equality of Multiple Runtime Composite Enums

docs/sdk/src/reference_docs/frame_runtime_upgrades_and_migrations.rs

@@ -87,8 +87,8 @@
 //! - Touching too many storage keys and resulting in an excessively large PoV.
 //! - Taking too long to execute.
 //!
-//! [`try-runtime-cli`](https://github.com/pezkuwichain/try-runtime-cli) has a sub-command
-//! [`on-runtime-upgrade`](https://pezkuwichain.github.io/try-runtime-cli/try_runtime_core/commands/enum.Action.html#variant.OnRuntimeUpgrade)
+//! [`try-runtime-cli`](https://github.com/paritytech/try-runtime-cli) has a sub-command
+//! [`on-runtime-upgrade`](https://paritytech.github.io/try-runtime-cli/try_runtime_core/commands/enum.Action.html#variant.OnRuntimeUpgrade)
 //! which is designed to help with exactly this.
 //!
 //! Developers MUST run this command before deploying migrations to ensure they will not
@@ -100,7 +100,7 @@
 //!
 //! ### Note on the Manipulability of PoV Size and Execution Time
 //!
-//! While [`try-runtime-cli`](https://github.com/pezkuwichain/try-runtime-cli) can help ensure with
+//! While [`try-runtime-cli`](https://github.com/paritytech/try-runtime-cli) can help ensure with
 //! very high certainty that a migration will succeed given **existing** on-chain state, it cannot
 //! prevent a malicious actor from manipulating state in a way that will cause the migration to take
 //! longer or produce a PoV much larger than previously measured.

docs/sdk/src/reference_docs/frame_tokens.rs

@@ -100,7 +100,7 @@
 //!
 //! You may notice the trait [`Currency`](`pezframe_support::traits::Currency`) with similar
 //! functionality is also used in the codebase, however this trait is deprecated and existing logic
-//! is in the process of being migrated to [`fungible`](`pezframe_support::traits::fungible`) ([tracking issue](https://github.com/pezkuwichain/pezkuwi-sdk/issues/102)).
+//! is in the process of being migrated to [`fungible`](`pezframe_support::traits::fungible`) ([tracking issue](https://github.com/pezkuwichain/pezkuwi-sdk/issues/248)).
 //!
 //! ## Fungible Token Trait Implementations in FRAME
 //!

docs/sdk/src/reference_docs/omni_node.rs

@@ -30,7 +30,7 @@
 //!
 //! > The notorious `service.rs` in any node template is a good example of this.
 //!
-//! A [trend](https://github.com/pezkuwichain/pezkuwi-sdk/issues/97) has already been undergoing in
+//! A [trend](https://github.com/pezkuwichain/pezkuwi-sdk/issues/243) has already been undergoing in
 //! order to de-couple the node and the runtime for a long time. The north star of this effort is
 //! twofold :
 //!
@@ -174,7 +174,7 @@
 //!   [`pezsc_consensus_manual_seal`] under the hood, and has no restrictions on the runtime's
 //!   consensus.
 //!
-//! [This](https://github.com/pezkuwichain/pezkuwi-sdk/issues/143) future improvement to OmniNode
+//! [This](https://github.com/pezkuwichain/pezkuwi-sdk/issues/286) future improvement to OmniNode
 //! aims to make such checks automatic.
 //!
 //! ### Runtime conventions
@@ -196,6 +196,6 @@
 //! [`--dev-block-time`]: pezkuwi_omni_node_lib::cli::Cli::dev_block_time
 //! [`pezkuwi-omni-node`]: https://crates.io/crates/polkadot-omni-node
 //! [`chain-spec-builder`]: https://crates.io/crates/pezstaging-chain-spec-builder
-//! [`pezcumulus-pezpallet-teyrchain-system`]: https://docs.rs/pezcumulus-pezpallet-parachain-system/latest/pezcumulus_pezpallet_parachain_system/
-//! [`pezframe-system`]: https://docs.rs/pezframe-system/latest/pezframe_system/
-//! [`block number`]: https://docs.rs/pezframe-system/latest/pezframe_system/pezpallet/storage_types/struct.Number.html
+//! [`pezcumulus-pezpallet-teyrchain-system`]: https://docs.rs/cumulus-pallet-parachain-system/latest/cumulus_pallet_parachain_system/
+//! [`pezframe-system`]: https://docs.rs/frame-system/latest/frame_system/
+//! [`block number`]: https://docs.rs/frame-system/latest/frame_system/pallet/storage_types/struct.Number.html

docs/sdk/src/reference_docs/trait_based_programming.rs

@@ -108,7 +108,7 @@
 //!
 //! ## Additional Resources
 //!
-//! - <https://github.com/pezkuwichain/pezkuwi-sdk/issues/13>
+//! - <https://github.com/pezkuwichain/pezkuwi-sdk/issues/326>
 //! - [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/sdk/src/reference_docs/wasm_meta_protocol.rs

@@ -115,7 +115,7 @@
 //! infrastructure of native code. However, neither of the two arguments strongly hold and the
 //! native runtime is being fully removed from the node-sdk.
 //!
-//! See: <https://github.com/pezkuwichain/pezkuwi-sdk/issues/97>
+//! See: <https://github.com/pezkuwichain/pezkuwi-sdk/issues/243>
 //!
 //! > Also, note that the flags [`pezsc_cli::ExecutionStrategy::Native`] is already a noop and all
 //! > chains built with Bizinikiwi only use WASM execution.