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.
This commit is contained in:
2026-04-18 18:56:17 +00:00
parent e1c3b40cb0
commit 40c9af678f
205 changed files with 8 additions and 37633 deletions

View File

@@ -1,45 +0,0 @@
# IP Conflict Investigation
**Date**: 2026-01-21
**Issue**: Suspected duplicate IP addresses (192.168.11.166 and/or 192.168.11.167)
---
## Investigation Status
Checking for IP conflicts across:
- All Proxmox containers/VMs
- UDM Pro DHCP leases
- ARP tables
- Network configuration
---
## Findings
Results will be populated after investigation...
---
## MAC Addresses Found
From previous investigation:
- **192.168.11.166**: MAC `BC:24:11:18:1C:5D` (eth0, net0)
- **192.168.11.167**: MAC `BC:24:11:A8:C1:5D` (eth1, net1)
From UDM Pro screenshot:
- **192.168.11.167**: MAC `bc:24:11:8d:ec:b7` (UDM Pro view)
**Note**: MAC address discrepancy detected - investigating...
---
## Next Steps
1. Identify all devices using these IPs
2. Check for duplicate assignments
3. Resolve conflicts if found
---
**Status**: Investigation in progress...