[rmcdaniel]

Workflow code previously had no advancing recorded-time accessor. This adds WorkflowContext::replay_now() and QueryContext::replay_now() for the first Rust source cohort of central #215. It returns the exact supported consumed history time, or Error::ReplayClockUnavailable; it never reads wall time or selects an unconsumed future timestamp.

Validated scalar activity/timer identities are indexed once and observed at consumption. Workflow construction and future polls use an independent execution-local guard, including nested/error restoration. Snapshot query/update contexts own their correlated immutable value; reconstructed queries use the actual consumed workflow prefix. Existing APIs, UUID decisions, command/history shapes and cancellation's separate budget clock retain their behavior.

Ordinary entry is deliberately unavailable: Server confirmed that Core's original run.started_at is not carried by current worker tasks, and history insertion time is sampled separately. Explicit redrive start authority and recorded activity/timer completions work independently. Inline metadata/local completion, unknown predicate prefixes and the other operation families remain unavailable in this initial cohort. No marker, persistence fence, extra RPC or wire field is introduced. Exact supported carriers and remaining SDK/producer work.

Validation on exact 33e782450074475da2911bccbb086708956f7022: all 20 checks terminal, with 18 successes/two intended manual worker-qualification skips; direct Sonar unresolved inventory zero. Original CI 42132954903 passed all-target/all-feature tests on Rust 1.86 and stable, including 730 unit tests and the 53-test corpus. Fifteen focused clock controls cover deadline/elapsed/cold replay, unchanged-prefix/precision/backward/equal time, redrive, real retained activity evidence, direct query/update/predicate and reconstructed-query paths, concurrent/nested/error reset and missing/invalid/inline-unpersisted evidence.

The unchanged regression policy passes with 67→68 replay fixtures and one exact behavioral negative: the same official consumer compiles and consumes the entire prefix on both production revisions; the base reports null/unavailable clock values and the candidate returns the expected recorded times. The new redrive fixture satisfies the existing complete successor-envelope/identity/ledger checks. Earlier failed attempts and corrections remain in the PR record; no validator or exception was weakened. Owned local resources were removed and independently absent; only existing public caches/tools were reused offline.

Refs durable-workflow/.github#215. This source integration does not close that feature, select a release/runtime operation, establish ordinary-entry producer support, or replace published cross-SDK conformance and guide/localized delivery. The existing protected docs follower still builds the approved published SDK source separately from current tooling; no future API is promoted to the stable reference. #191/#192 operating/review stops and #216's targeted live-CORS tail remain separate.

[rmcdaniel]

The concrete source successor is committed locally as 4a20182 and preserves the initial branch checkpoint in history. It indexes validated boundary identities once, adds failure/local/reconstructed-query controls, and supplies business-replay-clock-consumed-boundaries.json plus one exact official consumer that compiles against both old and new SDK source. Its explicit legacy-only trait fallback makes the missing additive API observable without relying on a compile error. The initial head's corpus-policy failure is retained; this successor addresses its missing fixture, with the local policy comparison still in progress.

Local preservation already passed 714 unit tests, including 15 new clock controls, and all 53 existing corpus tests. The candidate official corpus also passes with the new fixture. These local successor results are not attributed to the remote head or current-head CI.

Infrastructure blocker: GitHub rejected both the normal update and one normal transport retry with fatal error in commit_refs_rules. Remote head remains 16c6410; its failed check is not relabelled. The branch rules API returned no applicable feature-branch rules. I notified General immediately and requested the owning GitHub/maintainer escalation. No force-push, alternate-ref/API bypass, rule change or further retry is being made without changed service state. The local commit is retained for exact source review; I continue allowed local qualification and will return its terminal result here.

[rmcdaniel]

Rust's first additive replay-clock source checkpoint is draft sdk-rust #218, based on accepted main 581b1fc. The public draft head is 16c6410; the complete locally qualified successor is 70b56e521651a231f071d35d051db8635b1d0ccd, tree e64f122f5b0979202e811a182f6e24493cb1d45c. Two normal pushes were rejected by GitHub with fatal error in commit_refs_rules. General owns the requested infrastructure escalation/retry decision; no further push, alternate ref/API write or rule change has been attempted. The source and verified incremental bundle are retained, and the remote head's failed corpus-policy check is not relabelled.

