feat(nexus): paginate the Nexus Links tables (FE-1106)

[rossedfort]

Description & motivation 💭

The CHASM migration raises the number of Nexus links a workflow can have from 30 to 2000. The Nexus Links tab drew both tables as plain Tables, so all of those rows would render at once. Both tables now use the client-side Paginated table already used on the deployment and Nexus endpoint pages. Link order is unchanged, and page sizes stay at the standard 100/250/500/1000, so anything up to 100 links still fits on one page.

Paginated kept its state in fixed page and per-page URL params. Two of them on one page would read the same params, so paging Outbound would also page Inbound, and both page-size selects would get the same DOM id. Paginated now takes optional pageParameter and perPageParameter props. They default to the existing keys, so current pages behave as before. The Nexus Links tables use inbound-page / inbound-per-page and outbound-page / outbound-per-page.

Also fixed: both tables' screen-reader captions said "Workers" (a copy-paste leftover). The captions and the Inbound/Outbound headings now come from i18n strings.

Testing 🧪

How was this tested 👻

• Manual testing
• E2E tests added
• Unit tests added

Added paginated.svelte.test.ts cases for a custom page param (?inbound-page=3&page=1 renders page 3) and a custom page-size param.

Steps for others to test: 🚶🏽‍♂️🚶🏽‍♀️

1. Open a workflow with more than 100 Nexus operations (inbound or outbound) and go to the Nexus Links tab.
2. Page through one table and confirm the other table stays where it was.
3. Change the page size on each table and confirm the URL params are separate.
4. Load ?outbound-page=99 and confirm it jumps back to the last page.

Issue(s) closed

FE-1106

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
holocene	Ready	Preview	Oct 15, 2026 5:31pm UTC

[KATIETOLER]

All the testing flows worked well, looks good to me!