feat: taskstore v2 — store sidecar owns init+daemon, sessions connect-only #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "taskstore-pod-architecture"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per the component spec: init logic and the dolt daemon move into a dedicated
store container (kmcp sidecar); MCP sessions and exec access are strictly
connect-only. Empirically verified in a podman pod mirroring the k8s pod
(shared netns + volume, separate containers).
dolt sql-server 127.0.0.1:3307 (foreground-supervised, container lives as
long as the daemon) -> first-boot bd init --server --server-host 127.0.0.1
--server-port 3307 --prefix caiman -> validate metadata -> SQL health gate
-> /tmp/taskstore-ready marker. Any failure = exit 1 = CrashLoop.
externally-managed: clients resolve 127.0.0.1:3307 from the PVC, refuse
when it is down (never spawn), and bd's pgrep/pid-file daemon tracking is
out of the client path entirely — which is what makes the cross-container
split safe
metadata guard + short SQL retry, then exec beads-mcp
store ready line (bd list answers DURING init — SQL alone races init)
ships bare binaries); the in-repo image remains
Co-Authored-By: Claude Fable 5 noreply@anthropic.com