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/DEPLOYMENT_PROGRESS_UPDATE.md

@@ -1,94 +0,0 @@
-# Deployment Progress Update
-
-**Date**: 2025-12-24  
-**Status**: 3/5 Contracts Deployed Successfully
-
----
-
-## ✅ Successfully Deployed Contracts
-
-### 1. ComplianceRegistry
-- **Address**: `0xf52504A9c0DAFB0a35dEE0129D6991AA27E734c8`
-- **Status**: ✅ Deployed
-- **Deployer**: `0x4A666F96fC8764181194447A7dFdb7d471b301C8`
-
-### 2. CompliantUSDT
-- **Address**: `0xFe6023265F3893C4cc98CE5Fe7ACBd79DB9cbB2D`
-- **Status**: ✅ Deployed
-- **Block**: 209570
-- **Gas Used**: 1,693,323
-- **Initial Supply**: 1,000,000 cUSDT
-- **Decimals**: 6
-
-### 3. CompliantUSDC
-- **Address**: `0x044032f30393c60138445061c941e2FB15fb0af2`
-- **Status**: ✅ Deployed
-- **Block**: 209579
-- **Gas Used**: 1,693,299
-- **Initial Supply**: 1,000,000 cUSDC
-- **Decimals**: 6
-
----
-
-## ⏳ Pending Deployments
-
-### 4. TokenRegistry
-- **Status**: ⏳ Needs `--via-ir` flag
-- **Issue**: "Stack too deep" error
-- **Fix**: Add `--via-ir` to deployment command
-
-### 5. FeeCollector
-- **Status**: ⏳ Pending
-- **Issue**: May need `--via-ir` flag
-
----
-
-## 🔧 Fixes Needed
-
-### TokenRegistry Deployment
-
-The deployment failed with "Stack too deep" error. Use:
-
-```bash
-cd /home/intlc/projects/proxmox/smom-dbis-138
-source .env
-
-forge script script/DeployTokenRegistry.s.sol:DeployTokenRegistry \
-  --rpc-url $RPC_URL \
-  --broadcast \
-  --legacy \
-  --gas-price 20000000000 \
-  --via-ir \
-  -vv
-```
-
-**Note**: Added `--via-ir` flag to fix "Stack too deep" error.
-
----
-
-## 📋 Next Steps
-
-1. ✅ Deploy TokenRegistry with `--via-ir` flag
-2. ✅ Deploy FeeCollector (may also need `--via-ir`)
-3. ⏳ Register CompliantUSDT in ComplianceRegistry
-4. ⏳ Register CompliantUSDC in ComplianceRegistry
-5. ⏳ Register CompliantUSDT in TokenRegistry
-6. ⏳ Register CompliantUSDC in TokenRegistry
-7. ⏳ Verify all deployments
-
----
-
-## 📝 Save to .env
-
-Add these to your `.env` file:
-
-```bash
-COMPLIANCE_REGISTRY_ADDRESS=0xf52504A9c0DAFB0a35dEE0129D6991AA27E734c8
-COMPLIANT_USDT_ADDRESS=0xFe6023265F3893C4cc98CE5Fe7ACBd79DB9cbB2D
-COMPLIANT_USDC_ADDRESS=0x044032f30393c60138445061c941e2FB15fb0af2
-```
-
----
-
-**Last Updated**: 2025-12-24
-