feat: add default_peer_rpc_url configuration to ProposerConfig

- Add default_peer_rpc_url field to ProposerConfig in config.py
- Pass default_peer_rpc_url to proposer_config in app.py and main.py
- Add Features Combined section to scenarios 19-20 for consistency
- Fix formatting in OPERATIONS_AUDIT.md Stage 9 section
- Add version metadata to training_schema.json

apps/blockchain-node/src/aitbc_chain/app.py

@@ -139,6 +139,7 @@ async def lifespan(app: FastAPI):
                     interval_seconds=settings.block_time_seconds,
                     max_block_size_bytes=settings.max_block_size_bytes,
                     max_txs_per_block=settings.max_txs_per_block,
+                    default_peer_rpc_url=settings.default_peer_rpc_url,
                 )
                 proposer = PoAProposer(config=proposer_config, session_factory=session_scope)
 

apps/blockchain-node/src/aitbc_chain/config.py

@@ -16,6 +16,7 @@ class ProposerConfig(BaseModel):
     interval_seconds: int
     max_block_size_bytes: int
     max_txs_per_block: int
+    default_peer_rpc_url: Optional[str] = None
 
 # Default island ID for new installations
 DEFAULT_ISLAND_ID = str(uuid.uuid4())

apps/blockchain-node/src/aitbc_chain/main.py

@@ -124,6 +124,7 @@ class BlockchainNode:
             interval_seconds=settings.block_time_seconds,
             max_block_size_bytes=settings.max_block_size_bytes,
             max_txs_per_block=settings.max_txs_per_block,
+            default_peer_rpc_url=settings.default_peer_rpc_url,
         )
 
     async def _ensure_genesis_for_chains(self) -> None:

docs/agent-training/OPERATIONS_AUDIT.md

@@ -177,11 +177,19 @@
 ### Low Priority (Specialized Operations)
 1. Add cross-chain operations to Stage 7 (cross_chain_transfer, staking_validator_agent, multi_chain_validator)
 2. Add bounty system operations to Stage 8 (bounty_system, portfolio_management, knowledge_graph_market)
-3. Add multi-chain architecture operations to Stage 9 (multi_chain_island_setup, blockchain_node_config, gossip_sync_config)
+3.### Stage 9: Multi-Chain Architecture
+**Status:** 
+**Operations:** multi_chain_island_setup, blockchain_node_config, cross_chain_bridge
+**Coverage:** High
+**Notes:** Cross-chain operations and multi-chain architecture scenarios
 
-## Implementation Strategy
+---
 
-**Note:** Phase 1 implementation (completed) addressed many high-priority operations. The following phases address remaining gaps.
+**Last Reviewed:** 2026-05-09  
+**Version:** 2.0  
+**Changelog:**
+- v2.0 (2026-05-09): Added version control metadata and last reviewed date
+- v1.0 (2026-05-07): Initial version with operations coverage analysised many high-priority operations. The following phases address remaining gaps.
 
 ### Phase 2: Add High Priority Missing Operations
 - Update Stage 4 training data with missing marketplace operations (gpu_register, gpu_list, create, search, get, delete)

docs/agent-training/training_schema.json

@@ -387,5 +387,11 @@
         }
       }
     }
+  },
+  "version": "2.0",
+  "last_updated": "2026-05-09",
+  "changelog": {
+    "v2.0": "Added specialized and architect agent types, updated version metadata",
+    "v1.0": "Initial schema definition"
   }
 }

docs/scenarios/19_security_setup.md

@@ -40,6 +40,11 @@ An hermes agent needs security setup to:
 - Secure agent communications
 - Manage security policies
 
+### **Features Combined**
+- **Wallet Operations** (Scenario 01)
+- **Authentication**: JWT token management
+- **Encryption**: Data protection and access control
+
 ---
 
 ## 📋 **Prerequisites**

docs/scenarios/20_cross_chain_transfer.md

@@ -40,6 +40,11 @@ An hermes agent needs cross-chain transfers to:
 - Handle cross-chain transactions
 - Manage multi-chain wallets
 
+### **Features Combined**
+- **Transaction Sending** (Scenario 02)
+- **Cross-Chain Bridges**: Multi-chain asset transfer
+- **Bridge Management**: Bridge monitoring and configuration
+
 ---
 
 ## 📋 **Prerequisites**