Skip to content

feat(web): show proposal discovery freshness and indexing limitations - #281

Merged
Caneryy merged 2 commits into
stolla-labs:mainfrom
sasasamaes:feat/proposal-discovery-freshness
Aug 30, 2026
Merged

feat(web): show proposal discovery freshness and indexing limitations#281
Caneryy merged 2 commits into
stolla-labs:mainfrom
sasasamaes:feat/proposal-discovery-freshness

Conversation

@sasasamaes

Copy link
Copy Markdown
Contributor

Summary

Implement PRD §5.1 freshness states (Current, Delayed, Stale, Unavailable) derived from RPC event scan metadata. Users can now distinguish complete history from incomplete responses on community and global proposal lists.

Linked issue

Closes #264

Test plan

  • Unit tests: 23 tests covering all 4 freshness states and malformed RPC metadata edge cases
  • Proposal discovery mock updated and passing
  • Manual: community proposal list shows freshness banner when scan is behind network head
  • Manual: global proposal list shows freshness banner with retry preserving filters
  • npm run lint — no new errors introduced
  • npm run typecheck — no new errors introduced

Checklist

  • I have run npm run lint and fixed any warnings introduced by my changes (pre-existing warnings are acceptable).
  • I have run npm run build and it completes successfully.
  • My changes do not introduce new environment variables, secrets, or generated files.
  • UI changes include screenshots at mobile and desktop widths.

Implement PRD §5.1 freshness states (Current, Delayed, Stale, Unavailable)
derived from RPC event scan metadata. Users can now distinguish complete
history from incomplete responses on community and global proposal lists.

- Add evaluateDiscoveryFreshness() pure function with ledger gap thresholds
- Track latestLedger, lastEventLedger, and per-page errors in useProposalDiscovery
- Add DiscoveryFreshnessBanner component with retry and docs link
- Wire banner into /communities/[id]/proposals and /proposals pages
- Unit tests cover all 4 states and malformed RPC metadata edge cases

Closes stolla-labs#264
@vercel

vercel Bot commented Aug 26, 2026

Copy link
Copy Markdown

@sasasamaes is attempting to deploy a commit to the caneryy's projects Team on Vercel.

A member of the Team first needs to authorize it.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Caneryy
Caneryy merged commit 312cb75 into stolla-labs:main Aug 30, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Show proposal discovery freshness and indexing limitations

2 participants