Query Pagination Next: Add border and spacing support - #66394

Thanks for the PR @karthick-murugan 👍

I've taken this for a spin on a local rebase onto trunk, testing borders and padding through Global Styles, a block instance value, and both again at different viewports, with and without enhanced pagination.

✅ Border and Padding work in the editor and on the frontend
✅ A block instance value overrides Global Styles

Before we merge this though I think there are a few things to address. #66393 has the same shape, so these apply there too.

Rebase

docs/reference-guides/core-blocks.md has since moved to docs/reference-guides/core-blocks/README.md. Running npm run docs:build after the rebase will regenerate it and the block's own README.md.

Margin support

• A block instance left margin replaces the margin-inline-start: auto that positions this link for "Space between", so the Next link jumps to the left edge
• A margin set in Global Styles never applies, because the flex layout resets child margins with .is-layout-flex > :is(*, div) { margin: 0 }
• That reset wins over the :root :where(...) that Global Styles outputs

Padding is ok. The space between pagination links belongs to the container. core/buttons, core/social-links and core/navigation all put blockGap on the parent and keep margin off the children. core/button itself only adopts padding and border.

Query Pagination has no blockGap support yet but I will raise a PR for that separately.

Border controls shown by default

Recent border adoptions like Home Link and Post Navigation Link keep the border controls hidden by default. Setting __experimentalDefaultControls to false here would match them.

Box sizing

It'd be worth adding a style.scss with box-sizing: border-box while you're here, as Comment Edit Link and Post Navigation Link do.

Border screenshots

Padding screenshots