Skip to content

ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.

docs: recovery record + recovered original commit messages

Juan Denisd8bfb5cf41a3
diff --git a/RECOVERY.md b/RECOVERY.md
new file mode 100644
index 00000000..49b8181b
--- /dev/null
+++ b/RECOVERY.md
@@ -0,0 +1,61 @@
+# ServerKit — data-loss recovery record (2026-07-07)
+
+This repository was reconstructed after an accidental `rm -rf` (a staging test
+run from the wrong directory) deleted the working tree **and** `.git`. This file
+documents exactly what was recovered, from where, and what could not be
+restored — so the history and code can be trusted for what they are.
+
+## Sources
+
+| Source | Date | Role |
+|--------|------|------|
+| GitHub `origin/dev` | 2026-07-04 (`07baefb`) | **Full commit history — 1,130 commits.** The baseline everything sits on. |
+| VSS shadow copy | 2026-07-06 22:49 | Working tree; ~half its files were corrupted (zeroed blocks). Held 14 recoverable loose commit objects (plans 29–31). |
+| File-undelete (winfr) | deleted 2026-07-07 | Frontend/docs/scripts — current (July-7), mostly clean. No `.py`, no git. |
+| winfr `/extensive` | — | 18k files; 0 real `.py`, no git data. Ruled out. |
+
+## What was recovered
+
+- **Git history through 2026-07-04** — intact and complete (1,130 commits).
+- **Frontend** — current (July-7 from the undelete, verified clean).
+- **Backend** — CLEAN recovered files were applied; the many that the shadow
+ backup had **corrupted (zeroed) fell back to their July-4 baseline version.**
+ So a large part of the backend is at July-4, not July-6/7.
+- **14 original commit objects** (July-6, plans 29–31) preserved as reference
+ (see `docs/RECOVERED_COMMITS.txt`).
+
+## What was LOST (unrecoverable — the git objects were destroyed everywhere)
+
+- The discrete commits for plans ~32–36 (July-6 night → July-7, ending
+ `bea4373`) — code partly reconstructed, original commit granularity gone.
+- **New July-5–7 backend files that the shadow corrupted, with no July-4
+ fallback, were dropped**, including: `dns_cutover*`, `fleet_doctor*` /
+ `fleet_repair`, `survey_service`, `backup_drill_service`, `chat_webhook_service`,
+ `setup_health_service` / `setup_reconcile_service`, `security_policy_service`,
+ `cron_run_service`, migrations 056–068, `cloudflare.py` /
+ `cloudflare_service.py`, and their tests. These features must be re-done.
+- Backend files that changed July-5–7 but were corrupt in the backup now show
+ their **July-4** content (their recent edits are lost).
+
+## History layout
+
+- `07baefb` (July-4) and earlier — **real GitHub history, untouched.**
+- ~14 commits above it — **reconstruction**: grouped by plan (keyword-matched,
+ best-effort messages) + a catch-all. These are approximate, built only from
+ the CLEAN recovered files; corrupt/lost content is NOT in them.
+- Tag `recovery-blob` — an earlier single-commit snapshot (pre-cleanup; ignore).
+
+## ⚠️ Before trusting this repo
+
+Run the test suites — they will surface anything that reverted to July-4 or is
+missing, so you know what to re-do:
+
+```sh
+cd frontend && npm install && npm run lint && npm run build
+cd backend && python -m venv venv && source venv/bin/activate \
+ && pip install -r requirements.txt && pytest
+```
+
+Raw recovered data is preserved on `D:\` (the shadow copy under
+`ServerKit_RECOVERED`, undelete output under `SK_Recovery` / `SK_ext`) until you
+confirm this repo is good.
diff --git a/docs/RECOVERED_COMMITS.txt b/docs/RECOVERED_COMMITS.txt
new file mode 100644
index 00000000..b860a524
--- /dev/null
+++ b/docs/RECOVERED_COMMITS.txt
@@ -0,0 +1,11 @@
+# Recovered original commit objects (from the July-6 shadow copy)
+# Real pre-loss commits whose objects survived. Messages exact.
+
+2026-07-06 18:16:45 -0400 97fafc7 test(authz): generic structural per-app gate + seal leftover reads (plan 29 Phase 3)
+2026-07-06 18:23:49 -0400 9c88119 docs(security): 4-tier authz model + member-actions admin toggle (plan 29 Phase 5)
+2026-07-06 19:12:19 -0400 b4c0e65 fix(backup): vacuous WordPress drill fails + re-flag old vacuous 'drilled' runs (plan 30 Phase 1)
+2026-07-06 19:15:08 -0400 5dc71d8 feat(backup): stamp drill expectations at backup time + compare at drill (plan 30 Phase 2)
+2026-07-06 19:20:23 -0400 9f559e4 feat(backup): container-aware DB drills + real WordPress DB leg (plan 30 Phase 3)
+2026-07-06 19:23:57 -0400 421b1cb feat(backup): enqueue-time single-flight, WP drill via edit-gate, per-destination sampling (plan 30 Phase 4)
+2026-07-06 19:30:46 -0400 fee4f5c docs(backup): honesty passes — POSIX-only drill note, shallow-verify claim (plan 30 Phase 5)
+2026-07-06 19:49:14 -0400 fff856d feat(dns-cutover): reachable cutover+verify endpoints, server-sourced snapshots, world-restoring revert (plan 31 Phase 1)