test: cover large import batching boundaries

[cursor]

Risky behavior now covered

• A 201-session import is split into exact ordered batches of 100, 100, and 1 row.
• Database upserts run sequentially rather than concurrently.
• The endpoint waits for the final batch before returning and reports all 201 imported sessions.
• Exact batch contents guard against boundary omissions, duplicates, and reordering.

Test files updated

• test/web-import-route.test.ts

Why this reduces regression risk

The recent batching change prevents oversized database payloads and concurrent memory pressure on large local state imports. These assertions fail if batching is removed, batch boundaries drift, writes become concurrent, or the response returns before persistence finishes.

Validation

• npm test — 133 root tests and 5 web tests passed
• npm run build
• npx prettier --check test/web-import-route.test.ts
• Mutation check: replacing the sequential loop with Promise.all made the focused test fail because all three batches started concurrently.

  

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
polyagent	Ready	Preview	Aug 17, 2026 10:09am