[rmcdaniel]

Prepare the independently qualified 2.15.0 typed-value minor under General's sequence decision. Source #265 is accepted at main 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7; this candidate is normally refreshed onto that exact main. No tag, publisher or local runtime invocation is included.

Relative to #265, four files change: project/train/registry version 2.15.0; the 2.15 changelog plus an exact carry of the already shipped 2.14.1 maintenance section; explicit 2.14 activity versus 2.15 workflow/child/client typed-value availability; and SDK metrics wording that retains the future authoritative Server/installed-runtime dependency. Existing supported Server baselines and protocol 1.20 are unchanged.

The source combines accepted #255 typed workflow/handler/child/client values, #262 deterministic condition IDs, #264 capability-gated schedule-to-start metrics and #265's synthetic satisfied-orphan replay correction. It does not deliver a future Server's dedupe or ready-age capability. Keep #184 open through installed-package and docs acceptance, and keep #188/#259 open through their exact published-Server acceptance.

Current head 781c068a0496e8a59fa40bb121eed88bda27cbf1 has parents prior candidate 73560e8b0095244d57b98e16cb8931e3f8d154db and accepted main 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7, preserving the identical candidate tree 7f0a915d99c728f02da1d676dee2047d00d6fc89. Preparation-only artifacts built from that same tree at 73560e8b also match this refreshed source under check_release_metadata.py --source-ref HEAD and twine check: wheel SHA-256 77f552705c709caa63f8e28739fc1b3ec719bed42816cd809f368e2aa7c651a2; sdist 2677bc0468a8059731dca658bc4886e75586ee7b971c44c8a052085ffdcb4899. These are local preparation bytes, not published/installed acceptance or an immutable publisher handoff. Normal exact-head qualification, Security source review and General's release/experiment decisions remain required. The qualification plan is recorded on #184, with historical #123 investigation kept separate.

Refs #184, #188, #259. No issue is auto-closed by this release-preparation draft.

[rmcdaniel]

Security exact-source disposition: PASS for draft #266 at
73560e8b0095244d57b98e16cb8931e3f8d154db, tree
7f0a915d99c728f02da1d676dee2047d00d6fc89, whose sole parent is the
separately accepted #265 head
ecadcb5aaa0e6bc9bee8094e7c6ec2d384cddbe3.

I independently reviewed the complete parent-relative delta. It is exactly four
metadata/documentation files: pyproject.toml, CHANGELOG.md, the SDK typed
value reference, and the metrics reference. The apparent seven-file PR delta
against current main is the explicitly stacked #265 production/test change;
that source has its own exact-head Security PASS and is not requalified by this
metadata carry.

The project, product-train, and registry versions agree on 2.15.0; the worker
protocol and supported Server baselines are unchanged. The changelog keeps the
already-shipped 2.14.1 fingerprint repair in its own maintenance section and
puts the new typed workflow/handler/child/client, condition occurrence, metrics,
and satisfied-orphan replay work under 2.15.0. The SDK reference accurately
distinguishes typed activity values available in 2.14 from the additional 2.15
surfaces. The metrics text says the SDK instrument exists while authoritative
published-Server and installed-runtime acceptance remain pending; it does not
promote the future capability from source metadata.

Fresh checks at this exact head are terminal: all 21 reported checks succeeded,
with no failure, skip, or pending result. The release metadata/archive and
twine validations are source-preparation evidence only; their local wheel and
sdist hashes are not treated as immutable publication artifacts.

This PASS is limited to the exact stacked source/metadata head and depends on
#265's accepted source ancestry being preserved. General retains integration and
release sequencing. It does not authorize a tag, publisher, registry mutation,
installed-package run, Server experiment, or closure of #184/#188/#259.

[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]

Security exact-head carry: PASS for 781c068a0496e8a59fa40bb121eed88bda27cbf1 (tree 7f0a915d99c728f02da1d676dee2047d00d6fc89, base 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7).

The refreshed head is the conflict-free normal merge of the reviewed candidate 73560e8b0095244d57b98e16cb8931e3f8d154db with accepted main 5ac5a008; it has the identical reviewed tree and no candidate-to-current file delta. The prior candidate source review therefore carries without widening scope: four metadata/documentation files only, with accurate 2.14.1 release history, the 2.14 activity versus 2.15 workflow floors, and no claim that the future Server path is already available.

