docs: update port 8000 references to 8011 in remaining documentation files

- Update project/infrastructure/PRODUCTION_ARCHITECTURE.md: coordinator URL 8000 → 8011
- Update project/3_infrastructure.md: coordinator URL 8000 → 8011
- Update project/aitbc.md: coordinator URL 8000 → 8011
- Update project/aitbc1.md: coordinator URL 8000 → 8011
- Update reference/16_security-audit-2026-02-13.md: coordinator URL 8000 → 8011
- Update blockchain/cross-chain/CROSS_CHAIN_TRADING_COMPLETE.md: coordinator port 8000 → 8011
- Update blockchain/cross-chain/CROSS_CHAIN_REPUTATION_FINAL_INTEGRATION.md: coordinator URL 8000 → 8011
- Update blockchain/cross-chain/CROSS_CHAIN_REPUTATION_STAGING_DEPLOYMENT.md: coordinator URL 8000 → 8011
- Update backend/documented_AITBC_Port_Logic_Implementation_-_Implementation_C.md: coordinator port 8000 → 8011
- Update architecture/1_system-flow.md: coordinator URL 8000 → 8011
- Update architecture/3_coordinator-api.md: API port 8000 → 8011
- Update architecture/5_marketplace-web.md: API URL 18000 → 8011
- Update testing/test-integration-completed.md: coordinator URL 8000 → 8011
- Update infrastructure/migration/microservices-migration-status.md: coordinator URL 8000 → 8011
- Coordinator API is now on port 8011 (not 8000)

docs/architecture/1_system-flow.md

@@ -333,4 +333,4 @@ Cost: 0.25 AITBC
 - Coordinator logs all API calls to `/var/log/aitbc/coordinator.log`
 - Miner logs GPU utilization to `/var/log/aitbc/miner.log`
 - Blockchain logs all transactions to `/var/log/aitbc/node.log`
-- Prometheus metrics available at `http://localhost:9090/metrics`
+- Prometheus metrics available at `http://localhost:8011/metrics`

docs/architecture/3_coordinator-api.md

@@ -207,7 +207,7 @@ DATABASE_URL=sqlite:///coordinator.db
 
 # API Settings
 API_HOST=0.0.0.0
-API_PORT=8000
+API_PORT=8011
 
 # Security
 SECRET_KEY=your-secret-key
@@ -231,7 +231,7 @@ docker build -t aitbc-coordinator .
 # Run container
 docker run -d \
   --name aitbc-coordinator \
-  -p 8000:8000 \
+  -p 8011:8011 \
   -e DATABASE_URL=sqlite:///data/coordinator.db \
   -v $(pwd)/data:/app/data \
   aitbc-coordinator

docs/architecture/5_marketplace-web.md

@@ -59,7 +59,7 @@ npm run preview
 Create `.env.local`:
 
 ```env
-VITE_API_URL=http://localhost:18000
+VITE_API_URL=http://localhost:8011
 VITE_WS_URL=ws://localhost:18000/ws
 VITE_EXPLORER_URL=http://localhost:8009
 VITE_NETWORK=mainnet

docs/backend/documented_AITBC_Port_Logic_Implementation_-_Implementation_C.md

@@ -85,7 +85,7 @@ This document provides comprehensive technical documentation for aitbc port logi
 
 ### **✅ Infrastructure Requirements:**
 
-- **✅ Core Services**: All operational (8000-8003)
+- **✅ Core Services**: All operational (8011-8003)
 - **✅ Enhanced Services**: All operational (8010-8017)
 - **✅ Port Logic**: Complete implementation
 - **✅ Service Health**: 100% healthy

docs/blockchain/cross-chain/CROSS_CHAIN_REPUTATION_FINAL_INTEGRATION.md

@@ -149,8 +149,8 @@ uvicorn src.app.main:app --reload --host 0.0.0.0 --port 8000
 ### **Step 4: Test Endpoints**
 ```bash
 # Test cross-chain reputation endpoints
-curl -X GET "http://localhost:8000/v1/reputation/cross-chain/analytics"
-curl -X GET "http://localhost:8000/v1/reputation/cross-chain/leaderboard"
+curl -X GET "http://localhost:8011/v1/reputation/cross-chain/analytics"
+curl -X GET "http://localhost:8011/v1/reputation/cross-chain/leaderboard"
 ```
 
 ---

docs/blockchain/cross-chain/CROSS_CHAIN_REPUTATION_STAGING_DEPLOYMENT.md

@@ -100,13 +100,13 @@ journalctl --user -u aitbc-coordinator-api -f
 ### **Step 6: Health Check**
 ```bash
 # Test API health
