@go-to-k/cdkd 0.10.0 → 0.12.0

package/README.md

@@ -95,7 +95,7 @@ Reproduce with `./tests/benchmark/run-benchmark.sh all`. See [tests/benchmark/RE
 ```
 1. CLI Layer
    ├── Resolve --app (CLI > CDKD_APP env > cdk.json "app")
-   ├── Resolve --state-bucket (CLI > env > cdk.json > auto: cdkd-state-{accountId}-{region})
+   ├── Resolve --state-bucket (CLI > env > cdk.json > auto: cdkd-state-{accountId}, with legacy fallback to cdkd-state-{accountId}-{region})
    └── Initialize AWS clients
 
 2. Synthesis (self-implemented, no CDK CLI dependency)
@@ -355,7 +355,7 @@ cdkd diff
 cdkd destroy
 ```
 
-That's it. cdkd reads `--app` from `cdk.json` and auto-resolves the state bucket from your AWS account ID (`cdkd-state-{accountId}-{region}`).
+That's it. cdkd reads `--app` from `cdk.json` and auto-resolves the state bucket from your AWS account ID (`cdkd-state-{accountId}`). If you bootstrapped under a previous cdkd version, the legacy region-suffixed name (`cdkd-state-{accountId}-{region}`) is still picked up automatically with a deprecation warning.
 
 ## Usage
 
@@ -407,7 +407,6 @@ cdkd deploy -c env=staging -c featureFlag=true
 cdkd deploy MyStack \
   --app "npx ts-node app.ts" \
   --state-bucket my-cdkd-state \
-  --region us-east-1 \
   --verbose
 
 # Show diff (what would change)
@@ -447,8 +446,20 @@ cdkd state show MyStack --json        # raw {state, lock} JSON
 cdkd state rm MyStack                 # confirmation prompt (y/N)
 cdkd state rm MyStack --yes           # skip confirmation
 cdkd state rm StackA StackB --force   # also bypass the locked-stack refusal
+
+# Destroy a stack's AWS resources AND remove its state record, without
+# requiring the CDK app (no synth — works from any working directory).
+cdkd state destroy MyStack            # per-stack confirmation prompt
+cdkd state destroy MyStack OtherStack --yes
+cdkd state destroy --all -y           # every stack in the bucket
+cdkd state destroy MyStack --region us-east-1
 ```
 
+> `cdkd state destroy` vs `cdkd state rm`: `state destroy` deletes both the
+> AWS resources and the state record (the equivalent of `cdkd destroy` minus
+> the CDK-app dependency). `state rm` only forgets the state record and
+> leaves the AWS resources intact.
+
 ### Concurrency Options
 
 | Option | Default | Description |
@@ -547,7 +558,7 @@ s3://{state-bucket}/
 
 | Setting | CLI | cdk.json | Env var | Default |
 |---------|-----|----------|---------|---------|
-| Bucket | `--state-bucket` | `context.cdkd.stateBucket` | `CDKD_STATE_BUCKET` | `cdkd-state-{accountId}-{region}` |
+| Bucket | `--state-bucket` | `context.cdkd.stateBucket` | `CDKD_STATE_BUCKET` | `cdkd-state-{accountId}` (legacy `cdkd-state-{accountId}-{region}` is still read with a deprecation warning) |
 | Prefix | `--state-prefix` | - | - | `cdkd` |
 
 ### Multi-app isolation