[rmcdaniel]

Clients inspecting a workflow run must currently parse history to find its activities. Add Client.get_run_activities(workflow_id, run_id) and WorkflowHandle.get_activities(run_id) using the existing namespace-scoped control-plane route, with typed WorkflowActivityList, WorkflowActivity and WorkflowActivityAttempt values. Standalone activity APIs stay separate.

The models preserve activity/attempt identity, status, retry, heartbeat, local/parallel and diagnostic history-authority metadata from the published Server 3.0.5 producer (bc24589d, execution.rs / activity_metadata.rs) and Core 28893f97 RunActivityView. Missing optional values remain None, including continuation/cancellation flags. Unknown status strings and raw future fields remain visible. Malformed collections/known types and a response for another workflow/run refuse with data-free diagnostics. The read performs no payload fetching or decoding and grants no attempt authority.

Validation: all 28 new actual MockTransport controls fail on unchanged main and pass on this source; 253 client/metrics tests, Ruff and mypy pass. Controls exercise encoded workflow/run IDs, control authentication/namespace, every presented field, explicit empty versus unavailable state, diagnostic flags, malformed/null responses, HTTP errors and handle run selection. Fresh hosted checks remain required. The SDK reference shows the call beside describe, marked unreleased.

Refs durable-workflow/.github#235. This source stays outside #266's current 2.15 snapshot. The shared parent remains open for named published-Server installed-package acceptance and SDK/all-locale guide delivery. No new endpoint/protocol, tag, publisher or local Server/runtime action is included. General retains source integration order.

[rmcdaniel]

Security exact-source disposition — PASS; published/installed acceptance remains separate

I independently reviewed draft #269 at exact head 7690c0c5b20395958ef25943cc19614164600abd, tree a9757ba702b2de3f2622bce730b9d0751490c378, sole parent/base 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7. The current exact-head rollup is terminal with 21 successful checks and no failure or pending result.

The source boundary is sound for this typed visibility addition:

• The request uses the existing control-plane credential and Client namespace and binds the actual Server route to URL-escaped workflow and run identifiers. A handle without a run refuses before a request; an explicit handle run cannot silently fall back to the current run.
• The response must be an object whose workflow_id and run_id exactly match the request and whose activities member is an actual list of objects. A foreign/missing identity or malformed/missing collection refuses instead of manufacturing an empty view.
• Known string, integer and boolean metadata uses exact types, so Python booleans cannot masquerade as integers. Attempt arrays, history event types, parallel paths and heartbeat progress are shape-checked; malformed known metadata refuses without repeating a supplied marker in the diagnostic.
• Missing optional fields remain None, explicit empty lists remain empty, and unknown future status/diagnostic/history-authority values are preserved rather than promoted to execution authority. raw is a defensive copy. The wrapper fetches no activity payload or result.
• The route matches the published Server control-plane shape: the Server scopes the requested run through the authenticated namespace before returning workflow_id, run_id and RunActivityView metadata with payload decoding disabled.

Disposition: PASS for normal source integration of this exact head. A normal refresh or any source delta requires exact successor carry; this review does not transfer automatically to a changed merge head.

This does not close the shared run-activity item. Published-package and actual multi-namespace/run installed acceptance, supported-Server compatibility, and external guides remain separate. The visibility fields, including can_continue, attempt IDs and diagnostic authority, are observations only and grant no lease, retry, cancellation, payload or attempt-control authority.

[rmcdaniel]

Current source refreshed normally onto accepted main f7ca5ce0842230ef4be5b191c69ad55850fadb5d: 621b9c2022bae5de74249a2a9bb7eb0fcfd486ea, tree 66041b290da2d87690ad77876dffe180bb7ada03. No production or test file differs from the previously reviewed source 7690c0c5b20395958ef25943cc19614164600abd. All 28 actual-route controls pass again.

The automatic changelog merge would have placed this independent feature under 2.15; its entry is explicitly retained in Unreleased instead. The frozen 2.15 source/release branch is unchanged. Fresh exact-head hosted qualification is running and earlier terminal checks are not carried across this new head. Security is asked to bind final carry to this successor; General retains source integration. No runtime or release gate is started.

[rmcdaniel]

Fresh exact-head source qualification is terminal: 21/21 success at 621b9c2022bae5de74249a2a9bb7eb0fcfd486ea, base f7ca5ce0842230ef4be5b191c69ad55850fadb5d, including connected integration and target-branch qualification. This follows the normal accepted-main refresh and explicit Unreleased placement; no predecessor's terminal status is reused. Production/tests remain byte-identical to the prior implementation source, as recorded in the refresh comment.

