@go-to-k/cdkd 0.36.0 → 0.38.0

package/README.md

@@ -208,8 +208,15 @@ alias cdkd="node $(pwd)/dist/cli.js"
 
 ## Quick Start
 
+> **First-time setup**: cdkd requires a one-time `cdkd bootstrap` per AWS
+> account before any other command will work — it creates the S3 state
+> bucket (`cdkd-state-{accountId}`) that cdkd uses to track deployed
+> resources. This is separate from `cdk bootstrap` (which sets up the
+> CDK asset bucket / ECR repo and is also required — see
+> [Prerequisites](#prerequisites)).
+
 ```bash
-# Bootstrap (creates S3 state bucket - only needed once per account/region)
+# Bootstrap (creates S3 state bucket — one-time setup, once per AWS account)
 cdkd bootstrap
 
 # List stacks in the CDK app
@@ -283,10 +290,16 @@ cdkd deploy MyStack \
 cdkd diff MyStack
 
 # Detect drift between cdkd state and AWS reality (state-only; no synth)
-# Exits 0 with no drift, 1 when drift is detected, 2 on error.
+# Exits 0 with no drift, 1 when drift is detected, 2 on partial revert failure.
 cdkd drift MyStack
 cdkd drift --all --json
 
+# Resolve drift: state ← AWS (catch up state with manual console changes)
+cdkd drift MyStack --accept --yes
+
+# Resolve drift: AWS ← state (push state values back into AWS via provider.update)
+cdkd drift MyStack --revert --yes
+
 # Dry run (plan only, no changes)
 cdkd deploy --dry-run