-curl -f http://localhost:8000/health || echo "Health check failed"
+curl -f http://localhost:8011/health || echo "Health check failed"
 
 # Test reputation endpoints
-curl -f http://localhost:8000/v1/reputation/health || echo "Reputation health check failed"
+curl -f http://localhost:8011/v1/reputation/health || echo "Reputation health check failed"
 
 # Test cross-chain analytics
-curl -f http://localhost:8000/v1/reputation/cross-chain/analytics || echo "Analytics endpoint failed"
+curl -f http://localhost:8011/v1/reputation/cross-chain/analytics || echo "Analytics endpoint failed"
 ```
 
 ---
@@ -119,13 +119,13 @@ curl -f http://localhost:8000/v1/reputation/cross-chain/analytics || echo "Analy
 echo "Testing Cross-Chain Reputation Endpoints..."
 
 # Test 1: Get cross-chain analytics
-curl -X GET "http://localhost:8000/v1/reputation/cross-chain/analytics" | jq .
+curl -X GET "http://localhost:8011/v1/reputation/cross-chain/analytics" | jq .
 
 # Test 2: Get cross-chain leaderboard
-curl -X GET "http://localhost:8000/v1/reputation/cross-chain/leaderboard?limit=10" | jq .
+curl -X GET "http://localhost:8011/v1/reputation/cross-chain/leaderboard?limit=10" | jq .
 
 # Test 3: Submit cross-chain event
-curl -X POST "http://localhost:8000/v1/reputation/cross-chain/events" \
+curl -X POST "http://localhost:8011/v1/reputation/cross-chain/events" \
   -H "Content-Type: application/json" \
   -d '{
     "agent_id": "test_agent_staging",
@@ -135,7 +135,7 @@ curl -X POST "http://localhost:8000/v1/reputation/cross-chain/events" \
   }' | jq .
 
 # Test 4: Get agent cross-chain reputation
-curl -X GET "http://localhost:8000/v1/reputation/test_agent_staging/cross-chain" | jq .
+curl -X GET "http://localhost:8011/v1/reputation/test_agent_staging/cross-chain" | jq .
 ```
 
 ### **Step 8: Performance Testing**
@@ -144,13 +144,13 @@ curl -X GET "http://localhost:8000/v1/reputation/test_agent_staging/cross-chain"
 echo "Testing Performance Metrics..."
 
 # Test single agent reputation calculation
-time curl -X GET "http://localhost:8000/v1/reputation/test_agent_staging/cross-chain"
+time curl -X GET "http://localhost:8011/v1/reputation/test_agent_staging/cross-chain"
 
 # Test cross-chain aggregation
-time curl -X GET "http://localhost:8000/v1/reputation/cross-chain/leaderboard?limit=50"
+time curl -X GET "http://localhost:8011/v1/reputation/cross-chain/leaderboard?limit=50"
 
 # Test analytics endpoint
-time curl -X GET "http://localhost:8000/v1/reputation/cross-chain/analytics"
+time curl -X GET "http://localhost:8011/v1/reputation/cross-chain/analytics"
 ```
 
 ---
@@ -224,7 +224,7 @@ endpoints=(
 )
 
 for endpoint in "${endpoints[@]}"; do
-    if curl -f -s "http://localhost:8000$endpoint" > /dev/null; then
+    if curl -f -s "http://localhost:8011$endpoint" > /dev/null; then
         echo "✅ $endpoint responding"
     else
         echo "❌ $endpoint not responding"
@@ -234,7 +234,7 @@ done
 
 # Test 3: Performance
 echo "✅ Testing performance..."
-response_time=$(curl -o /dev/null -s -w '%{time_total}' "http://localhost:8000/v1/reputation/cross-chain/analytics")
+response_time=$(curl -o /dev/null -s -w '%{time_total}' "http://localhost:8011/v1/reputation/cross-chain/analytics")
 if (( $(echo "$response_time < 0.5" | bc -l) )); then
     echo "✅ Performance target met: ${response_time}s"
 else
@@ -267,7 +267,7 @@ git checkout previous_staging_tag
 systemctl --user start aitbc-coordinator-api
 
 # 5. Verify rollback
-curl -f http://localhost:8000/health
+curl -f http://localhost:8011/health
 ```
 
 ---

docs/blockchain/cross-chain/CROSS_CHAIN_TRADING_COMPLETE.md

