Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(subscriptions): handle SET_PROCESS_CENSUS payload; clarify limit zero-semantics

Second Copilot round:

- HasTxPermission grouped SET_PROCESS_CENSUS with NEW_PROCESS and read the tx
  via GetNewProcess(). A SET_PROCESS_CENSUS tx carries a SetProcess payload, so
  GetNewProcess() is nil and dereferencing newProcess.Process panicked (the
  prior round's move of the census check out of the managed guard made this
  reachable for all orgs). Split the case: NEW_PROCESS keeps its checks behind a
  nil-guard; SET_PROCESS_CENSUS reads GetSetProcess() and bounds GetCensusSize()
  against the governing plan's MaxCensus. Adds unit coverage for both the
  in-bounds (allowed) and over-cap (rejected) managed census-update paths.

- apicommon.IntegratorLimits doc: 0 is not uniformly 'unlimited'. Only MaxVotes
  treats 0 as unlimited; MaxManagedProcesses/MaxSMS/MaxEmails are hard caps where
  0 means no allowance. Clarified, and noted the distinct 'unknown' 0 when an
  override-enabled integrator has no plan.