docs: route-overlap warning on Dispute resolve, fix RN docs URL

03 - API Reference/Dispute API.md

@@ -10,6 +10,9 @@ tags: [api, dispute, reference]
 
 Endpoints live under `/api/disputes/*`. `backend/src/routes/disputeRoutes.ts` delegates to `DisputeController` (`backend/src/controllers/disputeController.ts`) for CRUD/triage. `backend/src/services/dispute/disputeRoutes.ts` provides lightweight release-hold endpoints (`raise`, `resolve`, `status`) used by escrow release gating. The routers apply `authenticateToken` globally — every endpoint requires `Bearer JWT`.
 
+> [!warning] Route overlap to verify
+> Both route modules define a `POST /:id-or-purchaseRequestId/resolve` shape. Because `app.ts` mounts the full controller router before the lightweight hold router, confirm the intended handler before wiring automation to the lightweight resolve endpoint.
+
 Model: [[Dispute]]. A dispute references a [[PurchaseRequest]] plus optional [[Payment]] context and is the input to the mediation workflow that can lead to refund, replacement, compensation, warning/ban, or no-action. Release/refund execution should go through the ledger-gated [[Payment API]] and [[Payout Flow]].
 
 ## Create

PRD - Decentralized Custody and Smart-Contract Escrow Roadmap.md

@@ -192,4 +192,4 @@ This roadmap was created together with a focused documentation alignment pass:
 
 - Safe threshold custody model: <https://docs.safe.global/advanced/smart-account-concepts>
 - OpenZeppelin AccessManager and timelock guidance: <https://docs.openzeppelin.com/contracts/5.x/access-control>
-- Request Network payment contracts overview: <https://docs.request.network/advanced/protocol-overview/contracts>
+- Request Network payment contracts overview: <https://docs.request.network/get-started/protocol-overview/contracts>