Run linter

Signed-off-by: Sergio Herrera <627709+seherv@users.noreply.github.com>

Author: seherv

RELEASE.md

@@ -10,11 +10,25 @@ A single tag (`v*`) triggers the release of the core SDK only:
 
 **The previously-separate distributions** — `dapr-ext-fastapi`, `dapr-ext-grpc`,
 `dapr-ext-langgraph`, `dapr-ext-strands`, `dapr-ext-workflow`, `flask-dapr` —
-are **no longer published**. Republishing them as `dapr-ext-name` shims that 
-depend on `dapr[name]` was considered but rejected: any shim that doesn't carry 
-the actual extension code creates a `RECORD` ownership conflict with the legacy 
-versions in existing user environments, and `pip uninstall` of a legacy package would
-delete files that core `dapr` now provides.
+are **no longer published**.
+
+The design constraint was keeping `from dapr.ext.X import ...` stable across
+the upgrade, so the cost lands once in pip during migration rather than
+forever in every existing codebase that already imports those paths.
+
+The price: legacy dists on disk now claim the same files core `dapr` ships,
+and pip has no cross-dist ownership awareness. `pip uninstall <legacy>` walks
+the legacy RECORD and deletes `dapr/ext/<name>/*.py` from disk, leaving a
+silently broken install: `pip show dapr` reports 1.19 installed, but
+`from dapr.ext.<name> import ...` raises `ModuleNotFoundError`. The recipe
+below uses `--force-reinstall --no-deps dapr` to rewrite those files after
+the legacy uninstall removes them.
+
+Republishing the legacy distributions as `dapr-ext-name` shims depending on
+`dapr[name]` was considered and rejected: any shim that doesn't ship the
+actual files leaves the legacy version's RECORD on disk in existing
+environments, so the same uninstall failure mode remains. They would also
+add a per-extension release artifact to maintain in perpetuity.
 
 Existing installs must migrate explicitly:
 

dapr/__init__.py

@@ -17,10 +17,10 @@
 # the environment in.
 #
 # 1. Legacy `dapr-ext-*` or `flask-dapr` dist still installed alongside
-#    core dapr. 
+#    core dapr.
 #    Pre-1.19 each extension was its own dist owning files under
-#    `dapr/ext/<name>/`, the new core wheel ships those same files. 
-#    pip has no cross-dist ownership awareness, so `pip uninstall <legacy>` 
+#    `dapr/ext/<name>/`, the new core wheel ships those same files.
+#    pip has no cross-dist ownership awareness, so `pip uninstall <legacy>`
 #    walks the legacy RECORD and deletes `dapr/ext/<name>/*.py` from disk. End
 #    state: `pip show dapr` reports OK, but `from dapr.ext.<name> import ...`
 #    raises ModuleNotFoundError.