ci: unified workflow (lint + typecheck + build + rust)

[kyscott18]

Replaces .github/workflows/lint.yml with a unified .github/workflows/ci.yml running four jobs:

• lint — Biome 2.1.2 (biome ci)
• typecheck — tsc --noEmit (frontend)
• build — next build (frontend)
• rust — cargo fmt --check, cargo clippy -D warnings, cargo build (backend workspace)

Notes:

• lint.yml is removed; its Biome job is rolled into ci.yml.
• The existing publish-backend.yml (Docker image publish) is unchanged — this adds build/lint CI for Rust, not publishing.
• The rust job runs in the rust:1.91-slim container (matching the backend Dockerfile) so bindgen's libclang is new enough for the upstream C23 headers from monad-bft. Cargo build is cached via Swatinem/rust-cache.
• All jobs are workflow_dispatch-able from the Actions tab (also run on pull_request and pushes to main).

Also adds a typecheck script (tsc --noEmit) to frontend/package.json.

⚠️ Known-red check: rust (clippy)

cargo fmt --check and cargo build pass. cargo clippy -D warnings currently fails on 8 pre-existing lint issues in backend/ (this code was never clippy-checked — publish-backend.yml only builds). We are keeping strict -D warnings and fixing those findings in a separate follow-up PR; the rust check here is expected red until then. Findings: large_enum_variant, needless_return, match_like_matches_macro, should_implement_trait (from_str), ptr_arg, clone_on_copy, manual_is_multiple_of, needless_borrow.

Follow-ups (separate PRs)

1. Fix the 8 backend clippy findings so the rust job goes green.
2. Unify the two pnpm projects (root + frontend/) into a single root pnpm workspace with root orchestration scripts — deferred because it needs coordinated Vercel deploy-settings changes.

Stacked on #99 for the pnpm lockfile fix; rebase base back to main once #99 merges.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
monode	Ready	Preview, Comment	Jun 11, 2026 9:05am

[greptile-apps]

Greptile Summary

This PR consolidates CI into a single unified ci.yml workflow (replacing lint.yml) with four parallel jobs — Biome lint, TypeScript typecheck, Next.js build, and a Rust job covering fmt/clippy/build — and also ships several frontend and backend improvements found while wiring up the checks.

• CI: New ci.yml runs lint, typecheck, build, and Rust checks on pull_request, push to main, and workflow_dispatch; the Rust job runs inside rust:1.91-slim to match the backend Dockerfile's libclang requirements, with Swatinem/rust-cache for build caching.
• Frontend: events-context gains per-subscriber event-type filtering and background-tab message dropping; use-block-execution-tracker is refactored to a ref-based inflight-block map for O(1) transaction updates; tps-chart adds a rAF-driven sliding window with progressive segment animation.
• Backend: Eight pre-existing Clippy warnings are resolved (large_enum_variant, needless_return, match_like_matches_macro, should_implement_trait, ptr_arg, clone_on_copy, manual_is_multiple_of, needless_borrow).

Confidence Score: 5/5

Safe to merge — the CI wiring is correct, the Rust clippy fixes are mechanical and verified, and the frontend refactors are well-structured with no logic regressions.

The workflow change is additive and mirrors the existing lint job patterns. The Rust changes fix all 8 listed clippy warnings correctly. The frontend changes (inflight-block ref map, event-type filtering, sliding TPS chart) are logically sound. The only issue is a team style-rule violation on one useRef call, which has no runtime impact.

frontend/hooks/use-block-execution-tracker.ts — contains the useRef style-rule violation; all other files look clean.

Important Files Changed

