docs: sync changelog

[github-actions]

Generated by scripts/build-changelog.mjs from the sources described in AGENTS.md section 4.6.

Review the diff, but fix wording in the source an entry came from rather than here — this file is generated, and the branch is rebuilt on every sync, so the diff always shows everything pending since the last merge.

[github-actions]

Claude encountered an error after 2m 21s —— View job

---

Review: docs: sync changelog (#435)

• Gather context (diff, generator, sources)
• Verify generated output against its source
• Check link targets and placement
• Post review

No blocking findings. The diff is +2/−0 in the generated changelog.mdx, and both bullets are faithful renderings of the source entry.

What I verified

Verbatim reproduction (§4.6). Both new bullets in changelog.mdx:87-88 are byte-identical to the **Added** paragraphs of the ## 2026-08-13 — Percentage-based fee sponsorship on POST /quote entry in references/api/changelog.mdx:20 and :22, minus the **Added** — lead. Nothing was hand-edited into the generated page.

Placement matches the generator's rules. The two bullets land in the existing 2026-08-13 <Update> → ### API → **Added** group, ahead of the SOLANA_TX_TOO_LARGE bullet. That is what renderTypeGroups() produces: change types ordered by CHANGE_TYPE_ORDER (Behavior change before Added, as rendered), and items within a group in source-file order — the fee-sponsorship entry precedes the Solana entry in the source. Day tags stay tags={["API"]}, so the ### API section filter still catches the new bullets.

Link target resolves. /features/fee-sponsorship#how-subsidizationbps-works matches ### How \subsidizationBps` Worksatfeatures/fee-sponsorship.mdx:102(Mintlify slug drops the backticks). The prose also agrees with the feature page: swap-only support and400 on bridge/deposit-address flows (features/fee-sponsorship.mdx:117), and maxSubsidizationAmount still capping the total (:50`).

MDX escaping. Neither bullet contains a < or {, so escapeMdx() is a no-op here and there is no risk of a literal backslash rendering.

Notes (non-blocking)

• I could not run node scripts/build-changelog.mjs --check in this environment — it needs a full clone of relay-kit, and the command was not permitted. Determinism was therefore verified by reading the generator and comparing against the sources by hand, as described above. If you want the machine check, it is one --check run on a non-fork branch.
• The head branch carries a manual merge of main (921a1c8) on top of the bot's cb38f5f. Harmless — the PR diff against main is still exactly the two lines — but per .github/workflows/sync-changelog.yml:81-100 the branch is force-rebuilt as main plus one commit, so that merge disappears at the next sync that has new content. Note the early-exit at :91-97 compares only the changelog.mdx blob SHA, so a quiet hour will leave the merge commit sitting there rather than rebuilding the branch. No effect on what gets merged.
• Reminder for future entries, not this one: two source entries share 2026-08-13, so both collapse into one <Update> and any ](#2026-08-13-…) cross-reference is rewritten to the same #2026-08-13 anchor. Existing behavior, no action needed here.
  · branch bot/changelog-sync