docs(drift): draft from internal source

[pedromcunha]

Drafted from an internal source repo, requested by @alexanderattar.

This PR was auto-generated by the reusable-docs-draft-pr workflow from a Claude-drafted update in the source repo. It is opened as a draft — please review, edit as needed, and mark ready for review before merging.

Review checklist

• Content matches the behavior shipped in the source PR
• No internal-only details (service names, file paths, unreleased names, security internals) leaked into the draft
• Conforms to CLAUDE.md style rules
• Cross-references and internal links resolve
• Any Needs human input items from the source comment are addressed

---

Generated by reusable-docs-draft-pr.yml in relayprotocol/agents-config.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
unevenlabs	🟢 Ready	View Preview	Jul 30, 2026, 5:14 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

Claude finished @pedromcunha's task in 1m 15s —— View job

---

Code review — references/api/changelog.mdx

• Read PR diff
• Verify changelog claims & cross-links
• Check AGENTS.md style conformance
• Post review

Verdict: looks good to merge. No blocking issues. One clarification worth a look before you mark it ready.

What I verified

Check	Result
Field name for v3 (txHash, not hash)	✅ matches api_guides/migrating-to-requests-v3.mdx:444,491 — inTxs[].hash → inTxs[].txHash in v3
Link /references/api/get-requests-v2	✅ resolves (references/api/get-requests-v2.mdx, openapi: get /requests/v2)
Cross-reference to the 2026-06-19 v2 entry	✅ that entry exists at references/api/changelog.mdx:75 and describes the same fix
Newest-first ordering (§4.5)	✅ 2026-07-30 sits between 2026-08-03 and 2026-07-28
Entry format (## <date> — <summary> + bolded change-type lead)	✅ **Behavior change** matches established precedent in this file
No internal-only detail leaked	✅ no service names, repo paths, or internal component names
Anchor slug collision with the other 2026-07-30 entry	✅ headings differ, so Mintlify slugs differ

Minor — timeline may confuse readers

references/api/changelog.mdx:38 says the fix "mirrors the fix previously shipped for GET /requests/v2 on 2026-06-19", but per changelog.mdx:56-58 v3 only went live on 2026-07-22 — a month after the v2 fix. As written, a reader can't tell whether v3 shipped with the old composite identifier for its first 8 days, or whether this covers some earlier preview period. Worth a one-clause tightening, e.g.:

data.inTxs[].txHash … Previously this field returned an internal composite identifier that had to be parsed before it could be linked to an explorer — GET /requests/v3 shipped with the pre-fix behavior even though the equivalent GET /requests/v2 fix landed on 2026-06-19.

Only worth doing if that's actually what happened — confirm against the source PR. Fix this →

Nit — paragraph length (§2.10)

The entry is one 4-sentence paragraph, over the 2–3 sentence cap in AGENTS.md §2.10. Existing entries in this file run the same length (changelog.mdx:30,34), so this is consistent with local precedent — flagging only so the choice is deliberate. No change needed.

Companion surfaces — none needed

The 2026-06-19 v2 entry paired with a GET /chains explorerPaths.transaction addition; that's already documented and unchanged, so nothing else to update. No TON guide page or SDK page documents the inTxs[].txHash format, so no inbound links go stale.
· branch docs-drift/src-80d009e420-e9009cd