Filename	Overview
.github/workflows/ci.yml	New unified CI workflow — lint, typecheck, build, and Rust jobs are correctly structured; Rust job installs git before checkout and uses appropriate rust:1.91-slim container with rust-cache.
frontend/hooks/use-block-execution-tracker.ts	Major O(N²) → O(1) refactor using a ref-based inflight map; logic is sound, but useRef<number
frontend/contexts/events-context.tsx	Adds per-subscriber event-type filtering via ReadonlySet, background-tab message dropping, and useMemo on the context value — all look correct.
frontend/components/network-activity-tracker/tps-chart.tsx	Adds rAF-driven sliding window and progressive segment animation via useSlidingNow/drawHistory/buildTicks; intentional 60fps re-renders for smooth chart scrolling, rAF naturally pauses in hidden tabs.
backend/src/lib/server.rs	Boxes EventData in the enum variant to fix large_enum_variant; removes needless return and rewrites match-as-bool with matches!(); all changes are safe mechanical clippy fixes.
backend/src/lib/event_listener.rs	Renames from_str to from_name (avoids should_implement_trait warning) and replaces % 100 == 0 with is_multiple_of(100); both are correct clippy-driven cleanups.
backend/src/lib/event_filter.rs	Changes &Vec to &[T] (ptr_arg fix) and removes a redundant borrow on is_native_transfer (needless_borrow fix); both are correct and safe.
backend/src/bin/client.rs	Removes redundant as u64 casts from u64 timestamp subtractions; correct since both operands are already u64.
backend/src/lib/serializable_event.rs	Removes .clone() on a Copy type (clone_on_copy fix); trivially correct.
frontend/hooks/use-events.ts	Threads eventTypes through to subscribe(); all callers use module-level constants so the dep-array reference is stable — no spurious re-subscriptions.
frontend/hooks/use-block-state-tracker.ts	Adds BLOCK_STATE_EVENT_TYPES module-level constant and passes it to useEvents for filtered delivery; no logic changes.
frontend/hooks/use-swap-events.ts	Adds SWAP_EVENT_TYPES = ['TxnLog'] filter; hook already only cared about TxnLog events so this is a correct narrowing with no behaviour change.
frontend/hooks/use-total-transactions.ts	Adds TXN_HEADER_EVENT_TYPES = ['TxnHeaderStart'] filter; narrows subscription to the only event type the hook processes.
frontend/hooks/use-transfer-events.ts	Adds TRANSFER_EVENT_TYPES = ['TxnCallFrame', 'TxnLog'] filter matching what the hook already handled.
frontend/package.json	Adds typecheck script (tsc --noEmit) needed by the new CI typecheck job.
frontend/pnpm-lock.yaml	Removes duplicate entries introduced by the prior lockfile merge conflict; lockfile is now clean.
frontend/pnpm-workspace.yaml	Adds allowBuilds for sharp and unrs-resolver to allow postinstall scripts for those native packages.

Sequence Diagram

sequenceDiagram
    participant WS as WebSocket
    participant EC as EventsContext
    participant UE as useEvents (hook)
    participant H as Consumer Hook

    WS->>EC: onmessage(raw)
    Note over EC: Drop if visibilityState === hidden
    EC->>EC: JSON.parse → ServerMessage
    loop for each event in Events[]
        EC->>EC: "eventType = evt.payload.type"
        loop for each Subscriber
            alt "sub.eventTypes === null OR has(eventType)"
                EC->>UE: callback(evt)
                UE->>H: onEventRef.current(evt)
            else filtered out
                EC-->>EC: skip
            end
        end
    end
    Note over UE: Subscribes with stable module-level eventTypes[] constant

Loading

_{Reviews (6): Last reviewed commit: "fix(backend): resolve clippy lints (#101..." | Re-trigger Greptile}

[greptile-apps]

next build runs without required env vars

frontend/config/env.ts exposes NEXT_PUBLIC_EVENTS_WS_URL via getEnvOrThrow, which throws if the variable is unset. While the getter is lazy and won't fire during the webpack compile pass itself, any page that calls publicEnv.EVENTS_WS_URL during server-side rendering or static generation will cause next build to throw and fail the job. Consider adding an env: block (using GitHub Actions secrets) or providing dummy values so the build job gives reliable signal rather than potentially failing for a config reason instead of a code reason.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/ci.yml
Line: 43-57

Comment:
**`next build` runs without required env vars**

`frontend/config/env.ts` exposes `NEXT_PUBLIC_EVENTS_WS_URL` via `getEnvOrThrow`, which throws if the variable is unset. While the getter is lazy and won't fire during the webpack compile pass itself, any page that calls `publicEnv.EVENTS_WS_URL` during server-side rendering or static generation will cause `next build` to throw and fail the job. Consider adding an `env:` block (using GitHub Actions secrets) or providing dummy values so the build job gives reliable signal rather than potentially failing for a config reason instead of a code reason.

How can I resolve this? If you propose a fix, please make it concise.