tidaldb/tidal/docs/planning/milestone-0/phase-2/task-01-tidalctl.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

14 lines
573 B
Markdown

# Task 01 — `tidalctl` CLI
**Goal:** ship a tiny, dependency-light binary that inspects an embedded tidalDB home.
## Deliverables
- `tidalctl status --path <dir>` and `tidalctl paths --path <dir>` commands.
- Shared crate for serialization so CLI can read builder `Config` dumps atomically.
- Documentation on how to vendor the CLI into host repos (cargo install or binary download).
## Acceptance Criteria
- Works against both temp homes and long-lived dirs.
- Output is JSON by default with `--pretty` option.
- `cargo test -p tidalctl` exercises happy/error paths.