[Bug] Pending update removes an active published policy from published count

[filipenevola]

Summary

Submitting a new policy version for approval removes the policy from the platform's Published count even though the previous version remains active and explicitly marked Published.

Reproduction

1. Start with a policy whose current version (v1) is published.
2. Create a new draft version (v2).
3. Submit v2 for approval.
4. Inspect the policy's Version History and the organization Policies/Overview aggregates.

Observed

• Version History shows v1 Published and v2 Pending Approval.
• The policy header is Needs Review.
• The policy aggregate changes from 25 Published / 0 Needs Review to 24 Published / 1 Needs Review.
• The overview changes from 25/25 policies published to 24/25.

Expected

The policy should remain counted as published while its active v1 is published. A separate pending-review indicator can show that v2 needs approval. The published count should change only if there is no active published version.

Impact

This understates readiness during normal policy revision workflows and makes the overview disagree with Version History. It may also discourage use of the approval workflow because submitting a revision immediately lowers the published-policy metric before the revision is approved.

No organization identifiers, policy identifiers, or policy content are included in this report.