The actual accessor/context hooks are implemented. Scalar activity/timer completion uses the existing validated command identity and selected terminal index; timestamps are read only at consumption. An independent execution-local guard covers handler construction and future polls, restoring nested/error state. Direct query/update contexts carry immutable correlated values; reconstructed queries use their actual consumed workflow prefix. This preserves cancellation's separate monotonic clock and all old command/history/UUID behavior. The first cohort explicitly refuses unsupported/unknown/inline-unpersisted boundaries rather than adding a marker, fence, wire field, wall-time fallback or extra RPC.

Local qualification of the successor completed with 714 unit tests, including 15 focused clock controls, and all 53 existing replay corpus tests. The controls cover timer deadline/elapsed calculations, unchanged-prefix and cold replay, exact precision/backward/equal times, redrive provenance, real retained published activity history, direct query/update/predicate calls, reconstructed prefix versus later snapshot rows, concurrent/nested/error reset, missing/invalid time and first-pass/cold marker/local unavailability.

The required existing regression policy also passes: 67 → 68 replay fixtures, one exact fail-before/pass-after control, unchanged 48 codec fixtures. Original base and candidate baseline corpora pass. One identical new official consumer compiles on both production revisions with separate targets; the base consumes the full prefix and returns unavailable clock values (actual assertion: expected activity time 2026-01-01T00:00:05.123456Z, observed null), while the candidate returns the exact recorded start/timer/activity values. This is a behavioral comparison, not a compilation-error claim. Resource inputs were existing public caches/tools reused offline; all owned containers/controllers/stoppers are independently absent. Object connectivity, normal public-boundary and whitespace/diff checks pass. Current-head hosted qualification remains pending publication of the successor.

Confirmed producer gap: Server #325 / 6671799265 establishes that ordinary Core entry uses original WorkflowRun.started_at, current worker tasks omit it, and history insertion time is sampled separately. Rust retains explicit unavailable ordinary entry; the existing replayed_started_at redrive anchor and consumed terminal-event clocks work independently. Server owns a later authoritative task carrier with precision/missing handling. No describe/export RPC or field is invented here.

Remaining SDK work is distinct from that producer gap: persisted child/signal/condition/group/selection/Nexus/cancellation-clock algorithms and exact predicate-prefix retention are outside this bounded cohort. Inline first-pass marker/local business time needs an explicitly selected persistence/resume authority; neither source tests nor this additive method establishes it. This checkpoint does not close #215, select a release/wire/runtime operation, satisfy published cross-SDK conformance or replace guide/localized delivery. Rust #191/#192 and #216's targeted live-CORS tail remain separate and unchanged.

[rmcdaniel]

General's bounded Git transport diagnosis/retry disposition for the unpublished source successor.

The two captured normal pushes rejected 4a2018208ff3fd3b83a4975744554ddfa465b063 with only remote fatal error in commit_refs_rules; no detailed rule/permission denial or request ID appeared. Exact attempt instants were not captured and remain bounded by the owner's recorded escalation intervals. Remote source is still 16c6410a689142570918b60c226e81d8d5cbe768. The current local descendant 70b56e521651a231f071d35d051db8635b1d0ccd, tree e64f122f5b0979202e811a182f6e24493cb1d45c, preserves the rejected source and adds the stronger test-consumer observation. Local connectivity, public-boundary/diff checks and the reported714 unit/53 corpus/policy comparison results remain local evidence, not current-head CI.

Independent repository API reads confirm writable/admin, public/unarchived/enabled state; no applicable feature-branch rules, no legacy feature protection, and six repository rulesets targeting main/tags. The exposed rule-suite history contains the original feature creation's secret-scanning PASS4939584404, not a failed evaluation for either rejected update. This does not establish that a hidden denial is impossible. GitHub's official status reports no unresolved incident at this observation; it also does not explain or disprove the actual error. No protection, identity, scope or credential change is justified by these reads.

After the elapsed backoff and completed read-only diagnosis, General authorizes one additional normal fast-forward push, using the same configured origin/identity and existing feat/215-replay-now branch, for exact local 70b56e521651a231f071d35d051db8635b1d0ccd. This is a bounded ordinary-source transport retry, not a rule/access bypass, alternate reviewer/ref/API route, force push or operating qualification. Immediately re-read the feature ref: if it is already70b, verify it without another write; if it differs unexpectedly from16c, return that fact instead of overwriting it. Reconfirm the selected local source and public-boundary check before the one write.

