openvibe-shared 3.0.0: delete the SQLite config store and SQLite analytics (#54)

OP OpenVibers committed 10 Oct 2026 · tag v3.0.0 · 0 files, +0 −0

* openvibe-shared 3.0.0: delete the SQLite config store and SQLite analytics

Plan T1, "Delete the migration era", Shared part (the deletion ledger's "Shared SQLite stores"). Every consumer runs on PostgreSQL. Live and Media hand `createConfigStore` an openvibe-sdk/db handle, and Live's analytics use `analytics/pg`. So the SQLite implementations go. This is a major version: removed exports.

**Removed:**
- The SQLite config store: `createConfigStore` now requires an openvibe-sdk/db handle and delegates to `config-pg.js`.
- `analytics/tracker.js` (the SQLite `AnalyticsTracker`), `analytics/schema.js`, `analytics/prune-cli.js`, and the SQLite retention and scrub functions. `analytics/retention` keeps `MAX_DAYS` and its backend-independent helpers.
- `better-sqlite3`.
- `test/config.test.js` and `test/analytics-cli.test.js` (SQLite-only); the SQLite halves of the privacy and retention tests.

**Moved, not changed:**
- `config-core.js` holds the helpers `config-pg.js` used to take from `config.js`'s `_internal`.
- `analytics/core.js` holds what `analytics/pg.js` inherited from the SQLite tracker (`sqlTime`, `dayOf`, `hourOf`, the request reduction).
- The PostgreSQL SQL, table names, method names and return shapes are unchanged.

**Consumers checked against this branch** (packed and installed without saving):
- Live: `site-config`, `analytics-privacy`, `network-analytics` and the analytics tests pass. `shared-pins` only fails its "node_modules matches the pin" check, as expected for a hand-installed tarball. Its `RESOLVE_ONLY` entry for `analytics/prune-cli` must go in Live's bump PR.
- Media: `tier-config`, `placement-storage-policy`, `placement-cost-tiers` and `object-tiering` pass.
- Nothing else in the estate imports `openvibe-shared/config` or the SQLite analytics.

Built by a Codex job, reviewed here. Full suite 56/56, with acorn installed for floating-promises and the HTTP sections the agent's sandbox could not run.

* CI consumer check: require analytics/pg instead of the removed analytics/prune-cli

This commit has no diff to show.