type: create

description:
Currently laconic-so maps one stack to one deployment to one pod. All containers
in a stack's compose files become containers in a single k8s pod. This means:

- Can't upgrade doublezero without restarting agave-validator
- Can't restart monitoring without disrupting the validator
- Can't independently scale or lifecycle-manage components

The fix is stack composition. A meta-stack (e.g. biscayne-stack) composes
sub-stacks (agave, doublezero, agave-monitoring), each becoming its own
k8s Deployment with independent lifecycle.

title: Stack composition: deploy multiple stacks into one kind cluster

type: epic


description: Add laconic-so deployment prepare that creates cluster infrastructure without pods. Already implemented, needs review.

title: deployment prepare command

type: task


description: deployment stop on ANY deployment deletes the shared kind cluster. Should only delete its own namespace.

title: deployment stop should not destroy shared cluster

type: bug


description: Allow stack.yml to reference sub-stacks. Each sub-stack becomes its own k8s Deployment sharing namespace and PVs.

title: Add stacks: field to stack.yml for composition


description: Create three independent stacks from the monolithic agave-stack. Each gets its own compose file and independent lifecycle.

title: Split agave-stack into agave + doublezero + monitoring