🐛 Outcomes: Total number of CC members displayed incorrectly

[bosko-m]

Area

Other

Domain

gov.tools

Which wallet were you using?

No response

Context

In the Outcomes section, the total number of CC members displayed appears incorrect. The count should reflect either:

• the current enacted committee (post-epoch boundary), or
• a historically accurate committee size for the time relevant to the displayed outcome (e.g., at enactment).

Note: A GA changing the CC is expected to be enacted at the epoch boundary on Saturday evening, 6 September 2025; after that, “current” displays should reflect the new committee size.

Steps to reproduce

1. Open the Outcomes section.
2. View multiple governance action outcomes that reference CC membership.
3. Compare the displayed total CC member count against the expected value (current enacted committee or historical, depending on design).

Actual behavior

• The total CC member count in Outcomes is incorrect (does not match the enacted committee size appropriate for the display context).

Expected behavior

• If Outcomes is meant to show current status: display the current enacted CC size (updated after the epoch boundary).
• If Outcomes is meant to show historical status: display the committee size accurate to the outcome’s effective time (e.g., at enactment or ratification), and apply this consistently across all outcomes.

Notes

• Confirm intended UX: current vs historical CC size in Outcomes, then implement consistently.
• Check joins against committee tables and effective/expiration epoch logic; ensure you’re selecting the correct snapshot (e.g., DISTINCT ON with ORDER BY expiration_epoch DESC may need tightening).
• Review any client caching and server pagination that could mix snapshots.