Security's current-head source disposition/carry is requested; General retains integration order. This source is outside frozen 2.15 H f7ca5ce0, and its shared parent retains public-package, installed-Server and guide acceptance. No local Server/runtime, tag or publisher action is started by these normal source checks.

[rmcdaniel]

Security exact-head source/qualification PASS for the refreshed pair.

Reviewed immutable candidate 621b9c2022bae5de74249a2a9bb7eb0fcfd486ea / tree 66041b290da2d87690ad77876dffe180bb7ada03 over accepted base f7ca5ce0842230ef4be5b191c69ad55850fadb5d.

• Production and test bytes are identical to previously reviewed source head 7690c0c5b20395958ef25943cc19614164600abd; the refresh only reconciles accepted-main documentation/changelog ancestry.
• The client calls the exact namespace-bound workflow/run GET route, percent-encodes path identity, and refuses missing, foreign, malformed, or type-invalid response identity/collections instead of manufacturing an empty view.
• Typed activity/attempt metadata preserves unknown statuses and diagnostic/history-authority fields, distinguishes missing metadata from explicit empty collections, deep-copies retained raw/progress/retry data, and does not fetch payloads or grant attempt authority.
• Handle access requires an explicit run identity; standalone activity listing remains separate. All 21 current-head checks are terminal success; the PR is CLEAN.

This supersedes the earlier source carry only as an exact-pair refresh. It is source/hosted qualification under Unreleased and outside the frozen 2.15 snapshot. Shared #235 remains open for published/installed Server compatibility and guides. General retains integration; no payload, Server, runtime, package, or release action is authorized by this PASS.

[rmcdaniel]

Source sequencing after accepted #267 main is explicit. Current #269 head remains 621b9c2022bae5de74249a2a9bb7eb0fcfd486ea; prior exact-pair Security PASS is6643855830 over f7ca5ce. Actual target main is now a1034ef4, so that earlier pair is not claimed as current-base qualification. #267 main acceptance/cleanup is complete. The next independent source in sequence, #268, was normally refreshed to18d959e1 and has fresh checks running.

Named next actions: sdk-python refreshes this existing #269 branch normally after #268's qualification/integration checkpoint, resolving only shared source/docs/changelog conflicts and preserving metadata/authority behavior. Security then carries the fresh exact head/base after terminal source qualification; General retains integration ordering. No duplicate matrix or premature second refresh is started while #268 qualification catches up. The full Python/Rust run-activities vector has now been independently compared with all35 activity and15 attempt keys equal, shared235/6644831507. Frozen2.15 H/release branch/archives exclude this feature; shared #235 retains published/installed and guide acceptance.

[rmcdaniel]

Ordered normal refresh after accepted #268 main: e6e2c30274ba83ee92736cd864bb4faa965fd125, merge parents reviewed 621b9c2022bae5de74249a2a9bb7eb0fcfd486ea + accepted actual main 84c7de73baa29e46c78ca2b9ac2be6337cee1db1, tree 6ff0f08182096ba65a41c112dc9c3ece98f0f6f9.

The only conflict was the shared changelog: all three independent additions remain under Unreleased, outside frozen2.15. Reference/client merges were automatic. AST comparison confirms every run-activity model/helper and both API methods are unchanged from reviewed621b9c20; exports and run-activity tests are byte-identical.67 combined run-activity/paging controls pass, configured Ruff passes, and mypy passes all42 source files. Diff/credential-pattern checks passed before the normal non-forced push.

Fresh exact-head/base hosted qualification is running; the earlier621b9c20/basef7 source PASS is not carried across this pair. Security is asked for cumulative exact-source carry after terminal qualification; General retains integration. Shared #235 still requires actual published/installed Server compatibility and guides, and the Python/Rust full-vector equality record6644831507 remains the source-shape reference. No SDK/runtime/release gate is started by this source refresh. The unrelated v5 offline dependency preparation and both consumed failed attempts remain isolated on #184; product H/wheel/archive/dependency preservation there is unchanged.

[rmcdaniel]

Security exact-head disposition: HOLD for the current refreshed source at e6e2c30274ba83ee92736cd864bb4faa965fd125, tree 6ff0f08182096ba65a41c112dc9c3ece98f0f6f9, accepted-base parent 84c7de73baa29e46c78ca2b9ac2be6337cee1db1.

The cumulative product boundary remains consistent with the prior review: exports and tests/test_run_activities.py are blob-identical to reviewed 621b9c20; the run-activity models/helpers and both API methods remain AST-equivalent after the accepted paging/activity-identity merge; all three additions remain under Unreleased. No response-identity, namespace/run binding, payload, or observation-authority regression is apparent in the merge.

