chore: consolidate documentation — delete status/fix/progress cruft

Before: 335 tracked .md files; top level had 14 README-like docs;
docs/ contained ~234 files, most of them auto/LLM-generated status
reports (ALL_*_COMPLETE*, *_FIX*, DEPLOYMENT_*_FINAL*, etc.).

After: 132 tracked .md files. Repo now has exactly five top-level
docs: README.md, QUICKSTART.md, RUNBOOK.md, CONTRIBUTING.md,
CHANGELOG.md (moved up from docs/).

Keeper philosophy in docs/:
- API, CCIP (ops + security + receiver/router refs), Chainlist refs,
  compliance, deployment (guides not status), database connection,
  legal compliance, metamask integration, production checklist,
  tiered-architecture implementation/setup, reusable-components plan,
  token-mechanism doc, wrap-and-bridge operational reference, plus
  docs/specs/** and docs/api/ / docs/openapi/ trees.

Deleted (git history preserves provenance):
- All 'ALL_*_COMPLETE*' / '*_FIX*' / '*_FIXED*' / '*_FINAL*' /
  '*_STATUS*' / '*_PROGRESS*' / '*_SUMMARY*' files.
- BLOCKSCOUT_*_FIX / _CRASH / _INITIALIZATION / _SCHEMA / _YAML /
  _SKIP / _NEXT_STEPS / _START_AND_BUILD / _DATABASE_CREDENTIALS
  (the last contained passwords).
- CCIP_IMPLEMENTATION_* / CCIP_CURRENT_STATUS / CCIP_GAP_*
  (gap analyses are not a sustained reference).
- NPMPLUS_CREDENTIALS_GUIDE.md (contained creds).
- LETSENCRYPT_CONFIGURATION_GUIDE.md (contained creds; will be
  re-introduced as runbook content post-secrets-scrub).
- docs/diagnostic-reports/, docs/feature-flags/ (run-time artifacts).

README.md: dead links (START_HERE, README_DEPLOYMENT, COMPLETE_DEPLOYMENT,
DEPLOYMENT_COMPLETE_FINAL) replaced with links to the five canonical
top-level docs + docs/ index.

docs/BACKEND_AND_RPC_STATUS.md

@@ -1,147 +0,0 @@
-# Backend and RPC Endpoint Status
-
-**Date**: $(date)  
-**Status**: ✅ **BACKEND RUNNING** | ⚠️ **RPC ENDPOINT PROTECTED**
-
----
-
-## Backend API Server ✅
-
-### Status
-- **Running**: ✅ Yes (PID: Check with `cat /tmp/explorer_backend.pid`)
-- **Port**: 8080
-- **Health Endpoint**: `http://localhost:8080/health` ✅ Working
-- **Stats Endpoint**: `http://localhost:8080/api/v2/stats` ✅ Working
-
-### How to Start
-```bash
-./scripts/start-backend-service.sh
-```
-
-### How to Stop
-```bash
-kill $(cat /tmp/explorer_backend.pid)
-# or
-pkill -f api-server
-```
-
-### How to Check Status
-```bash
-curl http://localhost:8080/health
-```
-
-### Logs
-```bash
-tail -f /tmp/explorer_backend_*.log
-```
-
-### Database Connection
-- **Status**: ⚠️ Password authentication issue (server still runs in degraded mode)
-- **Note**: Backend API works but database queries may fail
-- **Fix**: Set correct `DB_PASSWORD` environment variable
-
----
-
-## RPC Endpoint ⚠️
-
-### Status
-- **URL**: `https://rpc-core.d-bis.org`
-- **HTTP Status**: 530 (Cloudflare Error)
-- **Error Code**: 1033
-- **Type**: JSON-RPC endpoint
-
-### Analysis
-The RPC endpoint returns HTTP 530 with error code 1033, which indicates:
-1. **Cloudflare Protection**: The endpoint is behind Cloudflare
-2. **Possible Causes**:
-   - Rate limiting (too many requests)
-   - Authentication required
-   - IP whitelisting
-   - DDoS protection triggered
-
-### This is Normal
-- RPC endpoints often have protection mechanisms
-- HTTP 530 is a Cloudflare-specific error code
-- The endpoint may still work for authenticated requests
-- Frontend uses this endpoint via ethers.js, which handles authentication
-
-### Verification
-The RPC endpoint is used by:
-- Frontend via `ethers.js` for blockchain interactions
-- MetaMask connections
-- Transaction signing
-
-If the frontend can connect to MetaMask and interact with the blockchain, the RPC endpoint is working correctly.
-
----
-
-## Fixes Applied
-
-### 1. Backend Server ✅
-- ✅ Fixed `nil` context issue in database connection
-- ✅ Created background service startup script
-- ✅ Server now runs and responds to health checks
-- ✅ API endpoints accessible
-
-### 2. RPC Endpoint Check ✅
-- ✅ Updated check script to use JSON-RPC calls
-- ✅ Properly handles Cloudflare errors
-- ✅ Documents that HTTP 530 is expected for protected endpoints
-
----
-
-## Current Status Summary
-
-| Component | Status | Notes |
-|-----------|--------|-------|
-| Backend API | ✅ Running | Port 8080, health check passing |
-| Local API Endpoints | ✅ Working | `/health`, `/api/v2/stats` |
-| Database Connection | ⚠️ Degraded | Password issue, but server runs |
-| RPC Endpoint | ⚠️ Protected | HTTP 530 is normal for Cloudflare-protected RPC |
-| Blockscout API | ✅ Working | All endpoints accessible |
-| CDN Libraries | ✅ Working | All libraries loading correctly |
-
----
-
-## Recommendations
-
-### Backend
-1. **Set Database Password**: 
-   ```bash
-   export DB_PASSWORD="your_actual_password"
-   ./scripts/start-backend-service.sh
-   ```
-
-2. **Check Database**: Verify PostgreSQL is running and password is correct
-
-### RPC Endpoint
-1. **No Action Required**: HTTP 530 is expected for protected RPC endpoints
-2. **Frontend Works**: If frontend can connect to MetaMask, RPC is working
-3. **Rate Limiting**: If issues occur, may need to implement request throttling
-
----
-
-## Verification Commands
-
-```bash
-# Check backend status
-curl http://localhost:8080/health
-
-# Check backend stats
-curl http://localhost:8080/api/v2/stats
-
-# Check backend process
-ps aux | grep api-server
-
-# Check RPC (may return 530 - this is normal)
-curl -X POST "https://rpc-core.d-bis.org" \
-  -H "Content-Type: application/json" \
-  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
-```
-
----
-
-**Conclusion**: Both issues are resolved:
-- ✅ Backend is running and accessible
-- ✅ RPC endpoint HTTP 530 is expected behavior for protected endpoints
-