Repository navigation
Fix: [Docs] - Add Docs Site MDX Page for Escrow Dispute Flow - #587
Open
VeronicDev wants to merge 1 commit into
Open
VeronicDev wants to merge 1 commit into
VeronicDev 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
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.
Closes #527
Changes
Created a dedicated MDX documentation page explaining the escrow dispute flow, arbitration process, timelock windows, and roles of buyer, seller, and arbitrator with a sequence diagram, and linked it in apps/docs-site/pages/_meta.json.
Verification
✅ The repository's own CI was run on this branch (on the contributor's fork) before opening this PR: every check passed except
Frontend CI,Frontend (Next.js),Server (TypeScript),Server quality gates,Playwright— they fail onmainwithout this change too (the same CI run on the untouched base commit a1c0b97), so they aren't caused by this PR. The change is within the issue's scope.