Archive FTWDB as an energy-storage test lab

[frahlg]

FTW now embeds DuckDB in Core for history and retains SQLite for configuration. Retire FTWDB as a product and preserve the repository as a frozen energy-storage test lab.

The README points to the adopted Core integration and an archive record covering energy semantics, retries, durable acknowledgements, recovery, retention, format compatibility, memory and migration lessons. Historical architecture, roadmap and release pages now carry retirement notices. The archive includes the September engine comparison, 74 runner/result files with provenance hashes, and the scoped large Core import result. Workstation paths and process dumps are removed; recorded timings and validation stay unchanged.

The original twelve local changed files are preserved byte-for-byte on archive/final-lab-snapshot-2026-09-08, commit 3c701a89fc1c70eba1bb4e39ce2b4d87aec82dc2. That snapshot is separate from the later fixes already on main; this PR does not replace the current storage implementation with the older checkout.

Validation: original file hashes match the preserved snapshot on GitHub; all 74 archived artifact hashes, JSON and Python syntax pass; reported medians reproduce from the raw repeats; local document links and fixture identity pass; git diff --check is clean. The preserved database workloads have not been rerun. Existing portable CI runs on this PR before the repository is archived.

---

Note

Low Risk
Documentation and archived benchmark artifacts only; no changes to the FTW runtime or supported storage path.

Overview
Retires FTWDB as an active product and reframes the repo as a frozen energy-storage test lab. The root and bench READMEs now state the 8 September 2026 archive date, redirect new storage work to FTW Core (DuckDB history + SQLite config), and link the archive record, engine comparison report, and archive/final-lab-snapshot-2026-09-08 branch. Install/release language shifts to “last published” and historical commands are explicitly research-only.

Adds bench/engine-evaluation-2026-09-07/ as a portable snapshot of the 7 September 2026 local engine shootout: sanitized JSON results (timings/validation unchanged; workstation paths and cgroup/process dumps removed; memory peaks kept), provenance.json with per-file SHA transforms, and reproducible harness code (Docker-pinned run.py, SQLite/ DuckDB/ClickHouse adapters, parquet/restore/semantics probes). The superseded report generator is omitted so the archive does not resurrect an outdated product recommendation; runners use FTWDB_EVAL_FIXTURE instead of a machine-local path.

^{Reviewed by Cursor Bugbot for commit bea0a38. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-08T12:02:47.255426Z	bea0a38	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_761a9d89-254d-476d-9534-db4daf85c3e2)