🐛 Live Voting: Number of CC members displayed inconsistently across governance actions

[bosko-m]

Area

Voting Pillar

Domain

gov.tools

Which wallet were you using?

No response

Context

In the Live Voting section, the displayed number of Constitutional Committee (CC) members varies between different governance actions, even within the same session. This suggests a mismatch in how the current CC size is derived (e.g., per-item vs global state, caching, or epoch boundary logic).

Note: GA that updates the CC is expected to be enacted at the epoch boundary on Saturday evening, 6 September 2025. After that boundary, the current CC size should reflect the newly enacted committee.

Notes

• Verify the source of truth for CC size (e.g., committee tables / latest enacted snapshot) and ensure it’s not computed per-item with stale or mixed data.
• Check for caching or time boundary issues (epoch start vs wall-clock time / timezone).
• Ensure pending (not yet enacted) committee changes do not affect the displayed “current” count in Live Voting.

Steps to reproduce

1. Open the Live Voting section.
2. Observe the CC members count shown on multiple governance action cards/detail views.
3. Compare counts between items during the same page load/session.

Actual behavior

• Different governance actions show different CC member counts at the same time in Live Voting.

Expected behavior

• Live Voting should show a single, consistent “current CC members” count for all governance actions (unless a GA explicitly requires a historical snapshot, which Live Voting does not).
• After the epoch boundary (6 Sep 2025), the count should update to the new enacted CC size.