Repository navigation
docs: describe timer replay across published SDK packages - #203
Merged
Merged
Conversation
|
This was referenced Oct 19, 2026
rmcdaniel
marked this pull request as ready for review
October 19, 2026 05:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #122, dependent on Sample251.
Document the separate twelve-original
--sdk-upgradescommand: actual old/new installed packages, unchanged application code, cold replay of original single/concurrent timer histories and fresh controls across PHP/Python/Rust. Preserve package identity, registered SDK/version/definition, complete prefixes, original identities/deadlines and typed results. Keep existing forty timer and twelve version-introduction outcomes distinct. Other operations, combined changes, routing and incompatible class adoption remain separate qualifications.Only two Markdown files change. All three candidate checks and direct Sonar review pass, with zero OPEN/CONFIRMED findings and no ignored conditions. Markdown-only PR duplication is unavailable, not measured zero. No runtime, dependency, tuple, policy or quality-setting change.
Sample source is now merged at
ca2549d04f6191ca95efcb58778572f68a783266, whole9f56968a18c9d55764ad3188a00af2ed2a9e0b5b, identical reviewed99/synthetic21fb. All nineteen candidate checks pass and actual twelve package, forty regression and twelve introduction originals are independently reviewed. The prepared consumer uses existing Python3 and all161 methods pass with jq absent. Initial d6 observer failures stay failed; prior642 component outcomes do not qualify final99.Independent merged Sample main passes all eighteen checks. Fresh main package39202489684, forty39202489550 and introduction39202489540 are separately read back: twelve package originals with exact installations/schedules and absent-worker fires, forty original outcomes with both class fences/restoration, and twelve exact legacy/fresh marker decisions. The first main update job failed pip installation before admission; its one unchanged-job repeat passed, while the original remains failed. No candidate results are carried forward.
Delivered guide merge
f555bbdbfd70ca5566b72493b8136e941252b3b4, whole18339fa6077df20fee3305e8ea74bc894c45aa7c, identical reviewed0a53/syntheticf7e3. Independent main repository39204315656, Sonar39204315653 and app check all PASS. Direct analysis revision is exactf555 and gateOK/no ignored conditions. Published main file blobs match: README f017cf98fd52448590a59fc8ae09c92f65550671 and SDK coverage5fcc7ab2e62d8d815215d1f460110909ae70da58. Completed remote head is independently verified absent. Broader#122 remains open for other accepted coverage gaps.