@go-to-k/cdkd 0.219.9 → 0.220.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -578,6 +578,25 @@ spec: S3 key layout, optimistic-locking mechanism (ETag-based), state
578
578
  schema, legacy `version: 1` migration, bucket-name migration via
579
579
  `cdkd state migrate`, and troubleshooting.
580
580
 
581
+ ## Deployment events (`cdkd events`)
582
+
583
+ Every `cdkd deploy` / `cdkd destroy` run records a structured event
584
+ stream to S3 — cdkd's local equivalent of CloudFormation's
585
+ `DescribeStackEvents`. Read it back with `cdkd events <stack>`:
586
+
587
+ ```bash
588
+ cdkd events MyStack # list runs, newest first
589
+ cdkd events MyStack --run <runId> # one run's full event stream
590
+ cdkd events MyStack --format json # machine-readable (AI-agent hand-off)
591
+ ```
592
+
593
+ Events are persisted as JSONL under a `deployments/` key family separate
594
+ from `state.json` (no state schema bump), so a destroyed stack's failure
595
+ history stays readable. Recording is best-effort and never blocks the
596
+ run; events carry error + metadata only (never resource properties). See
597
+ **[docs/deployment-events.md](docs/deployment-events.md)** for the full
598
+ reference.
599
+
581
600
  ## Stack Outputs
582
601
 
583
602
  CDK's `CfnOutput` constructs are resolved and stored in the state file: