Skip to content

Clarify POS validation and resolution contracts - #4683

Draft
vctrchu wants to merge 1 commit into
2026-10-rcfrom
vctrchu/pos-intercept-doc-types
Draft

vctrchu wants to merge 1 commit into
2026-10-rcfrom
vctrchu/pos-intercept-doc-types

Conversation

@vctrchu

@vctrchu vctrchu commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • clarify cash-payment event amounts and empty interceptor result behavior
  • document observable ERROR and WARNING severity semantics without unsupported permission claims
  • align validation-resolution component types with the 2026-10 POS runtime by excluding Route, Router, and receipt-only QrCode
  • clarify resolution revalidation updates

Validation

  • yarn lint
  • yarn type-check
  • yarn test packages/ui-extensions-tester/src/tests/pos-resolution-targets.test.ts (6 tests)
  • consumer type smoke check for ResolutionComponents
  • GitHub CI: lint, test, test-build, and type-check passed

No runtime API behavior changes.

@vctrchu
vctrchu force-pushed the vctrchu/pos-intercept-doc-types branch 3 times, most recently from 12c1abd to 379df1a Compare September 10, 2026 23:14
@vctrchu vctrchu changed the title Clarify POS validation intercept contracts Clarify POS validation and resolution contracts Sep 10, 2026
@vctrchu
vctrchu marked this pull request as draft September 10, 2026 23:31
@vctrchu
vctrchu force-pushed the vctrchu/pos-intercept-doc-types branch from 379df1a to 105e17d Compare September 10, 2026 23:36
@vctrchu
vctrchu force-pushed the vctrchu/pos-intercept-doc-types branch from 105e17d to ed004a0 Compare September 11, 2026 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant