docs: add v0.1.3 release notes

docs/release-notes/v0.1.3.md

@@ -0,0 +1,41 @@
+# tdc v0.1.3
+
+This release makes asynchronous TiDB Cloud lifecycle operations deterministic for agents and scripts through one consistent `--wait` flag. Commands still return as soon as the service accepts a request by default; add `--wait` when the next step depends on the resource being ready or gone.
+
+```bash
+export CLUSTER_ID="$(tdc db create-db-cluster \
+  --db-cluster-name agent-db \
+  --db-cluster-type starter \
+  --wait \
+  --query id \
+  --output text)"
+
+tdc db create-db-cluster-branch \
+  --db-cluster-id "$CLUSTER_ID" \
+  --db-cluster-branch-name development \
+  --wait
+
+tdc db delete-db-cluster \
+  --db-cluster-id "$CLUSTER_ID" \
+  --wait
+```
+
+The same contract applies when provisioning a TiDB Cloud Filesystem. A trusted machine can wait for the Drive9-backed data plane and capture the owner token in one command before injecting it into an agent sandbox:
+
+```bash
+export TDC_FS_TOKEN="$(tdc fs create-file-system \
+  --file-system-name agent-workspace \
+  --wait \
+  --query fs_token \
+  --output text)"
+```
+
+Cluster creation waits for `ACTIVE`, branch creation waits for `ACTIVE`, cluster deletion waits for `DELETED` or confirmed inaccessibility, and Filesystem creation waits until the data-plane root is readable. Timeouts and interruptions never delete or recreate an accepted resource. Filesystem deletion remains asynchronous because the backend does not expose reliable completion status; accepted deletion now correctly reports `deleting` instead of `deleted`.
+
+Upgrade an existing installation with:
+
+```bash
+tdc update --check
+tdc update
+tdc --version
+```