refactor: move brother_node development artifact to dev/test-nodes subdirectory

Development Artifact Cleanup:
✅ BROTHER_NODE REORGANIZATION: Moved development test node to appropriate location
- dev/test-nodes/brother_node/: Moved from root directory for better organization
- Contains development configuration, test logs, and test chain data
- No impact on production systems - purely development/testing artifact

✅ DEVELOPMENT ARTIFACTS IDENTIFIED:
- Chain ID: aitbc-brother-chain (test/development chain)
- Ports: 8010 (P2P) and 8011 (RPC) - different from production
- Environment: .env file with test configuration
- Logs: rpc.log and node.log from development testing session (March 15, 2026)

✅ ROOT DIRECTORY CLEANUP: Removed development clutter from production directory
- brother_node/ moved to dev/test-nodes/brother_node/
- Root directory now contains only production-ready components
- Development artifacts properly organized in dev/ subdirectory

DIRECTORY STRUCTURE IMPROVEMENT:
📁 dev/test-nodes/: Development and testing node configurations
🏗️ Root Directory: Clean production structure with only essential components
🧪 Development Isolation: Test environments separated from production

BENEFITS:
✅ Clean Production Directory: No development artifacts in root
✅ Better Organization: Development nodes grouped in dev/ subdirectory
✅ Clear Separation: Production vs development environments clearly distinguished
✅ Maintainability: Easier to identify and manage development components

RESULT: Successfully moved brother_node development artifact to dev/test-nodes/ subdirectory, cleaning up the root directory while preserving development testing environment for future use.

dev/env/node_modules/ethers/src.ts/providers/contracts.ts

@@ -0,0 +1,42 @@
+import type {
+    Provider, TransactionRequest, TransactionResponse
+} from "./provider.js";
+
+/**
+ *  A **ContractRunner** is a generic interface which defines an object
+ *  capable of interacting with a Contract on the network.
+ *
+ *  The more operations supported, the more utility it is capable of.
+ *
+ *  The most common ContractRunners are [Providers](Provider) which enable
+ *  read-only access and [Signers](Signer) which enable write-access.
+ */
+export interface ContractRunner {
+    /**
+     *  The provider used for necessary state querying operations.
+     *
+     *  This can also point to the **ContractRunner** itself, in the
+     *  case of an [[AbstractProvider]].
+     */
+    provider: null | Provider;
+
+    /**
+     *  Required to estimate gas.
+     */
+    estimateGas?: (tx: TransactionRequest) => Promise<bigint>;
+
+    /**
+     * Required for pure, view or static calls to contracts.
+     */
+    call?: (tx: TransactionRequest) => Promise<string>;
+
+    /**
+     *  Required to support ENS names
+     */
+    resolveName?: (name: string) => Promise<null | string>;
+
+    /**
+     *  Required for state mutating calls
+     */
+    sendTransaction?: (tx: TransactionRequest) => Promise<TransactionResponse>;
+}