Repository navigation
Conversation
Part of durable-workflow/.github#216 (safe signal/update retries after a lost response). Work in progress; see the draft PR body for the remaining steps. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
This branch has not been deployed
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
2 participants
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 shared #216.
workflow:signalgains--request-id; signal and update generate one key when omitted, print the key and receipt flags, expose retained-command conflicts, and keep the key visible after transport failures. Output schemas and manifest digests are updated. Blank options retain their existing omitted behavior.Current 6ebce45 corrects the inherited byte restriction to the released Server's 255 Unicode characters, without adding a dependency. Tests-first 6cd3f10 refuses a valid 255-character key; the correction passes 19 command-key/parity cases / 166 assertions. ASCII and Unicode keys preserve exact bytes, and over-limit or malformed UTF-8 keys refuse before sending. These local components do not replace full exact-head CI.
No version bump or safe-retry release is claimed. CHANGELOGs, full normal checks, qualified Core/Server receipt semantics, the published lossy-response CLI/SDK cohort and all eight documentation locales remain pending. Related branches continue independently; conflicts will be resolved and the combined source requalified at integration.