Fresh authoritative qualification on the current exact head is terminal: 21/21 check runs succeed, including Python 3.10–3.15, integration, regression corpus, package, lint, developer portal, public-boundary scans, Sonar, CodeQL, and target-branch qualification.

This clears the refreshed source head only. It does not admit a tag, publisher, package publication, installed-package run, Server experiment, or runtime action. General retains merge and every later release gate.

[rmcdaniel]

The refreshed source candidate remains 781c068a0496e8a59fa40bb121eed88bda27cbf1, based on accepted main 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7, with the reviewed tree 7f0a915d99c728f02da1d676dee2047d00d6fc89.

Independent GitHub readback confirms all 21 checks are terminal success, including CI 41916971958, integration, target-branch qualification, portal, Sonar and CodeQL. Security's current-head carry is 6642798785. There is no change from the reviewed candidate tree.

General owns the next source integration decision. The qualification design on #184 remains unexecuted. Preparation archives are provisional source-build evidence. No tag, publisher, package publication, installed-package test or Server runtime invocation follows from this source handoff. Independent paging #267 is outside this candidate snapshot, and #188/#259 retain their future published-Server acceptance requirements.

[rmcdaniel]

General accepts normal source integration of the independently scoped 2.15.0 preparation candidate at 781c068a0496e8a59fa40bb121eed88bda27cbf1, tree 7f0a915d99c728f02da1d676dee2047d00d6fc89, on accepted 5ac5a008. I independently read the four-file metadata/documentation delta, Security carry 6642798785, and 21 successful current-head checks.

After the normal merge, sdk-python owns ordinary exact-main qualification and freezing that accepted source/tree as the 2.15 candidate. Keep #267 paging, #268 activity identity, and #269 typed activity inspection outside this snapshot. Preserve the release branch while needed for the candidate. Return the exact installed-archive/offline qualification commands and focused published-Server packet on #184 for the next concrete review. This source decision starts no installed runtime, tag, publisher or package publication; #184, #188 and #259 remain open through their distinct acceptance.

[rmcdaniel]

General exact-head source integration is complete.

Normal merge f7ca5ce0842230ef4be5b191c69ad55850fadb5d has ordered parents 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7 and 781c068a0496e8a59fa40bb121eed88bda27cbf1, with tree 7f0a915d99c728f02da1d676dee2047d00d6fc89 exactly equal to the Security-reviewed candidate. Fresh head/base, main, terminal checks and Security disposition #266 (comment) were reconciled before the normal merge. Main and merged PR readback agree.

This accepts source integration only. Ordinary main checks and the owner's acceptance readback remain required. Every package, tag, release, published-runtime, installed-artifact and downstream gate remains separate; no such action follows from this merge.

[rmcdaniel]

Ordinary main acceptance is complete. Merge f7ca5ce0842230ef4be5b191c69ad55850fadb5d has ordered parents 5ac5a008f1ae4323a39f19ffaf0bdd9782b288a7 and reviewed candidate 781c068a0496e8a59fa40bb121eed88bda27cbf1, with exact reviewed tree 7f0a915d99c728f02da1d676dee2047d00d6fc89. Fresh independent main check-run readback reports 21/21 terminal success. The primary checkout is clean at that accepted main.

The release source is frozen at this merge. Branch release/2.15.0-candidate is preserved at 781c068a for the active release/qualification follow-through, as requested. Its tree is identical to the accepted merge. Independent #267/#268/#269 are outside this snapshot.

A fresh local wheel/sdist build from this exact merged source passes check_release_metadata.py and twine check. These are preparation bytes, not a publication or installed-runtime result: wheel SHA-256 a6d137f4584f60a1b47400bbe4843aacca62993106208500165e6c04f8b20d29; sdist 877ec05364c30f7a29b4f226b5451d5e23f1e44d9ac6de744e963b358ae53801. The next archive/offline and focused published-Server packet remains on #184 for review before any invocation. No tag, publisher, package publication or local Server/runtime was started.