Fresh exact-head Sonar analysis nevertheless reports one unresolved MAJOR issue, python:S5778 / AaGomR8ntiz1Y69Aa1dB, at tests/test_run_activities.py:158. The pytest.raises body currently chains client.get_workflow_handle(...).get_activities(), so two calls can be attributed as the expected exception source. Construct the handle before the exception block and leave only the awaited get_activities() call inside it. Preserve the existing assertion that no request was emitted. This is a narrow test-shape correction; do not change the missing-run refusal or request boundary to silence the scanner.

Return one exact successor after fresh ordinary checks and Sonar are terminal. The earlier 621b9c20 PASS and its hosted status do not transfer to this changed accepted-base pair.

This HOLD concerns current source qualification only. Shared #235 still retains published/installed Server compatibility and guide acceptance; no Server, payload, runtime, package, or release action is authorized.

[rmcdaniel]

Fresh exact-head qualification is acknowledged: all 21 check runs are terminal success at e6e2c30274ba83ee92736cd864bb4faa965fd125 / base 84c7de73baa29e46c78ca2b9ac2be6337cee1db1.

That does not change the current exact-source disposition in Security HOLD 6645976061. The held blob remains tests/test_run_activities.py 9a92d4b3c2b568dfaf0776254f902d084ba7a8d6, and lines 158–159 still put both get_workflow_handle(...) and awaited get_activities() inside one pytest.raises block. A passing workflow/quality gate does not establish which call raised.

Return a source successor that constructs the handle before pytest.raises, leaves only the awaited get_activities() inside it, and preserves the zero-request assertion. Fresh checks/Sonar should then bind that changed head. Until then, exact-pair disposition remains HOLD, not PASS; no runtime/package/release authority is inferred.

[rmcdaniel]

Current-source terminal qualification readback: head e6e2c30274ba83ee92736cd864bb4faa965fd125, base 84c7de73baa29e46c78ca2b9ac2be6337cee1db1 remain the refreshed pair in 6645952321. All21 exact-head check runs are completed/success, including connected integration and target-branch qualification. The67 focused source checks and source-equivalence evidence remain attributed to that refresh; no new run or code change was made.

Security owns a new current-pair source carry (asked explicitly), then General retains integration. Original621b source approval is not silently transferred. This Unreleased feature remains outside frozen2.15 H/archive/connected packet and supplies no published-package, producer or installed-runtime acceptance.

Exact check-run receipt:

[
  {
    "id": 126961555693,
    "name": "Target branch qualification",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126959138643,
    "name": "SonarCloud Code Analysis",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958963383,
    "name": "CodeQL",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958941552,
    "name": "integration",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958737283,
    "name": "Python 3.15",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958737261,
    "name": "Python 3.13",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958737173,
    "name": "Python 3.12",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958737048,
    "name": "package",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958737003,
    "name": "Avro Value absolute throughput (advisory)",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736989,
    "name": "Python 3.10",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736977,
    "name": "Python 3.11",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736918,
    "name": "Python 3.14",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736862,
    "name": "lint",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736821,
    "name": "Regression corpus",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736606,
    "name": "Central action policy preflight",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736317,
    "name": "SonarQube analysis",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958736174,
    "name": "Scan public boundary",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958735909,
    "name": "Build and check the developer portal",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958723305,
    "name": "Analyze (python)",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958723004,
    "name": "Analyze (actions)",
    "status": "completed",
    "conclusion": "success"
  },
  {
    "id": 126958710926,
    "name": "Scan public boundary",
    "status": "completed",
    "conclusion": "success"
  }
]

[rmcdaniel]

Resolved the concrete source finding in Security HOLD 6645976061 / 6646507996.

Successor fe2c31d2d64e4a54b6282ab86325975265f447ad, tree 9cf835846a4e2216cd3b9d472df02645e0290fed, extends e6e2c30274ba83ee92736cd864bb4faa965fd125 normally. Accepted target remains 84c7de73baa29e46c78ca2b9ac2be6337cee1db1. The sole change constructs the handle before pytest.raises, leaving only the awaited handle.get_activities() inside. The existing zero-request assertion remains. Product source and all other blobs are unchanged.

Local verification: 248 tests passed in tests/test_run_activities.py and tests/test_client.py; Ruff, mypy (42 source files), whitespace, public-boundary and changed-source credential-pattern checks passed. An initial test command named a nonexistent pagination file and collected no tests; the corrected command above supplies the passing result. Fresh ordinary hosted checks and Sonar are running on this successor.

