[EPIC] Engineering quality gates & developer experience

[joelpeace48-cell]

Epic / consolidation. Merges engineering quality-gate + DX tasks into one high-priority initiative. Supersedes #617, #630, #631, #638, #639, #640.

Why this matters (velocity = growth)

A growing project lives or dies by contributor velocity and release confidence. Strong automated gates let 40+ contributors ship fast without breaking the platform, and good DX attracts and retains contributors. This bundles the quality/DX work that compounds across every future PR.

Goal

Establish automated quality gates and developer-experience tooling so changes are safe-by-default and the codebase scales with its contributor base.

Scope (merged work items)

• Coverage gates + trend — per-package coverage thresholds (JS + Rust) that fail CI below target; PR comment with delta; ratchet policy. (was test: Coverage gates + PR trend reporting #639)
• API contract tests — validate live responses against openapi.yaml in CI (success + error shapes); fail on drift. (was test: Backend response contract tests against OpenAPI spec #638)
• Deterministic test factories/seeders — shared, seeded factories for campaigns/participants/keys + DB/devnet seed scripts. (was test: Deterministic test-data factories & seeders #640)
• Bundle budget + code splitting — size budgets + route-level lazy loading (esp. heavy/ZK chunks); CI fails on regression. (was feat: Bundle-size budget & route-level code splitting in CI #631)
• URL-synced filter/sort/search — shareable, restorable list state via query params. (was feat: URL-synced search, filter & sort state #630)
• Auto-published contract bindings — versioned @trivela/contract-bindings published on release tags, ABI/WASM-hash/contract-IDs in metadata. (was feat: Auto-publish versioned contract TypeScript bindings on release #617)

Acceptance criteria

• Coverage drop, OpenAPI mismatch, or bundle-budget regression each fail CI.
• Tests use shared deterministic factories; list views are shareable via URL.
• A release publishes consumable bindings matching the deployed ABI.

Verification

• CI gates (coverage/contract/bundle) with deliberate-break tests; release dry-run for bindings; E2E restore-from-URL.

Priority: high · Difficulty: hard · Effort: M–L

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!