refactor: consolidate blockchain explorer into single app and update backup ignore patterns

- Remove standalone explorer-web app (README, HTML, package files)
- Add /web endpoint to blockchain-explorer for web interface access
- Update .gitignore to exclude application backup archives (*.tar.gz, *.zip)
- Add backup documentation files to .gitignore (BACKUP_INDEX.md, README.md)
- Consolidate explorer functionality into main blockchain-explorer application

dev/cli/CLI_IMPROVEMENTS.md

@@ -0,0 +1,89 @@
+# CLI Improvements Documentation
+
+## Current Status
+- **CLI Functionality**: 60% working
+- **Working Features**: Version, Help, Config, Wallet, Environment tests
+- **Non-Working Features**: API integration, Marketplace, Agents, Blockchain
+
+## Development Environment Setup
+
+### Files Created
+1. `cli-test-config.yaml` - Test configuration
+2. `cli-staging-config.yaml` - Staging configuration with mock server
+3. `mock-cli-server.py` - Mock server for testing
+4. `test-cli-functionality.sh` - Current CLI testing script
+5. `test-cli-staging.sh` - Staging CLI testing script
+
+### Usage
+
+#### Test Current CLI Functionality
+```bash
+cd /home/oib/windsurf/aitbc/cli-dev
+./test-cli-functionality.sh
+```
+
+#### Test CLI with Mock Server
+```bash
+cd /home/oib/windsurf/aitbc/cli-dev
+./test-cli-staging.sh
+```
+
+## Identified Issues
+
+### 1. API Integration (404 errors)
+- **Problem**: CLI expects `/v1/health` but gets 404
+- **Root Cause**: API endpoint mismatch
+- **Solution**: Add root `/health` endpoint
+
+### 2. Marketplace Operations (Network errors)
+- **Problem**: CLI gets JSON parsing errors
+- **Root Cause**: Wrong endpoint paths
+- **Solution**: Add `/v1/marketplace/gpus` endpoint
+
+### 3. Agent Operations (Network errors)
+- **Problem**: CLI gets network errors
+- **Root Cause**: Missing agent router
+- **Solution**: Include agent router in main.py
+
+### 4. Blockchain Operations (Connection refused)
+- **Problem**: CLI cannot connect to blockchain node
+- **Root Cause**: Missing blockchain endpoints
+- **Solution**: Add blockchain router
+
+## Testing Strategy
+
+### Phase 1: Mock Server Testing
+- Use mock server to test CLI functionality
+- Validate CLI commands work with correct responses
+- No impact on production
+
+### Phase 2: Staging Testing
+- Test with staging configuration
+- Validate endpoint compatibility
+- Safe testing environment
+
+### Phase 3: Production Testing
+- Careful testing with backup
+- Monitor for issues
+- Quick rollback capability
+
+## Next Steps
+
+1. **Immediate**: Use mock server for CLI testing
+2. **Short Term**: Fix API endpoints in staging
+3. **Medium Term**: Implement fixes in production
+4. **Long Term**: Comprehensive CLI improvements
+
+## Risk Assessment
+
+- **Mock Server**: Zero risk
+- **Staging Testing**: Low risk
+- **Production Changes**: Medium risk
+- **Full Overhaul**: High risk
+
+## Success Metrics
+
+- **CLI Functionality**: Target 90%
+- **Test Coverage**: Target 100%
+- **Production Stability**: Maintain 100%
+- **User Impact**: Zero impact