v0.3.5 — Read-Only Customer Service Tools - #18
Merged
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.
Product impact
Adds one bounded customer-service workflow: a customer verifies one Demo order in the current chat and receives a deterministic, transient order and shipping status. Refunds, cancellation, address changes, notifications, and all other writes remain unsupported and route safely to policy or human support.
Implementation scope
Verification
Remaining risks and boundaries
The included data is fictional Demo data only. userIdent is anonymous session ownership, not durable customer identity. Verification limits and SQLite coordination are deployment-local. There is no real OMS/carrier integration, polling, notification, order history, or write authority. Merge, annotated tag, and GitHub Release remain separate publication gates.