Add governance signal hooks and priority-sort utilities

[Stanys-dev]

What this adds

Foundation layer for upcoming governance UX improvements: batch on-chain vote-status reads, active/pending proposal signals, client-side priority sorting, and GraphQL pre-sort for priority-desc. No visible UI change in this PR.

Why

Follow-up PRs will show vote badges, priority-sorted proposal lists, and sidebar urgency signals. Those features need shared hooks and pure sort/time helpers first, kept separate from UI so reviewers can validate data logic independently.

Changes

• hooks/useGovernorHasVotedBatch.ts — batch hasVoted reads via wagmi useReadContracts
• hooks/useActiveProposalNotVotedForWallet.ts — derives not-voted count from the batch map
• hooks/useProposalGovernanceSignals.ts — TanStack Query hook for active/pending counts, next end time, and active proposal IDs
• lib/sortProposalsByPriorityDesc.ts — client priority sort (active + not voted first, soonest end within tier 0)
• lib/utils.ts — formatCompactTimeLeft() for compact urgency labels
• types/index.ts — add priority-desc to ProposalSortOption
• graphqlApi/index.ts — map priority-desc to server end_time asc pre-sort
• vitest.config.ts + unit tests for sort and time helpers; npm test script

Scope

12 files. Hooks and lib only — no component or page changes. No contract changes.

Verification

• Ran npm run test — 7 tests pass
• Ran npm run build — compiles cleanly
• npm run lint fails with a pre-existing ESLint config error on this repo (circular structure in flat config); not introduced by this PR

Test plan (for reviewer)

• npm run test passes
• npm run build / Vercel preview succeeds
• No runtime/UI change expected — this is a data-layer-only PR

Made with Cursor

[vercel]

Someone is attempting to deploy a commit to the Lightchain AI Team on Vercel.

A member of the Team first needs to authorize it.