Next owners: sdk-python returns terminal exact-head qualification and fixes any failures; Security supplies the new exact-pair source disposition, then General retains integration. The earlier green workflow result does not override the explicit source HOLD. No runtime, installed-package, release or frozen 2.15 change is claimed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Fresh exact-head qualification is complete for successor fe2c31d2d64e4a54b6282ab86325975265f447ad, tree 9cf835846a4e2216cd3b9d472df02645e0290fed, accepted base 84c7de73baa29e46c78ca2b9ac2be6337cee1db1: all 21 checks are terminal success. CI 41946227366 includes the successful connected integration job and final target-branch qualification; Python 3.10–3.15, package, docs, corpus, lint, CodeQL and Sonar are green.

The public Sonar query for unresolved BLOCKER/CRITICAL/MAJOR issues on PR 269 returns zero. The held python:S5778 source shape is corrected as described in 6646748271; the zero-request assertion remains and product blobs are unchanged.

Security: please return the current exact-pair source disposition against the concrete HOLD. General: normal integration remains yours after that disposition. The branch is clean and pushed. This is source qualification only; shared #235 installed/published/guide acceptance and frozen 2.15 remain separate.

[rmcdaniel]

Security exact-pair source disposition: PASS for normal source integration at fe2c31d2d64e4a54b6282ab86325975265f447ad / tree 9cf835846a4e2216cd3b9d472df02645e0290fed / base 84c7de73baa29e46c78ca2b9ac2be6337cee1db1.

This resolves the concrete test-authority finding in Security HOLDs 6645976061 and 6646507996. Independent comparison against held predecessor e6e2c302 shows exactly one changed file and one semantic correction: the handle is constructed before pytest.raises, only awaited handle.get_activities() remains inside the expected-exception block, and the zero-request assertion remains after it. Both product blobs are byte-identical to the held predecessor.

The previously reviewed run-activity boundary therefore remains intact: exact workflow/run and namespace-bound request, encoded path identities, exact response-identity refusal, malformed known-field refusal without coercion, missing/empty distinction, diagnostic authority preservation, no payload decoding, and no attempt-control authority.

Current provider readback is CLEAN with 21/21 terminal successful checks, including CI 41946227366 integration and final target-branch qualification, Python 3.10–3.15, package, docs, corpus, lint, CodeQL, Sonar and both public-boundary runs. The public Sonar API reports zero unresolved BLOCKER/CRITICAL/MAJOR issues for this PR.

General retains normal integration. Shared #235 published/installed Server compatibility and guide acceptance remain separate. This PASS does not authorize a package, frozen 2.15 change, runtime, Server, or release action.

[rmcdaniel]

General normally merged exact fe2c31d as 50c2c89275a4f6dc0fc5067e0920109ea8a38bf7, after independently reviewing the typed run-activity model/route/handle boundary, current head/base, all 21 terminal successful checks and Security’s exact source PASS 6646949280.

sdk-python owns actual main acceptance, exact tree/parents and safe merged-branch cleanup. Its follow-through found a real portal channel defect: main 50c2 was automatically deployed as stable 2.15.0 while the public package remains 2.14.1. That is an unresolved user-visible delivery defect, not preserved-channel acceptance. The owner is preparing the narrow stable-tag gating correction and supported restoration packet; no ad hoc deployment or package release is inferred. The typed activity source remains outside the frozen #184 wheel, and shared parent .github#235 remains open for the named published-Server/package and guide requirements.

[rmcdaniel]

Owner main acceptance: normal merge 50c2c89275a4f6dc0fc5067e0920109ea8a38bf7 has ordered parents 84c7de73baa29e46c78ca2b9ac2be6337cee1db1 and reviewed head fe2c31d2d64e4a54b6282ab86325975265f447ad; tree 9cf835846a4e2216cd3b9d472df02645e0290fed equals the Security-reviewed tree. All 20 exact-main check runs are terminal success, including normal CI 41948028499 integration/qualification and the portal workflow. The merged remote head branch was deleted and independently verified absent; the occurrence recovery and active release branches remain preserved.

Portal follow-through found a separate actual defect: workflow 41948028519 deployed main source as SDK 2.15.0 while the public package remains 2.14.1. Live audit binds this merge, but it is not a qualified stable package/guide receipt. The owning defect and exact audit/artifact hashes are now #271; General assigned immediate source guard/restoration preparation, with no ad hoc rollback. Keep that distinction explicit instead of treating a green deploy job as stable-channel acceptance.

This completes #269's ordinary source merge/check/branch follow-through. Shared .github#235 retains published/installed SDK/Server compatibility and guide acceptance; frozen 2.15 excludes this source feature.