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/hardhat/dist/src/config.js

@@ -0,0 +1,66 @@
+export * from "./internal/core/config.js";
+// NOTE: We import the builtin plugins in this module, so that their
+// type-extensions are loaded when the user imports `hardhat/config`.
+import "./internal/builtin-plugins/index.js";
+import { throwUsingHardhat2PluginError } from "./internal/using-hardhat2-plugin-errors.js";
+/**
+ * Defines a Hardhat user config.
+ *
+ * This function is normally expected to be used in your `hardhat.config.ts` file
+ * like this:
+ *
+ * ```js
+ * import { defineConfig } from "hardhat/config";
+ *
+ * export default defineConfig({
+ *   // Your config ...
+ * });
+ * ```
+ * @note If using `--isolatedDeclarations`, you should import the type
+ * `HardhatUserConfig` from `hardhat/config` instead of relying on the return
+ * type of this function.
+ *
+ * @param config Your config. See {@link https://hardhat.org/config}.
+ * @returns The config.
+ */
+export function defineConfig(config) {
+    // In reality, this function doesn't do anything, it just returns your config.
+    // Why does it exist?
+    //  - It gives autocomplete of the config both to js and ts users.
+    //  - It allows you to define and export the config in a single statement,
+    //    having type-safety without much more verbosity.
+    //  - While it doesn't do anything, it feels mandatory, so most users will
+    //    use it and have a better user experience.
+    return config;
+}
+/**
+ * @deprecated This function is part of the Hardhat 2 plugin API.
+ */
+export function extendConfig(..._args) {
+    throwUsingHardhat2PluginError();
+}
+/**
+ * @deprecated This function is part of the Hardhat 2 plugin API.
+ */
+export function extendEnvironment(..._args) {
+    throwUsingHardhat2PluginError();
+}
+/**
+ * @deprecated This function is part of the Hardhat 2 plugin API.
+ */
+export function extendProvider(..._args) {
+    throwUsingHardhat2PluginError();
+}
+/**
+ * @deprecated This function is part of the Hardhat 2 plugin API.
+ */
+export function scope(..._args) {
+    throwUsingHardhat2PluginError();
+}
+/**
+ * @deprecated This function is part of the Hardhat 2 plugin API.
+ */
+export function subtask(..._args) {
+    throwUsingHardhat2PluginError();
+}
+//# sourceMappingURL=config.js.map