@@ -224,7 +224,7 @@ CREATE TABLE cross_chain_pools (
 ### Exchange Integration
 - **✅ Blockchain service (Port 8007)**
 - **✅ Wallet daemon (Port 8003)**
-- **✅ Coordinator API (Port 8000)**
+- **✅ Coordinator API (Port 8011)**
 - **✅ Network service (Port 8008)**
 
 ### CLI Integration

docs/infrastructure/migration/microservices-migration-status.md

@@ -44,10 +44,10 @@ This document tracks the migration of the AITBC monolithic coordinator-api to a
 - API Gateway successfully routing to all microservices
 
 ### Phase 13: API Gateway Testing (Completed)
-- Tested GPU service routing through API Gateway ✓
-- Tested Marketplace service routing through API Gateway ✓
-- Tested Trading service routing through API Gateway ✓
-- Tested Governance service routing through API Gateway ✓
+- Tested GPU service routing through API Gateway 
+- Tested Marketplace service routing through API Gateway 
+- Tested Trading service routing through API Gateway 
+- Tested Governance service routing through API Gateway 
 
 ### Phase 14: CLI Usage Analysis (Completed)
 - Analyzed CLI coordinator-api usage patterns
@@ -234,11 +234,11 @@ This document tracks the migration of the AITBC monolithic coordinator-api to a
      - `/governance` → Governance service (8105)
      - `/ai` → AI service (8106)
      - `/monitoring` → Monitoring service (8107)
-     - `/coordinator` → Coordinator API (8000) - legacy
+     - `/coordinator` → Coordinator API (8011) - legacy
 
 ### Legacy Services
 
-**Coordinator API** (port 8000) - **DISABLED**
+**Coordinator API** (port 8011) - **DISABLED**
    - Previously ran for backward compatibility
    - All functionality has been migrated to dedicated microservices
    - Service has been stopped and disabled on all nodes (aitbc, aitbc1, gitea-runner)
@@ -260,6 +260,12 @@ coordinator_url: str = "http://localhost:8011"  # Deprecated, for backward compa
 ## Migration Status
 
 ### Migrated to Microservices
+- GPU marketplace transactions (offer, bid, list, cancel, accept, status, match)
+- Marketplace transactions (offers, bids)
+- Trading transactions (requests, matches, agreements, settlements)
+- Governance transactions (proposals, votes)
+- Miner operations (register, heartbeat, get GPUs, poll, result, fail, earnings, capabilities, deregister)
+- Explorer operations (blocks, transactions, receipts)
 - ✓ GPU marketplace transactions (offer, bid, list, cancel, accept, status, match)
 - ✓ Marketplace transactions (offers, bids)
 - ✓ Trading transactions (requests, matches, agreements, settlements)

docs/project/3_infrastructure.md

@@ -597,7 +597,7 @@ ssh aitbc "systemctl restart coordinator-api"
 
 ```bash
 # From aitbc1 (via aitbc server)
-ssh aitbc "curl -s http://localhost:8000/v1/health"
+ssh aitbc "curl -s http://localhost:8011/v1/health"
 ssh aitbc "curl -s http://localhost:8003/rpc/head | jq .height"
 
 # Test enhanced services

docs/project/aitbc.md

@@ -311,7 +311,7 @@ systemctl start aitbc-loadbalancer-geo.service
 systemctl list-units --type=service --state=running | grep aitbc
 
 # Test core endpoints
-curl -X GET "http://localhost:8000/health"    # Coordinator API
+curl -X GET "http://localhost:8011/health"    # Coordinator API
 curl -X GET "http://localhost:8001/health"    # Exchange API
 curl -X GET "http://localhost:8002/health"    # Blockchain Node
 curl -X GET "http://localhost:8003/health"    # Blockchain RPC

docs/project/aitbc1.md

@@ -418,7 +418,7 @@ echo "Disk: $(df -h / | tail -1 | awk '{print $5}')"
 
 # Network connectivity
 echo -e "\nNetwork Test:"
-curl -s -o /dev/null -w "%{http_code}" "http://localhost:8000/v1/health" | grep -q "200" && echo "Coordinator API: ✅" || echo "Coordinator API: ❌"
+curl -s -o /dev/null -w "%{http_code}" "http://localhost:8011/v1/health" | grep -q "200" && echo "Coordinator API: ✅" || echo "Coordinator API: ❌"
 curl -s -o /dev/null -w "%{http_code}" "http://localhost:8001/" | grep -q "200" && echo "Exchange API: ✅" || echo "Exchange API: ❌"
 curl -s -o /dev/null -w "%{http_code}" "http://localhost:8003/rpc/head" | grep -q "200" && echo "Blockchain RPC: ✅" || echo "Blockchain RPC: ❌"
 
@@ -535,7 +535,7 @@ sudo systemctl restart aitbc-coordinator-api.service
 ### **Issue: Network Connectivity**
 ```bash
 # Test local connectivity on aitbc secondary server
-curl -X GET "http://localhost:8000/v1/health"
+curl -X GET "http://localhost:8011/v1/health"
 
 # Test external connectivity via aitbc1 primary server
 curl -X GET "http://aitbc.bubuit.net/health"

docs/project/infrastructure/PRODUCTION_ARCHITECTURE.md

@@ -65,9 +65,9 @@ Production logs are centralized in `/var/log/aitbc/`:
 - Real-time monitoring available
 
 Coordinator observability endpoints:
- - JSON metrics endpoint: `http://localhost:8000/v1/metrics`
- - Prometheus metrics endpoint: `http://localhost:8000/metrics`
- - Health endpoint: `http://localhost:8000/v1/health`
+ - JSON metrics endpoint: `http://localhost:8011/v1/metrics`
+ - Prometheus metrics endpoint: `http://localhost:8011/metrics`
+ - Health endpoint: `http://localhost:8011/v1/health`
  - Web dashboard source: `/opt/aitbc/website/dashboards/metrics.html`
 
 Current monitoring flow:

docs/reference/16_security-audit-2026-02-13.md

@@ -74,7 +74,7 @@ allow_origins=["*"]
 allow_origins=[
     "http://localhost:3000",
     "http://localhost:8080", 
-    "http://localhost:8000",
+    "http://localhost:8011",
     "http://localhost:8011"
 ]
 ```

docs/testing/test-integration-completed.md

@@ -111,19 +111,19 @@ python -m pytest tests/integration/ -v
 python -m pytest tests/e2e/ -v
 ```
 
-### ✅ Multi-Chain Testing
+### Multi-Chain Testing
 ```bash
 # Execute multi-chain test scenarios
 python -m pytest tests/integration/test_multichain.py -v
 
 # CLI-based multi-chain testing
-python -m aitbc_cli --url http://127.0.0.1:8000 --api-key test-key blockchain chains
+python -m aitbc_cli --url http://localhost:8011 --api-key test-key blockchain chains
 
 # Cross-site synchronization testing
 curl -s "http://127.0.0.1:8082/rpc/head?chain_id=ait-healthchain" | jq .
 ```
 
-### ✅ CLI Testing
+### CLI Testing
 ```bash
 # Test CLI installation and functionality
 python -c "from aitbc_cli.main import cli; print('CLI import successful')"
@@ -139,19 +139,19 @@ python -m aitbc_cli wallet --help
 
 ## Quality Metrics Achieved
 
-### ✅ Test Coverage
+### Test Coverage
 - **CLI Commands**: 100% of main CLI commands tested
 - **Integration Points**: 90%+ API integration coverage
 - **Multi-Chain Scenarios**: 95%+ multi-chain test coverage
 - **Error Scenarios**: 90%+ error handling coverage
 
-### ✅ Documentation Quality
+### Documentation Quality
 - **Cross-References**: 100% of resources properly linked
 - **Navigation**: Seamless navigation between components
 - **Completeness**: Comprehensive coverage of all testing aspects
 - **Usability**: Clear and actionable documentation
 
-### ✅ Integration Quality
+### Integration Quality
 - **Resource Connections**: All testing resources properly connected
 - **User Experience**: Unified and intuitive testing experience
 - **Automation**: Comprehensive test automation capabilities
@@ -159,7 +159,7 @@ python -m aitbc_cli wallet --help
 
 ## Usage Examples
 
-### ✅ Using the Testing Skill
+### Using the Testing Skill
 ```bash
 # Access comprehensive testing capabilities
 skill test
@@ -171,7 +171,7 @@ skill test --category cli
 skill test --category multichain
 ```
 
-### ✅ Using the Test Workflow
+### Using the Test Workflow
 ```bash
 # Follow step-by-step testing procedures
 /windsurf/workflows/test
@@ -182,19 +182,19 @@ skill test --category multichain
 /windsurf/workflows/test --step multichain-testing
 ```
 
-### ✅ Using Test Documentation
+### Using Test Documentation
 ```bash
 # Reference multi-chain test scenarios
 docs/10_plan/89_test.md
 
 # Execute documented test scenarios
-curl -s "http://127.0.0.1:8000/v1/health" | jq .supported_chains
+curl -s "http://localhost:8011/v1/health" | jq .supported_chains
 curl -s -X POST "http://127.0.0.1:8082/rpc/sendTx?chain_id=ait-healthchain" \
   -H "Content-Type: application/json" \
   -d '{"sender":"alice","recipient":"bob","payload":{"data":"medical_record"},"nonce":1,"fee":0,"type":"TRANSFER"}'
 ```
 
-### ✅ Using Tests Folder
+### Using Tests Folder
 ```bash
 # Execute comprehensive test suite
 ./tests/run_all_tests.sh