Repository navigation
docs: add contract fixture comparison and redelivery checks - #16
Draft
upgundecha wants to merge 1 commit into
Draft
upgundecha wants to merge 1 commit into
upgundecha wants to merge 1 commit into
Conversation
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.
Change
Extend the selection guide with evidence for running the same versioned contract fixtures against an emulator and its real service. Record separate run dates/results, fixture revision, emulator and client versions, relevant cloud configuration, and known differences or unrun cases in the evaluation checklist and decision record.
Add an object → queue → worker evaluation scenario in which processing commits a side effect before acknowledgement fails, followed by redelivery and verification of duplicate handling. Distinguish failed settlement from a successful settlement whose response is lost. Update the adoption sequence to include this scenario where the service and receive mode support it.
Evidence and usefulness
The guidance helps readers distinguish application duplicate handling demonstrated locally from service delivery semantics requiring cloud validation. It describes an evaluation approach, without adding unverified executable examples or claiming that the catalog runs compatibility tests. No tool entries or license classifications change; no vendor affiliation is asserted by this change.
Validation:
npm ci --ignore-scriptsandnpm run lintpassed on Node.js 24. The changed selection guide also parsed as GitHub-flavored Markdown, with consistent columns in all 14 tables. No emulator or real-cloud integration tests were run; this PR adds documentation only.Checklist
npm run lint.