tidaldb/tidal/docs/planning/milestone-0/phase-2/OVERVIEW.md
jx12n 3bcfb3c576 feat: Bazel build, crate docs/ai-lookup, docker images, and engine hardening
- Add BUILD.bazel across tidal, tidal-net, tidal-server, tidalctl for bzlmod build
- Add tidal/ crate docs (README, CHANGELOG, CONTRIBUTING, AGENTS, CLAUDE, API, ARCHITECTURE) and ai-lookup reference
- Add docker standalone/cluster/deploy images, compose, and prometheus config
- Harden WAL (batch format, writer, dedup, diagnostics), text syncer/collectors, and vector registry
- Expand tidalctl CLI and tests; restructure WAL/visibility integration test suites
- Refine tidal-net transport/client/server and tidal-server cluster/scatter-gather
2026-06-07 18:29:38 -06:00

808 B

Milestone 0 · Phase 2 — Tooling & Diagnostics

Objective: give developers minimal introspection tooling that works even when tidalDB is embedded. This phase adds tidalctl plus a metrics endpoint so later milestones can reuse the same plumbing.

Success criteria

  • tidalctl status --path <dir> prints build info, WAL seq, open segments, and builder config snapshot.
  • Metrics exporter (text or JSON) exposes uptime, WAL queue depth, and build hash; tag everything with partition_id=0 to future-proof multi-node rollouts.
  • Tooling uses the same Paths helper from Phase 1 — no duplicated layout logic.

Dependencies: Phase 1 (stable directories + config serialization).

Unblocks: future performance debugging + automated tests that assert health via CLI before/after workloads.