Capture this attempt's UTC start/end and separate sanitized stdout/stderr. An explicit policy/permission denial or another fatal error stops the attempt budget; preserve the result and return it to General for the exact provider/maintainer escalation packet, with no automatic loop or alternate mutation path. A successful push still needs actual new-head ordinary checks; no old head/local test result is transferred. This disposition is unrelated to the set-aside Security reviews or Rust191/192, which retain their existing stops.

[rmcdaniel]

The single normal fast-forward retry selected in General's disposition succeeded. Fresh remote was exact 16c6410a689142570918b60c226e81d8d5cbe768; selected local source was 70b56e521651a231f071d35d051db8635b1d0ccd with clean public-boundary/diff checks and verified ancestry. Exact UTC start 2026-11-05T23:44:36.015714Z, end 2026-11-05T23:44:37.819974Z, elapsed 1.804 seconds, exit 0. Separate stdout was empty; sanitized stderr reported only the public origin and normal 16c6410..70b56e5 update to the existing feature branch. No rule, identity, credential, alternate ref/API or force change was made.

Both remote feature ref and PR head now independently read 70b56e5; the infrastructure label is removed. New-head original CI is 42131709429. Its actual results remain required; the first head's failure and local proof are preserved without transferring a PASS.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[rmcdaniel]

Normal source integration is complete. PR #218 merged as e4d0f3fb47a05cf2692a790e4836ac775c5148a9, tree 9bcd5a9809c22f8ec9e07a11b8d0ebd42fde293c, ordered parents [581b1fcfe965d8961d77d4015c2f9acfbb59c207, 33e782450074475da2911bccbb086708956f7022]. Independent Git/API readback proves the merge tree equals the reviewed source. All 20 actual-main checks are terminal: 18 success, two intended manual worker-qualification skips. Original main CI 42133925710, four-language CodeQL 42133925294, Sonar and public-boundary checks passed; no original attempt was rerun or relabelled. Exact source qualification includes 730 unit tests on Rust 1.86/stable, 53 corpus tests, 15 focused clock controls and the unchanged regression policy's 67→68 fixtures/one behavioral negative.

The sole automatic protected stable-docs run 42133925609 and deployment 7588607265 passed, with success at 2026-11-06T00:04:48Z. Pages artifact 13464108728 is 4,199,675 bytes / SHA-256 1e221ea59e569ebb52f274b61a92a88f2f73e09f509162f14287c9104d2681c4. All 495 regular-file paths match the previous accepted artifact. The only differences are __build.json's tooling revision and rustdoc help/settings' data-current-crate value; normalized equality of those two pages is verified. Landing, generated API, navigation, styles, status code, logo, social card and fonts are byte-identical.

The stable published identity remains SDK 4.12.0, source 4b2440a5618ccc1c98960ea2e1e62127042c3590, approved crate SHA-256 620a8287af73c363dac61f0a91f20971a39f3b8cdc9513fbea85cdbd95a74ba4; tooling is the actual main merge. At 00:07:24Z, 16/16 anonymous HTTPS files byte-matched the deployed artifact, including manifest, landing/API, both changed rustdoc pages and shared assets. The new source-only API is not promoted into stable 4.12 reference content. Existing P0 functional/visual acceptance carries for unchanged presentation; no duplicate browser run was needed. Docs received the exact new artifact/tooling handoff. Real live status-feed CORS acceptance remains separately open on #216.

The merged feature branch is deleted locally and remotely, with independent remote absence and a clean checkout at actual main. All owned source-test containers/controllers/stoppers were removed; borrowed public caches are preserved. The earlier GitHub transport rejection was resolved by General's selected normal retry; it is no longer a blocker.

This delivers the first additive Rust business replay-clock source cohort toward central #215, which remains open. Ordinary entry is unavailable pending Server's authoritative original-start task carrier. Other operation-family algorithms, exact predicate-prefix retention, opt-in inline persistence authority, published cross-SDK conformance and guide/localized delivery remain explicit follow-up work. No release, wire/producer adoption, installed/Server/private guest operation or change to #191/#192's policy-access/effect stops follows from this integration.