The following improvements have been made to `meepctl` to simplify operations:
| Feature | Commit | Description |
|---------|--------|-------------|
| **Individual core deploy/delete** | `8873a29` | `meepctl deploy core <app>` and `meepctl delete core <app>` — deploy or delete a single core app instead of the entire group |
| **Individual dep deploy/delete** | _(latest)_ | `meepctl deploy dep <app>` and `meepctl delete dep <app>` — deploy or delete a single dependency app |
| **Force-deploy cooldown** | _(latest)_ | 5-second wait between delete and re-deploy when using `--force`, allowing K8s to clean up resources |
| **`--no-cache` dockerize flag** | `8598278` | `meepctl dockerize <app> --no-cache` — build Docker images from scratch without using cached layers |
| **Dockerize filename fix** | `a5fcff8` | Safely handles filenames with spaces in dockerize checksum calculation |
| **Permissive workdir creation** | `4d49a73` | Uses 0777 permissions for `~/.meep` directories so K8s fsGroup can manage ownership properly |
| **Individual core deploy/delete** | `meepctl deploy core <app>` and `meepctl delete core <app>` — deploy or delete a single core app instead of the entire group |
| **Individual dep deploy/delete** | `meepctl deploy dep <app>` and `meepctl delete dep <app>` — deploy or delete a single dependency app |
| **Force-deploy cooldown** | 5-second wait between delete and re-deploy when using `--force`, allowing Kubernetes to clean up resources |
| **`--no-cache` dockerize flag** | `meepctl dockerize <app> --no-cache` — build Docker images from scratch without using cached layers |
| **Dockerize filename fix** | Safely handles filenames with spaces in dockerize checksum calculation |
| **Permissive workdir creation** | Uses `0777` permissions for `~/.meep` directories so Kubernetes `fsGroup` can manage ownership properly |
