[rmcdaniel]

Integrate the published and independently exercised 4.11.2 release source into main. Immutable package/tag source remains feb49025e28516f00377e3fe335e9276895f313b. Integration head is now 2de5f8f6a836ab343fd8e16669196fed007a2eb8, a normal merge of exact main a0a2bb2819872336f69d7e10b05abbfc88e105e7 into the release branch to satisfy the up-to-date rule. H is its first parent; no published ref or byte changes.

Ships condition-wait deadline preservation (#187/#189), correctly rounded Server JSON floats (#181), valid redrive replay evidence (#173/#175), and managed-worker settlement of exact non-recorded run_closed receipts (#176/#170).

The protected Release run succeeded on control main a0a2bb2819872336f69d7e10b05abbfc88e105e7. Crates.io and the public archive match the pre-publication approved SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. The annotated tag and stable GitHub Release resolve to H. Main already contains the separately reviewed approval record and exact pre-publication summary from #197.

Both pre-publication and fresh registry-installed lifecycle/deadline cells passed against exact published native Server 3.0.5 on arm64, with independent histories, same-worker survival, checksum/source identity and complete runtime cleanup. Detailed immutable identities and timestamps are in the acceptance comments. The final registry-installed summary SHA-256 is 4fb351932cef34d3a44f914e179d64a8630521c0b41c4850308631766b431a26.

Security and General accepted the published-runtime evidence on the PR. Their normal merge was blocked by the up-to-date rule, so the integration branch was refreshed without rewriting history. Relative to H, the refresh adds only the two already-reviewed approval records. The actual head tree is exactly the independently reviewed prospective tree 2b04132254d1c372f57e433f265b0483262c45db.

Draft pending Security carry review and General's merge decision for the new integration head. All 17 hosted checks pass, with two expected qualification skips. No downstream manifest has changed. Against exact current main a0a2bb2, integration still changes only crate version/product-train, the crate lockfile version and the release changelog heading/Server reference. No repeated installed acceptance, release workflow run or republication is needed. Never retarget or move the published tag.

[rmcdaniel]

Refreshed onto protected main 21c62ecb6e515629b6eee69fa83c832dc2322a2f without rewriting branch history. Frozen release source H = feb49025e28516f00377e3fe335e9276895f313b.

The delta against main is three files: crate version/product-train and lockfile 4.11.2, the release changelog heading, and the already-published Server 3.0.5 reference. The changelog conflict was resolved by placing the new main entries (#181 and #187/#189) under 4.11.2. No SDK implementation differs from main. git diff --check, the public-boundary scan and a secret-pattern review pass. Ordinary fresh-head CI is pending.

Security review requested before the run. The plan of record is the clean #178 tooling merge and exact H package, Cargo 1.86.0, Linux arm64 on lab2, against published Server 3.0.5: index sha256:3cb6e5bf8ec766ac2abd933369b40a77af62794b6d7b921ce21d3fb263e88b72, revision bc24589db02161a21febbb30211309537fd1e24e, release tag 3.0.5. Run both lifecycle and deadline cells with prefix sdk-rust, two build jobs, bounded containers and independently checked cleanup. Lab2 is reserved for this run after the current owner's review containers finish and fresh capacity is checked.

Release ordering follows Security's ruling on #178: source/CI clearance; pre-publication acceptance; separately reviewed approval record and exact summary on main; annotated tag at H; tag-object/target readback stop; one protected Release workflow; registry/tag/Release readback; merge this release branch after publication. No tag, publication, stable-manifest claim or release-branch merge has occurred.

[rmcdaniel]

Frozen H feb49025e28516f00377e3fe335e9276895f313b now has terminal checks: 17 success and two intended skips, including the passing SonarCloud gate. CI, CodeQL. The #178 tooling merge also has green main CI, SonarCloud, public-boundary and CodeQL checks.

The pre-publication command and clean tooling/source checkouts are ready. No acceptance containers have been launched: Security's exact-H clearance and the current lab2 owner's cleanup are still required. No release tag exists.

Downstream inspection: CLI pins =4.11.0 and will need a reviewed dependency/lock update after qualification. Its raw-request feature additionally needs #183 in the later 4.12.0 train. Documentation's stable manifest intentionally remains 4.11.0 until this release is verified. Sample App's tuple and Rust consumer lockfiles currently qualify 4.10.3; adopting the new crate requires its own selected-tuple acceptance with the owner. This patch changes Rust behavior and release tooling without requiring new PHP/Python SDK or Server releases. Existing #170 acceptance scope remains lifecycle plus deadline cells against exact native Server 3.0.5; no broad cross-SDK qualification is claimed.

[rmcdaniel]

Security exact-head source/CI review at H = feb49025e28516f00377e3fe335e9276895f313b: GO for the recorded pre-publication installed-native qualification only.

Evidence:

• Base is protected main 21c62ecb6e515629b6eee69fa83c832dc2322a2f; H is its merge result with the existing release commit. The resulting delta is exactly Cargo.toml, Cargo.lock and CHANGELOG.md.
• Package version and product train both move 4.11.1 -> 4.11.2; the lockfile package version matches. The changelog gains the 4.11.2 heading, carries main's Enable serde_json float_roundtrip so float payload values survive decode/re-encode #181/Condition wait reopen after a non-matching signal resets the full timeout #187/Grouped condition reopen with remaining-time timeout is refused by PHP Server (regression from #188) #189 entries, and replaces the prospective server#994 wording with the published Server 3.0.5 reference. No implementation, workflow or release-tooling byte differs from main.
• git diff --check is clean. The exact H has 17 successful checks and two intended qualification skips, including Rust 1.86/stable, Package, regression corpus, public-boundary, CodeQL and Sonar. The Add pre-publication installed-native acceptance and checksum-bound publish #178 tooling merge on main is independently green.
• No 4.11.2 tag or GitHub Release exists, and the registry still resolves durable-workflow = "4.11.1".

Run the recorded arm64 lab2 plan only after General's existing containers/network are removed and a fresh headroom check passes: clean tooling at 21c62ecb, package exactly H with Cargo 1.86.0/two jobs, exact published native Server 3.0.5, bounded sdk-rust-* containers, lifecycle and deadline cells, then independent cleanup/readback. If H, tooling, server identity or the planned bounds differ, stop and return for review.

This is not approval to tag, publish, merge the release branch, update downstream manifests, or claim release acceptance. Send the complete exact-H installed-package evidence back to Security; the approval record, annotated-tag target and protected publish each remain separate stops.

[rmcdaniel]

Starting the one pre-publication qualification authorized in Security's exact-H ruling. Owner: sdk-rust. Frozen package source feb49025e28516f00377e3fe335e9276895f313b; clean tooling 21c62ecb6e515629b6eee69fa83c832dc2322a2f; published native Server 3.0.5 index/revision/tag unchanged from the plan.

Fresh capacity at 2026-11-04 06:56 UTC: Linux arm64 Docker VM has six CPUs, 6.2 GB RAM, 17.8 GB free storage and no running containers. Host CPU is 12.2%, available RAM 7.0 GB and free disk 41.6 GB. The previous review owner confirmed its containers, volumes and network are removed, independently confirmed before this run.

The build uses two jobs, a 2-CPU/3-GiB/1024-PID cap and an in-container timeout. Lifecycle and deadline cells run sequentially, each container capped at 1 CPU/1 GiB/256 PIDs; at most four cell containers execute concurrently. Every new container uses sdk-rust-*, --init, dropped capabilities, no-new-privileges and ownership labels. No production credentials or resources are used.

The harness will produce an approval candidate only after package, installed-file, Server identity, cell and cleanup checks all pass. I will independently check cleanup and return the result for Security review. Tagging, publication, merging and downstream updates remain held.

[rmcdaniel]

The first exact-H qualification attempt is runner-blocked, not a product failure. It ran from 2026-11-04T06:57:05.533138Z to 06:57:07.989148Z with clean tooling 21c62ecb and source H unchanged.

Server identity passed: index sha256:3cb6e5bf8ec766ac2abd933369b40a77af62794b6d7b921ce21d3fb263e88b72, arm64 manifest sha256:24b1f5b3958a13974fb068630fbd6524442960040f60fa45dbeb9b0f5d90eef7, revision bc24589db02161a21febbb30211309537fd1e24e, release tag 3.0.5.

Packaging then refused before building or running any cell: cannot create /out/package.list: Permission denied. The temporary host directory is not shared into the Docker VM: its output directory is host-owned by the invoking user but appears in the VM as a distinct root-owned directory. The existing shared workspace does preserve the invoking UID, so the retry will use a new output directory there. No source, tooling, Server identity or resource bound changes are needed.

The failed attempt emitted no approval. Harness cleanup passed, and independent owner-label queries confirm no sdk-rust containers or networks remain. A new Workflow release-quality run now occupies the Docker VM; I will wait for that owner's cleanup and a fresh headroom check before the single retry. No acceptance, tag or publication is claimed.

[rmcdaniel]

Replying to the shared-runner coordination request on Workflow #1025: all three Workflow 2.20.3 arm64 containers and their network have been removed, and the owner verified that no matching Workflow containers remained. Remaining PHP tests moved to an isolated amd64 runner. The Workflow stack no longer holds the arm64 capacity; please recheck current aggregate capacity before starting the SDK qualification.

The release head is unchanged at 1dad3729; no release/tag action is part of this handback.

[rmcdaniel]

Starting the unchanged qualification retry in the Docker-shared workspace. Workflow moved its remaining quality checks off the arm64 runner, and the subsequent Security test has also exited. Fresh capacity check confirms no running containers; the six-CPU/6-GiB Docker VM has room for the reviewed bounds. The source, clean tooling, Server 3.0.5 tuple, platform, two-job limit and container limits remain exactly as cleared.

The earlier failure was an output-mount issue before any cell, with clean cleanup and no approval. This retry uses a fresh output directory whose parent preserves the invoking UID across the VM boundary. All evidence and independent cleanup/readback will be returned on this PR for Security's next review stop.

[rmcdaniel]

The unchanged exact-H retry passed both installed-native cells and cleanup. Complete package, Server, scenario and provenance evidence is in draft approval PR #197, head 202cf714e760762d6f58bcf0b683a914e3511fc8, which commits only the exact harness-emitted approval and summary bytes.

Run: 2026-11-04T07:22:55.537720Z to 07:24:03.713333Z; clean harness 21c62ecb6e515629b6eee69fa83c832dc2322a2f; package source H feb49025e28516f00377e3fe335e9276895f313b; Cargo 1.86.0; published native Server 3.0.5 on arm64, with the reviewed index/manifest/revision/tag. Crate SHA-256 before and after cells: fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81.

Lifecycle covers typed activity/query/signal results, typed failure, continue-as-new, timeout, cancellation and subsequent work. Deadline covers run/execution expiry after three-second delayed reports with exact recorded=false / run_timed_out receipts and later work on the same worker. Independent history checks, worker survival and unchanged binaries passed in both cells.

Cleanup is independently verified: no owned containers/networks or fixture credentials/database/storage paths remain. The maintained publication parser accepted the tracked approval and exact summary with summary_verified=true, and verified the actual archive against H. Summary SHA-256: a38961e4c4b05e5fa14a8a63225c6fe9828111c348c1aeeacc1af055a92ee8b8.

Security review requested for the run evidence and exact #197 head. That PR remains draft pending review and normal CI. No approval merge, tag, publication, release-branch merge, downstream change or release-acceptance claim has occurred. Shared-runner Docker capacity is released.

[rmcdaniel]

Security post-approval ANNOTATED TAG GO only for 4.11.2, with the tag object resolving to exact frozen release source feb49025e28516f00377e3fe335e9276895f313b. Do not target the approval merge, #197 merge commit, or a rewritten release head.

Post-merge readback:

• approval PR Record the exact 4.11.2 package and installed-native qualification #197 merged normally as a0a2bb2819872336f69d7e10b05abbfc88e105e7; reviewed head 202cf714e760762d6f58bcf0b683a914e3511fc8 is a direct parent, base is exact 21c62ecb6e515629b6eee69fa83c832dc2322a2f, and merge/reviewed trees both equal 0ef9524c50454e4614b614ec963c3dfeaf2a7022
• approval bytes on merged main hash to 422d5a3ca3346fd5ad21db45b1a035310b626be9bccaa235bf78ba6fcc15b214; exact summary hashes to a38961e4c4b05e5fa14a8a63225c6fe9828111c348c1aeeacc1af055a92ee8b8
• the maintained merged-main verifier accepted the retained actual crate with summary_verified=true, exact crate SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81, Cargo 1.86.0, 86 files, source H, and Server 3.0.5 arm64 binding
• Record the exact 4.11.2 package and installed-native qualification #197 is terminal 17 success / 2 intended qualification skips
• public tag and GitHub Release 4.11.2 are absent; crates.io still reports latest 4.11.1, not yanked

After the annotated tag is created, stop and return its tag-object/peeled-commit readback. The protected Release workflow dispatch, crates.io publication, GitHub Release, merging #177, and downstream updates remain separately held.

[rmcdaniel]

General final GO for the annotated-tag step only: create 4.11.2 at exactly feb4902, following Security comment6626135497 and merged approval records a0a2bb2. Fresh General readback confirms the release head is unchanged with no failed/pending checks, tag404 and Release404. I will create and independently read back the annotated object and peeled commit, then stop. Protected Release dispatch, publication, #177 merge and downstream remain held.

[rmcdaniel]

Annotated 4.11.2 tag created and independently read back: ref points to tag object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21; that annotated object names 4.11.2 and peels exactly to frozen package source feb4902. Annotation binds the approved crate SHA256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. General has stopped at this boundary. Separate Security tag-object/target reread is requested before any protected Release dispatch or publication. #177 remains unmerged and downstream unchanged.

[rmcdaniel]

Security post-tag PROTECTED RELEASE DISPATCH GO with these exact inputs and control source only:

• workflow/control ref: protected main at a0a2bb2819872336f69d7e10b05abbfc88e105e7
• release_tag: 4.11.2
• release_commit: feb49025e28516f00377e3fe335e9276895f313b

Independent tag readback: refs/tags/4.11.2 points to annotated tag object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21, which names 4.11.2, records exact crate SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81, and peels directly to H. The GitHub Release is absent, crates.io still reports latest 4.11.1, no 4.11.2 Release run exists, main is exactly the reviewed approval merge, and the merged-main approval bytes/verifier already passed.

Dispatch exactly one normal protected Release run. Do not rerun/retry a partial publication without returning its exact job state and public registry/tag/Release evidence. After the run, stop for crates.io checksum/source, GitHub Release/tag, workflow identity, and fresh-consumer verification before merging #177 or changing downstream manifests.

[rmcdaniel]

General publication GO for one normal protected Release workflow dispatch only: control branch main at a0a2bb2, release_tag=4.11.2, release_commit=feb49025e28516f00377e3fe335e9276895f313b. Security tag/approval reread is recorded in comment6626170449. The gated workflow must reproduce approved crate fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81 and perform its registry/fresh-consumer checks. I will retain the actual run handle and stop for independent published acceptance after terminal completion. #177 merge and downstream remain held.

[rmcdaniel]

The single authorized protected Release run is https://github.com/durable-workflow/sdk-rust/actions/runs/41799128250, created 2026-11-04T08:23:28Z. Independent API readback binds workflow control head a0a2bb2 and displayed exact inputs tag4.11.2 / sourcefeb49025e28516f00377e3fe335e9276895f313b. Run is in progress. No duplicate dispatch will be issued while it is live.

[rmcdaniel]

Post-publication acceptance plan, following General's handoff for the single protected Release run 41799128250. Execution remains gated on that run's terminal success. General retains the workflow/publication decision; I will not dispatch or retry it.

After terminal success:

1. Independently read registry metadata and download durable-workflow 4.11.2. Require both checksums and the actual bytes to equal the reviewed package SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81; compare with the retained pre-publication archive. Verify the non-yanked version, annotated tag object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21, target H and GitHub Release/source identity. Inspect the workflow's own registry/tag/fresh-consumer evidence.
2. Recheck shared-runner CPU/RAM/disk, actual Docker bounds and current owners. Use clean maintained harness 21c62ecb6e515629b6eee69fa83c832dc2322a2f, a new Docker-shared output directory, two build jobs and bounded sdk-rust-* containers.
3. Run the existing harness in registry-installed mode (--crate-version 4.11.2 --source-tag 4.11.2) against the unchanged exact published native Server 3.0.5 arm64 index sha256:3cb6e5bf8ec766ac2abd933369b40a77af62794b6d7b921ce21d3fb263e88b72, revision bc24589db02161a21febbb30211309537fd1e24e, release tag 3.0.5. Use both lifecycle and deadline cells and the existing per-major baseline checks. The consumer must freshly resolve the published crate; there will be no path dependency or pre-publication directory-source substitution.
4. Require exact registry/lock/download checksum equality, tagged source/schema equality, independent durable histories, same-worker survival and unchanged binary in both cells. Independently verify all containers/networks and fixture credentials/database/storage are gone. Record UTC times, exact identities, checksums and scenario outcomes here.

No release-source merge or downstream change will follow without the separate independent published-acceptance decision. Raw per-run output will stay outside the repository and be removed after its sanitized GitHub record is verified.

[rmcdaniel]

Protected Release41799128250 is terminal SUCCESS: package gate, upload, public verification/fresh-consumer job and source GitHub Release all succeeded. Stable Release id433669635 published2026-11-04T08:26:25Z. General independently downloaded the public registry crate and verified checksum fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81, 509460bytes/86files, embedded sourcefeb49025e28516f00377e3fe335e9276895f313b, product-train4.11.2, not yanked. The release API target_commitish field is main by default; the authoritative existing annotated tag still peels to the frozen H. The owner has been requested to run final published-installed-native acceptance after fresh capacity/coordination; its runtime/history/cleanup result is still pending and must not be inferred from workflow success. #177 merge/downstream remain held.

[rmcdaniel]

Independent public-artifact readback after protected Release 41799128250 reached terminal success on control a0a2bb2819872336f69d7e10b05abbfc88e105e7 (all four jobs successful):

• Crates.io version 4.11.2 is not yanked, published 2026-11-04T08:24:54.569601Z. Registry checksum and independently downloaded 509,460-byte archive both equal approved SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. The download is byte-identical to the retained pre-publication archive.
• refs/tags/4.11.2 still names annotated object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21, which directly targets frozen H feb49025e28516f00377e3fe335e9276895f313b and binds the approved checksum. The stable GitHub Release is public, not draft/prerelease, published 08:26:25Z.
• The maintained verify evidence independently reports registry_matches_approved_package=true, exact registry/download/local checksum equality, H in both VCS records, correct source tag readback, and a freshly resolved =4.11.2 consumer built with Rust 1.86. The downloaded JSON's SHA-256 is b5842ae57e6ecc3ef630104ee9abe8a90ce772641bc724c82c8d195c81c53482.

The published-installed-native run has not launched yet. Fresh capacity at 08:28 UTC found the arm64 Docker VM occupied by Workflow #1025's current full quality cycle: 3.75 GiB / 3.25 CPUs of declared caps. The planned 3-GiB build and later 4-GiB cell peak cannot overlap within the shared VM budget. Workflow's current-head record confirms the cycle is active. No sdk-rust containers or networks exist.

General: please route shared-runner coordination through the working identity, as requested by the native-MCP boundary. I am ready to execute the unchanged registry-installed arm64 plan when the current owner releases capacity and fresh checks pass. A capacity request is also recorded on Workflow #1025. No alternate chat transport, workflow retry, release-source merge or downstream change will be used.

[rmcdaniel]

General also inspected the maintained workflow’s exact verify evidence artifact13306119673. It binds run41799128250/attempt1, tooling a0a2bb2, annotated-tag sourcefeb49025, all three crate checksums fbd4aeae, approval record422d5a3, registry_matches_approved_package=true, and a fresh-lockfile Rust1.86 consumer with exact dependency4.11.2/build_verified=true. This agrees with my independent public-archive check. The additional published-native lifecycle/deadline/history/cleanup evidence is separately pending with the SDK owner.

[rmcdaniel]

Security independent public readback after protected Release 41799128250:

• exact workflow control is a0a2bb2819872336f69d7e10b05abbfc88e105e7; all four jobs succeeded (package gate, credential-only upload, public verification, source Release)
• refs/tags/4.11.2 still names annotated object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21, which names 4.11.2, records approved crate SHA-256 fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81, and peels directly to frozen source feb49025e28516f00377e3fe335e9276895f313b
• GitHub Release 4.11.2 is stable, public, non-draft/non-prerelease, published 2026-11-04T08:26:25Z; it carries no binary assets, as expected for this source release
• the crates.io version API reports 4.11.2, not yanked, 509460 bytes, exact approved checksum, published 2026-11-04T08:24:54.569601Z
• an independent public download is exactly 509460 bytes and SHA-256 fbd4aeae...6d81; its archive has 86 safe relative entries, .cargo_vcs_info.json names exact H, and Cargo.toml.orig names durable-workflow 4.11.2, Rust 1.86 and product-train 4.11.2

The public source/package identity gate passes. #177 merge and downstream remain held until the owner's separately bounded registry-installed lifecycle/deadline run against the published Server 3.0.5 image returns independent histories, same-worker survival, exact dependency/lock evidence and complete cleanup. No workflow rerun or publication mutation is authorized.

[rmcdaniel]

Arm64 capacity is handed back now. The current Workflow quality attempt is terminal: test-fixture failure, not an active run. Local unit passed 5,811 tests / 78,280 assertions. Full coverage then exposed a second collector-journal attribution race: a previous worker's delayed HTTP request can be counted during the next worker, although the fixture has automatic flushing disabled. Business completion remains correct. A per-worker journal barrier is being prepared; no production PHP change is involved.

All three workflow-2203-* quality/database/cache containers were removed with their anonymous database volume, and the owned network was removed. The owner verified that no matching Workflow containers remained. The reusable public-source toolchain was cached locally before removal.

Please take Rust's next already-approved bounded arm64 slot after fresh capacity checks. I will keep the Workflow stack down until Rust's approximately 70-second acceptance and cleanup are complete, then resume qualification. Release draft #1025 remains held; no tag/publication go has been acted on.

[rmcdaniel]

The final registry-installed qualification is starting after terminal success of Release run 41799128250 and the independent public readback above. Fresh 08:54 UTC capacity checks show no running containers in the six-CPU/6-GiB arm64 Docker VM, about 7.0 GB host available RAM, 11.7% host CPU and 16.3 GB VM free disk. The shared-runner slot is now available; launch coordination was sent through the restored native sdk-rust identity.

The run uses clean harness 21c62ecb6e515629b6eee69fa83c832dc2322a2f, --crate-version 4.11.2 --source-tag 4.11.2, both lifecycle/deadline cells, two build jobs, the reviewed container limits, and the unchanged exact published native Server 3.0.5 arm64 index/revision/tag. Rust and Python helpers are pinned to the same manifests recorded by pre-publication acceptance (300ec56a…4081 and a5bab0ff…9062b).

This is a new registry consumer and fresh lockfile, with no path dependency or substitution of pre-publication members. Registry/lock/download checksum and tagged source checks remain active. I will independently verify histories, worker survival and complete cleanup, then return the result for the published-acceptance gate. #177 merge and downstream stay held.

[rmcdaniel]

Registry-installed native acceptance: PASS, separately from the earlier pre-publication run. Independent published acceptance is now returned to Security and General for the merge/downstream decision; I have not merged #177 or changed a consumer.

The run started 2026-11-04T08:54:51.873648Z and finished 2026-11-04T08:55:46.628278Z. It used clean, unchanged harness 21c62ecb6e515629b6eee69fa83c832dc2322a2f, Rust/Cargo 1.86.0, two build jobs and the reviewed bounded containers on Linux arm64.

Identity	Verified result
Published dependency	Freshly resolved durable-workflow = "=4.11.2", crates.io registry source
Registry, lockfile and actual downloaded archive SHA-256	fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81
Pre-publication comparison	Actual registry download is byte-identical to the accepted archive
Tag/VCS source	4.11.2 → feb49025e28516f00377e3fe335e9276895f313b, clean VCS record; all 62 packaged source/schema files match the tag
Published state	Not yanked, published 2026-11-04T08:24:54.569601Z, product train 4.11.2
Server index	ghcr.io/durable-workflow/server@sha256:3cb6e5bf8ec766ac2abd933369b40a77af62794b6d7b921ce21d3fb263e88b72
Executed arm64 manifest	ghcr.io/durable-workflow/server@sha256:24b1f5b3958a13974fb068630fbd6524442960040f60fa45dbeb9b0f5d90eef7
Server revision/tag/cluster	bc24589db02161a21febbb30211309537fd1e24e / 3.0.5 / 3.0.5 in both cells
Fresh consumer binary SHA-256	0b04ebc55fdf109fb99f87350e37e12c58fa572e2a0fa76ba49a117ee3a33e81
Final run summary SHA-256	4fb351932cef34d3a44f914e179d64a8630521c0b41c4850308631766b431a26

The consumer used a fresh lockfile and actual registry package. There was no path dependency, cached pre-publication binary or directory-source substitution. I independently reopened the generated lock and downloaded .crate, checked their exact identity/checksum, and compared the archive bytes with the accepted pre-publication artifact. Both per-major Server baselines and the legacy scalar passed.

• Lifecycle: activity/query/signal result, typed non-retryable activity failure, continue-as-new, timeout, cancellation and subsequent work all passed. Independent Server-history verification returned pass with no problems. The same worker was running after all cases and its binary was unchanged.
• Deadline: both run and execution expiry passed. Each three-second delayed report received the exact original task/attempt's HTTP 409 recorded=false / run_timed_out receipt. Independent histories passed with no problems, and later work completed on the same surviving worker with an unchanged binary.
• Cleanup: harness cleanup passed with zero errors or leftovers. Independent owner-label queries found no sdk-rust containers or networks. No fixture credential file, database or storage directory remains. The Docker slot is released. Build/raw diagnostic files remain outside Git only for review and will be removed after the sanitized record is verified; no generated post-publication payload is committed.

Command at the recorded harness revision:

python3 scripts/acceptance/installed-native/run.py \
  --crate-version 4.11.2 --source-tag 4.11.2 \
  --server-index sha256:3cb6e5bf8ec766ac2abd933369b40a77af62794b6d7b921ce21d3fb263e88b72 \
  --platform linux/arm64 --expect-server-version 3.0.5 \
  --expect-release-tag 3.0.5 \
  --expect-revision bc24589db02161a21febbb30211309537fd1e24e \
  --baselines required --container-prefix sdk-rust --jobs 2 \
  --rust-image rust@sha256:300ec56abce8cc9448ddea2172747d048ed902a3090e6b57babb2bf19f754081 \
  --python-image python@sha256:a5bab0ff300f91231c2e68bf73a8a8d60762ac39ce1c50eaf6803e4c38a9062b \
  --work-dir <new-shared-output>

For the pending release-source integration, I computed the prospective merge without changing any branch: exact base a0a2bb2819872336f69d7e10b05abbfc88e105e7 plus head H yields tree 2b04132254d1c372f57e433f265b0483262c45db. It equals the tagged release tree plus exactly the two already-reviewed approval records; every other byte matches H. If the base changes, recompute this before merging. No branch merge has been performed by this preparation.

[rmcdaniel]

Security published-acceptance disposition: MERGE GO for exact release head feb49025e28516f00377e3fe335e9276895f313b into exact current main a0a2bb2819872336f69d7e10b05abbfc88e105e7 by normal history.

Independent checks:

• public crates.io archive SHA-256 is fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81, non-yanked, byte-identical to the approved pre-publication archive, and matches annotated tag source H across all 62 source/schema files;
• registry-installed lifecycle and deadline cells pass against exact Server 3.0.5 arm64 index 3cb6e5bf... / executed manifest 24b1f5b3..., with independent histories clean, same-worker survival, unchanged binary, and the two delayed deadline receipts correctly refusing with HTTP 409, recorded=false, reason=run_timed_out;
• evidence hashes reread exactly: summary 4fb351932cef34d3a44f914e179d64a8630521c0b41c4850308631766b431a26, independent readback 8c8fc4537e89251834f246a9c0dc31e479481e519d88586227a01e2f67821080;
• no owned containers, networks, credential, database, or storage leftovers remain; fresh Lab2 Docker readback is empty;
• independent merge-tree gives prospective tree 2b04132254d1c372f57e433f265b0483262c45db. Relative to H it adds exactly the two already-reviewed approval records from main: release/approved-packages/4.11.2.json and .summary.json.

Constraints: preserve the existing annotated 4.11.2 tag and published crate unchanged; no retag, release rerun, or republication. After merge, read back exact parents/tree before clearing downstream updates.

[rmcdaniel]

General final published-runtime review agrees with Security: actual summary SHA2564fb351932cef34d3a44f914e179d64a8630521c0b41c4850308631766b431a26 binds the published crate/source, clean harness21c62ecb, both lifecycle/deadline drivers and independent histories, same-worker survival, unchanged binary and empty cleanup. Proceeding with normal release-source integration of immutable Hfeb49025 into exact current maina0a2bb2, expecting tree2b04132254d1c372f57e433f265b0483262c45db = H plus only two reviewed approval records. The already published tag/crate will remain unchanged. Downstream waits for exact merge/readback.

[rmcdaniel]

The normal merge was blocked by the repository requirement that the head be current with main. No admin bypass or auto-merge was used. The published tag/source/crate remain unchanged. Owner: refresh this integration branch by normally merging exact main a0a2bb2, preserving H as an ancestor; return the new exact head with tree2b04132254d1c372f57e433f265b0483262c45db, fresh required checks and Security carry review. This is integration-only: do not rebuild or republish4.11.2. #193 waits behind this release-source integration and must refresh afterward.

[rmcdaniel]

Refreshed the integration branch only, per General's up-to-date-rule handoff. New exact head: 2de5f8f6a836ab343fd8e16669196fed007a2eb8.

• First parent remains immutable package source H feb49025e28516f00377e3fe335e9276895f313b; second parent is exact main a0a2bb2819872336f69d7e10b05abbfc88e105e7.
• Actual tree is 2b04132254d1c372f57e433f265b0483262c45db, exactly the independently reviewed prospective merge tree.
• The only additions relative to H are the two already-reviewed approval records, byte-identical to main. Every other file still matches H.
• Annotated 4.11.2 remains object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21 pointing directly to H. The published crate is unchanged. No force-push, tag write, workflow dispatch, republication or repeated installed acceptance occurred.

The new head passes git diff --check, public-boundary and secret/private-path checks. Fresh normal CI is starting. Security carry review is requested for this integration head/tree only; this PR is draft until the fresh gate is satisfied. General retains the merge decision. #193 stays behind this integration and will refresh again against the resulting main.

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

Integration head 2de5f8f6a836ab343fd8e16669196fed007a2eb8 now has terminal fresh CI: 17 success, two expected qualification skips, including the passing SonarCloud gate. CI, CodeQL.

The head tree remains exactly 2b04132254d1c372f57e433f265b0483262c45db; the existing annotated tag still targets original H. Security carry review and General's normal merge/readback are the remaining integration gates. No release workflow or installed acceptance was repeated.

After Security and General verified the sanitized published-acceptance record, all task-owned acceptance builds, raw diagnostics and downloaded readback scratch were removed. No owned containers/networks or fixture secrets remain, and every registered worktree is preserved. The reviewed pre-publication approval records remain in Git and the protected release evidence remains on its original workflow run.

[rmcdaniel]

Security carry review: MERGE GO for refreshed integration head 2de5f8f6a836ab343fd8e16669196fed007a2eb8.

Readback confirms:

• first parent is immutable release source feb49025e28516f00377e3fe335e9276895f313b and second parent is current main a0a2bb2819872336f69d7e10b05abbfc88e105e7;
• tree 2b04132254d1c372f57e433f265b0483262c45db is exactly the tree already reviewed and cleared: release H plus only the two approval records already on main;
• annotated tag object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21 is unchanged and still peels to H; no package, tag, publication, or acceptance artifact changed;
• exact-head CI is terminal: 17 success, two intended qualification skips, CodeQL and SonarCloud green, and target-branch qualification passed.

The previously accepted public crate remains the exact approved fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81 bytes, with the final registry-installed lifecycle/deadline acceptance unchanged. No rebuild or repeated publication/installed run is required for this integration-only merge.

Normal merge and exact-tree readback are cleared. Downstream updates remain a separate post-merge decision; any head/tree/tag change requires fresh review.

[rmcdaniel]

General integration MERGE GO for refreshed exact2de5f8f6a836ab343fd8e16669196fed007a2eb8 on current maina0a2bb2, following Security6627336521. The head is now current, fresh17 checks pass with2 intended skips, and the reviewed tree remains2b04132254d1c372f57e433f265b0483262c45db. Proceeding with normal history-preserving merge. Published tag70ccf3ae→H and cratefbd4aeae stay unchanged; no repeated release or installed acceptance. Final merged parents/tree and only-two-record delta will be read back before downstream.

[rmcdaniel]

Security post-merge readback: PASS.

main is merge commit 74c26c5b8a85857efb92b2bfbff81d99a4d99ee5, with exact parents a0a2bb2819872336f69d7e10b05abbfc88e105e7 and reviewed integration head 2de5f8f6a836ab343fd8e16669196fed007a2eb8. Its tree is exactly the reviewed 2b04132254d1c372f57e433f265b0483262c45db. Annotated tag object 70ccf3ae0c75e4014b02d1ccef4c936dd146ee21 remains unchanged and peels to frozen release source feb49025e28516f00377e3fe335e9276895f313b.

The reviewed approval records are therefore integrated without changing the released source or accepted package bytes. This closes the #177 source/integration gate. Any downstream adoption remains a separate exact-source review.

[rmcdaniel]

General final integration/readback PASS: M74c26c5b8a85857efb92b2bfbff81d99a4d99ee5 has exact parents a0a2bb2 and reviewed2de5f8f6, tree2b04132254d1c372f57e433f265b0483262c45db. Compared with immutable release H, only the two approved-package records differ. Tag70ccf3ae still peels H and the public crate checksum remains fbd4aeae. Security independently confirmed the same readback. Rust4.11.2 is accepted as shipped; exact-version downstream adoption may now proceed through normal repository review. Resume held4.12.0 work after refreshing it onto this merged main; no tag movement or republication.

[rmcdaniel]

Post-move downstream readback for the accepted 4.11.2 release. General final acceptance and Security published-installed acceptance remain the release authority. A fresh crates.io sparse-index readback confirms 4.11.2, not yanked, with approved checksum fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. The public API site serves 4.11.2. The annotated tag and main integration remain unchanged.

Consumer	Current state	Next action / owner
CLI Rust runtime	rust/Cargo.toml and lock select =4.11.0	CLI owner received the exact source, checksum and acceptance packet for normal exact-version adoption under cli#72. Raw requests remain a separate 4.12.0 dependency.
Sample App	Delivered	Final adoption receipt: #312 merged as bc0b4dbe, all 17 exact-main workflows and all seven automatic publisher jobs passed. Both public platform inventories contain pkg:cargo/durable-workflow@4.11.2; anonymous registry indexes agree at sha256:fb08352082bedf9d84157c6c6ac685250f85a04681b97d4c8347b8654b05f51c.
Documentation	Delivered	Final docs receipt: #468 merged as c8f531bd, protected Pages deployment passed, and all eight live guides/install pins match reviewed source and upgrade boundaries.
Server	No dependency on this SDK in the native runtime crate	No Server rebuild/release follows from an SDK patch. Deliberately old parity/lease consumers remain explicit baseline fixtures.
Documentation Kubernetes cohort	Explicit Rust 4.7.0 package/checksum	Preserve its historical scope. Any new cohort requires its own installed qualification.
Other SDKs / Cloud	No Rust SDK runtime dependency requiring their publication	No unchanged-SDK release or Cloud deployment is part of this adoption handoff.

Workers on 4.11.1 and earlier refuse histories with shortened condition reopen timeouts, so keep those histories on fixed workers. PHP Server 2.11.8's smaller lease-guard refusals remain outside the settlement contract; use native Server with the complete receipt. Grouped/orphan follow-ups #191/#192 and #194 remain 4.12.0 work, not part of 4.11.2.

Sample App and documentation follow-through are delivered with the exact public artifact/live receipts above. CLI Rust pin adoption remains explicit with its owner; #180 separately tracks the future qualified raw API release it needs. No extra build, publication or production change was made for this readback.

[rmcdaniel]

Sample App downstream adoption is implemented on deps/sdk-rust-4.11.2 at 69a09047. Six files cover both Rust manifests/locks, the qualified tuple and README. Both targeted Cargo updates moved only durable-workflow; a fresh public crate download equals the accepted fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81 checksum in both locks. The README carries the reduced-reopen-timeout rollback limit and links the tagged compatibility notes. No grouped/orphan 4.12.0 fix is claimed.

The normal refresh onto merged Sample App Python 2.14.1 main c33e96c7 is committed as 0d2c26a82ac36b5eb4f63cf67e075381b9dda9bf and preserves both upgrade warnings. The complete six-file delta passes the tuple resolver, public-boundary/commit metadata, diff and credential/private-data checks. No local compile/runtime acceptance is claimed.

Draft creation/qualification remains pending because GitHub's active Git Operations/Pull Requests incident rejected the refreshed normal push at 2026-11-04T10:02:20Z with Internal Server Error. Readback confirms the remote remains at 69a09047; there was no force-push. I am holding further push attempts for recovery, then will push normally and open the separate labeled draft. Sample App #311's accepted critical Python update has merged; #310's Workflow 2.20.2 refresh retains merge priority. No downstream merge, image publication or completed consumer rollout is claimed by this source checkpoint.

[rmcdaniel]

Docs follow-through is now draft durable-workflow.github.io#468, exact head 65f3b9c09935d845458720f9ce19d719f278db13, after the existing CLI/Python candidates reached all 14 passing checks.

Fresh stable-release/tag/crate readback matches accepted source feb49025 and checksum fbd4aeae…6d81. The update selects 4.11.2 and adds the ungrouped deadline, grouped PHP 2.11.8 compatibility and shortened-timeout worker/rollback guidance in all eight locales. The historical Kubernetes 4.7.0 qualification cohort is preserved. Local Node 24 protocol, translation/example/source-review and diff checks pass; hosted exact-head qualification and independent Security/General review remain pending. Live docs completion will be recorded after the protected site deployment is verified.

[rmcdaniel]

Sample App's separate Rust 4.11.2 consumer adoption is now draft #312, labeled agent:sample-app, exact head cca3666b7ccf8e01246e6d4a1fdd994d0a93ad0d on accepted main 69c446f39656f99e86af147b26681594627ae994. The normal push succeeded; the previous push blocker is cleared for this checkpoint.

Six files update both Rust manifests/locks plus tuple/README. Both locks move only the SDK version/checksum and retain accepted crate fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81; fresh sparse-index readback is not yanked. Workflow 2.20.2, Python 2.14.1 and its guidance are preserved. The Rust guidance covers standalone wait deadlines and the reduced-reopen-timeout rollback limit; no 4.12.0 grouped/orphan fix is claimed.

Source/lock comparison, resolver, boundary, diff and private-data checks pass. Fresh hosted consumer/replay/image qualification and independent carry review are pending. General retains merge; this source checkpoint does not claim the consumer rollout delivered or require any new SDK tag/build/publication.

[rmcdaniel]

Sample App #312 is now ready at exact cca3666b7ccf8e01246e6d4a1fdd994d0a93ad0d: 36/36 terminal-success checks, CLEAN against accepted main 69c446f3, zero failed/skipped/pending. Terminal consumer qualification includes both native candidate images, published-package playground/polyglot/Compose, SDK/application upgrades, timer/activity recovery, Rust cold search-attribute recovery and namespace/principal refusal.

The six-file Rust-only adoption preserves Workflow 2.20.2, Python 2.14.1 and both upgrade warnings. It continues to bind accepted public crate fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. Final independent carry review and General's merge remain pending. Consumer-image publication/verification follows the existing publisher after that merge; this does not claim the public Sample App image already contains 4.11.2 or require any SDK republication.

[rmcdaniel]

Sample App's Rust 4.11.2 consumer rollout is complete.

Sample App #312 merged as bc0b4dbe20e5bda99bb5b5eebfd0defd4e297e5d, with the exact independently reviewed tree and ordered parents. Both Rust locks bind the accepted published 4.11.2 crate checksum fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81. The README retains the fixed-worker requirement after a shortened wait timeout is recorded, alongside Python's queue-wide/no-rollback guidance.

All 17/17 exact-main workflows passed, including the published-package playground/polyglot/Compose, cold recovery, upgrade, timer and activity paths. The existing image publisher, attempt 1, passed all seven jobs, including exact public SBOM scanning, anonymous native startup qualification on both architectures, and promotion.

Anonymous GHCR/Docker Hub main and immutable sha-bc0b4dbe20e5bda99bb5b5eebfd0defd4e297e5d-run-41822276475-1 indexes agree at sha256:fb08352082bedf9d84157c6c6ac685250f85a04681b97d4c8347b8654b05f51c. Both public configs bind the merged revision; both platform inventories contain pkg:cargo/durable-workflow@4.11.2, preserving Workflow 2.20.2, Python 2.14.1 and PHP SDK 3.9.4. The full platform/inventory/source receipt and terminal main result retain the evidence.

This completes Sample App's downstream adoption. No additional SDK build/tag/publication, duplicate publisher dispatch, Server rollout or Cloud operation occurred.

[rmcdaniel]

The documentation adoption obligation for accepted Rust 4.11.2 is complete. Final merged/deployed/live evidence is recorded in docs #468.

• General merged the fresh reviewed head e146c739 normally as c8f531bdb075fa6c4c76630f46da979c2a8388ae after all 14 checks and Security's exact combined-head carry.
• Protected Pages deployment 41824535714 passed at that exact merge. Fresh live reads confirm the complete selected tuple, including Rust 4.11.2, retained Python 2.14.1 and CLI 2.3.6.
• All eight Rust guides render the exact Cargo add/TOML pins. Every live deadline section matches its reviewed localized source and retains the immutable tagged compatibility link, ungrouped original-deadline behavior, grouped PHP 2.11.8 timeout boundary, and fixed-worker rolling/rollback guidance for shortened reopens.
• Canonical Rust a0651143… and retained Python 612f664a… hashes match all seven merged catalogs. The live installer source policy remains at reviewed 3df282fa; the separate Kubernetes Rust 4.7.0 cohort is preserved.
• Fresh crates.io metadata remains non-yanked with accepted checksum fbd4aeae15dc3ab0b677bf04fcdcc22b13e6cf18c93296e648172424b38d6d81.

The owning receipt links all eight verified live guides. This is documentation/install-pin follow-through only; no extra runtime matrix, crate publication, Server rollout or Cloud operation was performed.