@go-to-k/cdkd 0.147.2 → 0.149.0

package/README.md

@@ -306,6 +306,8 @@ cdkd state info --state-bucket my-bucket  # explicit bucket; reports Source: --s
 cdkd state list
 cdkd state ls --long          # include resource count, last-modified, lock status
 cdkd state list --json        # JSON output (alone, or combined with --long)
+cdkd state list --tree        # parent → child stack tree (nested stacks; #555 A3)
+cdkd state list --tree --json # tree as nested JSON
 
 # List resources of a single stack from state
 cdkd state resources MyStack          # aligned columns: LogicalID, Type, PhysicalID
@@ -314,7 +316,9 @@ cdkd state resources MyStack --json   # full JSON array
 
 # Show full state record for a stack (metadata, outputs, all resources incl. properties)
 cdkd state show MyStack
-cdkd state show MyStack --json        # raw {state, lock} JSON
+cdkd state show MyStack --json              # raw {state, lock} JSON
+cdkd state show MyParent --show-nested      # recursively show every nested-stack child (#555 A4)
+cdkd state show MyParent --show-nested --json  # tree as nested {state, lock, children: [...]} JSON
 
 # Orphan one or more RESOURCES from cdkd's state (does NOT delete AWS resources).
 # Per-resource, mirrors aws-cdk-cli's `cdk orphan --unstable=orphan`.
@@ -585,11 +589,16 @@ the offending resources (or accept abandoning them) first. Nested
 [#464](https://github.com/go-to-k/cdkd/issues/464) PR B1: `cdkd export`
 recursively walks the cdkd state tree, validates every parent → child
 link, and surfaces the full leaf-first migration scope to the user;
-the CFn-side `--include-nested-stacks` IMPORT changeset submission
-itself is deferred to PR B2, so the command warns on `--dry-run` /
-hard-errors on real run with a clear pointer + workaround (keep on
-cdkd, or destroy children leaf-first via `cdkd state destroy <child>`
-and re-export the flattened parent). Fresh `cdkd deploy` of nested
+the CFn-side per-stack IMPORT loop submission itself is deferred to
+PR B2 (the original "one atomic `--include-nested-stacks` IMPORT
+changeset" design was found infeasible by the 2026-05-24 AWS spike —
+AWS rejects that flag combination with
+`ValidationError: IncludeNestedStacks is not supported for changeSet type: IMPORT`;
+see [docs/design/464-nested-stacks-export-import.md](docs/design/464-nested-stacks-export-import.md)
+§4.0), so the command warns on `--dry-run` / hard-errors on real run
+with a clear pointer + workaround (keep on cdkd, or destroy children
+leaf-first via `cdkd state destroy <child>` and re-export the
+flattened parent). Fresh `cdkd deploy` of nested
 stacks works via [#459](https://github.com/go-to-k/cdkd/issues/459).
 
 ```bash