Skip to content

fix(search): expose shop payment readiness independently of stock - #58

Merged
ilyar merged 8 commits into
mainfrom
jon/readiness-integration-19
Nov 10, 2026
Merged

ilyar merged 8 commits into
mainfrom
jon/readiness-integration-19

Conversation

@ilyar

@ilyar ilyar commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Search results showed stock availability even when the shop could not accept payment. This adds paymentReady and paymentUnavailableReason using the same route and sender checks as checkout, so assistants can explain why payment is unavailable before offering it

Stock availability, ranking, filters, prices and demand tracking retain their existing meaning. Payment and booking tools remain authoritative and recheck readiness before writing

The candidate also includes receipt and Catalog acceptance tests, review-state transition tests, and a cleanup-only timeout for disposable test databases. It does not diagnose the disputed production order or claim verified production webhook receipts

Rebased on 234f6abd92664fbcbdcbf7811e476a98d93df143, preserving the new homepage and seller assistant screens. Only CHANGELOG conflicted, both upstream entries and the readiness entry are retained. The seven implementation and test commits remain patch-identical to the previously reviewed candidate

Validation and delivery results are recorded in the latest progress comments. Integration is fast-forward only, without a merge commit

Refs: #5, #19

Runs the platform webhook handler against a migrated database and checks the
read-only receipts aggregate for each delivery outcome.

Refs: #19
Covers when a platform shop's published products are not_configured,
pending, synced or failed, and what plain sync and retries do to rows
published before the connection was ready.

Refs: #19
The handler matches an event to its order by PayPal order id; whether a
receipt naming another capture should end processed is not a requirement.
The evidence query already excludes it.

Refs: #19
DROP DATABASE waits for a checkpoint; with many parallel workers on a local
disk its sync exceeded the default 10 s hook timeout. Only this hook changes.

Refs: #19
@ilyar

ilyar commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator Author

The user has requested completion and a fast-forward integration of this candidate

  • The previous candidate passed GitHub lint, the full test suite and production build
  • Rebase onto current main, preserving the newer seller UI and documentation
  • Check the rebased result locally and in PR CI
  • Fast-forward main without a merge commit, then verify delivery of the resulting SHA

@ppmarkek Integration is in progress, the original scoped search contract remains unchanged, there is no request to pause unrelated work
Production order diagnostics are separate and do not block this fix

Document the search readiness snapshot and its limits for buyer assistants.

Refs: #19
@ilyar
ilyar force-pushed the jon/readiness-integration-19 branch from 010e52d to a8530bc Compare November 10, 2026 20:30
@ilyar
ilyar marked this pull request as ready for review November 10, 2026 20:30
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-10T20:30:44.376590Z
We couldn’t complete this review. Comment @codex review to try again.
a8530bc Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@ilyar

ilyar commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator Author

Rebased candidate: a8530bc, based on current main 234f6ab

  • Preserved both new upstream UI changes, only CHANGELOG required conflict resolution
  • Range-diff confirms seven implementation/test commits are patch-identical
  • Local lint, diff check and full standard PostgreSQL 17 suite: 107 files, 1,894 tests
  • Draft status removed
  • Rebased production build in CI, local Turbopack was blocked by EPERM when creating a process/port
  • Fast-forward main and verify the exact deployed SHA

No payment, production SQL or infrastructure configuration was changed

@ilyar
ilyar merged commit a8530bc into main Nov 10, 2026
2 checks passed
@ilyar

ilyar commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator Author

Fast-forward integration completed: main advanced from 234f6ab to a8530bc, with no merge commit

  • Rebased onto current main and preserved both upstream UI changes
  • Local lint and standard PostgreSQL suite: 1,894 tests
  • Rebased PR CI: lint, full tests and production build passed
  • Fast-forward main, PR marked MERGED by GitHub
  • Main CI and Render delivery
  • Exact-SHA live health/readiness and MCP search readiness fields

Production order diagnosis and uninspected receipts remain separate open evidence, this integration does not close #19

@ilyar
ilyar temporarily deployed to agentshelf-e5bk.onrender.com November 10, 2026 20:38 — with GitHub Actions Inactive
@ilyar

ilyar commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator Author

PR #58 is integrated and deployed: a8530bc, fast-forward from 234f6ab, no merge commit

  • Latest main preserved, CHANGELOG conflict resolved without dropping either upstream entry
  • Local lint and full PostgreSQL 17 suite: 1,894 tests across 107 files
  • PR CI and main CI + delivery passed, including production build
  • Render deploy dep-dbpo1kugekts73ekhe70 is live on the same SHA
  • Independent public home, health and readiness checks passed at 20:41 UTC on 10 November
  • Live MCP tools/list and search_products confirmed the description and additive fields: 6 results, 4 payment-ready and 2 not_connected
  • Liepāja Phone Workshop reports paymentReady=true, Demo Phone Workshop reports false/not_connected, independently of availability
  • No private routing columns leaked into search results, no order, booking or payment was created by this verification

@ppmarkek The scoped search candidate is now on main and live, the temporary one-writer reservation for catalog.ts and the search contract is finished

This closes the readiness integration, not the remaining #19 evidence work: disputed-order diagnosis, production receipts and Catalog findings are separate

This branch was previously deployed

1 inactive deployment
agentshelf-e5bk.onrender.com — a8530bc6 Deployed Nov 10, 2026 by ilyar via deploy-render #98
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