Repository navigation
Run message comparisons with purchase and resume support - #61
Merged
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
1 participant
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.
Agents running a two-message comparison need to preserve the reviewed Study and purchase while the buyer completes checkout. This adds a runnable workflow and shared-client orchestration that prepares a private Study, requires exact draft confirmation, reuses a saved hosted checkout, and resumes the same research after the server accepts access.
The existing billing catalog, Stripe Checkout adapter, ACP session readback, MCP research services and webhook entitlement rules remain the runtime authority. Stable keys and private checkpoints preserve retries across process restarts. Pending/canceled checkout and incomplete research cannot produce a completed report. Buyer approval and subscription legal acceptance are explicit; no prices or allowances are introduced.
Validation: 27 shared-client tests, including a CLI journey across separate processes with simulated payment; TypeScript compilation; 20 Slack regression tests; CLI syntax and diff checks. Read-only production checks verified account authentication, billing catalog, MCP discovery and all five required research tools. Real card payment, webhook activation, actual research execution and assistant-host acceptance were not performed in this change; the dated verification record lists these limits.
Guide:
docs/message-comparison.md. Entry point:examples/message-comparison.mjs.