Remove private tracker references from public sdk-python

Test docstrings and the CHANGELOG rationale line referenced the private
tracker; rewrite them as direct prose and point pyproject Issues URL at
the public durable-workflow/sdk-python issues surface so pip/PyPI users
land in the right place.

Author: durable-workflow-ops

CHANGELOG.md

@@ -16,8 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   via `except Exception:` or `except DurableWorkflowError:` must now either
   catch the class by name (e.g. `except (ActivityCancelled, WorkflowCancelled):`)
   or catch `BaseException`. Mirrors the standard-library precedent set by
-  `asyncio.CancelledError` and `KeyboardInterrupt`. Rationale and upstream
-  lesson: [zorporation/durable-workflow#441](https://github.com/zorporation/durable-workflow/issues/441).
+  `asyncio.CancelledError` and `KeyboardInterrupt`.
 
 ## [0.3.0] — 2026-04-19
 

pyproject.toml

@@ -54,7 +54,7 @@ docs = [
 Homepage = "https://github.com/durable-workflow/sdk-python"
 Documentation = "https://durable-workflow.github.io/docs/2.0/polyglot/python"
 Repository = "https://github.com/durable-workflow/sdk-python"
-Issues = "https://github.com/zorporation/durable-workflow/issues"
+Issues = "https://github.com/durable-workflow/sdk-python/issues"
 
 [tool.setuptools.packages.find]
 where = ["src"]

tests/test_activity_context.py

@@ -203,11 +203,11 @@ async def heartbeat_activity() -> str:
     async def test_cancellation_survives_user_generic_except(self, mock_client: AsyncMock) -> None:
         """A user activity with ``except Exception:`` must not swallow cancellation.
 
-        Regression guard for zorporation/durable-workflow#441: when the server
-        signals cancellation via the heartbeat response, the activity function
-        may have a broad ``except Exception:`` block (for logging, retry, etc.).
-        That block must *not* catch ``ActivityCancelled``, so the worker still
-        reports the activity as cancelled rather than completing normally.
+        Regression guard: when the server signals cancellation via the heartbeat
+        response, the activity function may have a broad ``except Exception:``
+        block (for logging, retry, etc.). That block must *not* catch
+        ``ActivityCancelled``, so the worker still reports the activity as
+        cancelled rather than completing normally.
         """
         mock_client.heartbeat_activity_task = AsyncMock(return_value={"cancel_requested": True})
 

tests/test_errors.py

@@ -89,7 +89,7 @@ class TestCancellationContract:
     Guards the pre-1.0 design decision that ``WorkflowCancelled`` and
     ``ActivityCancelled`` inherit from :class:`BaseException` directly, so that
     user worker/activity code cannot accidentally swallow a cancellation signal
-    in a catch-all. See zorporation/durable-workflow#441.
+    in a catch-all.
     """
 
     def test_workflow_cancelled_not_caught_by_exception(self) -> None: