make mining_device into submodule of integration_tests_sv2 crate

Author: plebhash

.github/workflows/ci.yaml

@@ -33,7 +33,6 @@ jobs:
           cargo clippy --manifest-path=pool-apps/Cargo.toml -- -D warnings
           cargo clippy --manifest-path=pool-apps/jd-server/Cargo.toml -- -D warnings
           cargo clippy --manifest-path=miner-apps/Cargo.toml -- -D warnings
-          cargo clippy --manifest-path=miner-apps/mining-device/Cargo.toml -- -D warnings
           cargo clippy --manifest-path=integration-tests/Cargo.toml -- -D warnings
           cargo clippy --manifest-path=bitcoin-core-sv2/Cargo.toml -- -D warnings
 
@@ -58,7 +57,6 @@ jobs:
           cargo fmt --all --manifest-path=pool-apps/Cargo.toml -- --check
           cargo fmt --all --manifest-path=pool-apps/jd-server/Cargo.toml -- --check
           cargo fmt --all --manifest-path=miner-apps/Cargo.toml -- --check
-          cargo fmt --all --manifest-path=miner-apps/mining-device/Cargo.toml -- --check
           cargo fmt --all --manifest-path=integration-tests/Cargo.toml -- --check 
           cargo fmt --all --manifest-path=bitcoin-core-sv2/Cargo.toml -- --check
 

.github/workflows/lockfiles.yaml

@@ -27,7 +27,6 @@ jobs:
           cargo build --manifest-path=pool-apps/Cargo.toml --locked
           cargo build --manifest-path=pool-apps/jd-server/Cargo.toml --locked
           cargo build --manifest-path=miner-apps/Cargo.toml --locked
-          cargo build --manifest-path=miner-apps/mining-device/Cargo.toml --locked
           cargo build --manifest-path=integration-tests/Cargo.toml --locked
 
           # while bitcoin-core-sv2 crate is still a lib crate, no need to lock it so we skip it here

.github/workflows/msrv.yaml

@@ -32,9 +32,6 @@ jobs:
       - name: Build miner applications workspace
         run: cargo build --manifest-path=miner-apps/Cargo.toml --all-features
 
-      - name: Build mining-device (separate workspace)
-        run: cargo build --manifest-path=miner-apps/mining-device/Cargo.toml
-
       - name: Build integration tests workspace
         run: cargo build --manifest-path=integration-tests/Cargo.toml
 
@@ -54,9 +51,6 @@ jobs:
       - name: Check test compilation for miner applications workspace
         run: cargo test --manifest-path=miner-apps/Cargo.toml --no-run
 
-      - name: Check test compilation for mining-device
-        run: cargo test --manifest-path=miner-apps/mining-device/Cargo.toml --no-run
-
       - name: Check test compilation for integration tests workspace
         run: cargo test --manifest-path=integration-tests/Cargo.toml --no-run
 

.github/workflows/tests.yaml

@@ -50,7 +50,5 @@ jobs:
         run: cargo test --manifest-path=pool-apps/jd-server/Cargo.toml
       - name: Test miner applications workspace
         run: cargo test --manifest-path=miner-apps/Cargo.toml
-      - name: Test mining-device (separate workspace)
-        run: cargo test --manifest-path=miner-apps/mining-device/Cargo.toml
       - name: Test bitcoin-core-sv2 crate
-        run: cargo test --manifest-path=bitcoin-core-sv2/Cargo.toml
+        run: cargo test --manifest-path=bitcoin-core-sv2/Cargo.toml

README.md

@@ -29,7 +29,6 @@ If you're looking for the low-level protocol libraries, check out the [`stratum`
 - `miner-apps/` - Miner applications
   - `jd-client/` - Job Declarator Client allows miners to declare custom block templates for decentralized mining
   - `translator/` - Translator Proxy bridges SV1 miners to SV2 pools, enabling protocol transition
-  - `mining-device/` - Mining device simulator for development and testing
 - `stratum-apps/` - Shared application utilities
   - Configuration helpers (TOML, coinbase outputs, logging)
   - Network connection utilities (Noise protocol, plain TCP, SV1 connections)