Add a participation readiness checklist to community detail

[Caneryy]

Planning

• Plan ID: N5
• Depends on: Introduce a shared community route context for contract-scoped actions #250 (H4), Standardize async states across community and proposal screens #251 (H5)
• PRD alignment: FR-8; UJ-2

Problem

Members must infer whether wallet connection, network, NFT membership, delegation, and Voting Power are ready before they can vote.

Scope

Add a read-only checklist to the canonical Community detail page with direct connect, switch-network, mint, and delegate actions where applicable. Reuse existing hooks and transaction lifecycle components.

Acceptance criteria

• Disconnected, wrong-network, non-member, undelegated, zero-power, ready, loading, and read-error states are distinct.
• Each unmet condition has at most one primary recovery action.
• Successful mint or delegation refreshes the affected rows.
• Component tests cover the full state table without live RPC.

Verification

npm run lint && npm run typecheck && npm test

[bobo-24]

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. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[Iker2522]

I'd like to take this issue on!
​I can implement the voting readiness checklist on the canonical Community detail page as outlined in Plan N5.
​I will build a read-only checklist that distinctly handles disconnected, wrong-network, non-member, undelegated, zero-power, ready, loading, and read-error states, ensuring each unmet requirement provides a single primary recovery action (connect wallet, switch network, mint NFT, delegate). I'll reuse existing hooks and transaction lifecycle components so successful mints or delegations automatically trigger a refresh of the affected rows.

[ZacLou]

I'd like to work on this issue. I'll review the requirements and open a PR shortly.

[ZacLou]

Hi @Caneryy, I'd like to be assigned to this issue so I can resubmit the implementation as a focused PR. I previously opened #289 but understand it was closed because the issue wasn't assigned first—my mistake.

I have already reviewed Plan N5 and the dependencies (#250, #251), and I can implement the readiness checklist on the community detail page reusing the existing hooks and transaction lifecycle components. I will also include component tests covering the full state table without live RPC.

Please assign me if it's still available. Thanks!