@go-to-k/cdkd 0.35.0 → 0.37.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
@@ -376,6 +383,30 @@ cdkd state destroy MyStack --region us-east-1
 > `cdkd destroy` (synth-driven, deletes AWS resources + state) and
 > `cdkd state destroy` (state-driven, same effect) round out the matrix.
 
+## `publish-assets`: synth + build + publish, no deploy
+
+`cdkd publish-assets` runs the asset half of the deploy pipeline only —
+synthesize the CDK app, build any Docker images, upload file assets to
+S3, push images to ECR — and stops. No state writes, no provisioning,
+no lock acquisition. This is the typical CI split where one runner
+builds and uploads assets and a separate runner deploys.
+
+```bash
+cdkd publish-assets                          # synth + publish all stacks (or auto-detect single stack)
+cdkd publish-assets MyStack                  # synth + publish a specific stack
+cdkd publish-assets --all                    # synth + publish every stack in the app
+cdkd publish-assets 'MyStage/*'              # wildcard (CDK display path)
+cdkd publish-assets -a cdk.out               # skip synth — use a pre-synthesized cloud assembly
+```
+
+Stack selection follows the same rules as `deploy` / `diff` / `destroy`
+(positional > `--stack` > `--all` > auto-detect). Concurrency knobs
+are `--asset-publish-concurrency` and `--image-build-concurrency`.
+`-a/--app` accepts either a shell command (`"npx ts-node app.ts"`) or
+a path to an already-synthesized cloud assembly directory; pointing at
+`cdk.out` skips synthesis. See [docs/cli-reference.md](docs/cli-reference.md#publish-assets-synth--build--publish-no-deploy)
+for details.
+
 ## `--no-wait`: skip async-resource waits
 
 CloudFront Distributions, RDS Clusters/Instances, ElastiCache, and