perf(exec): parallelize dyad_census on ComputePool (#570)

[DecisionNerd]

Implements #570: parallel dyad_census on ComputePool.

Closes #570

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Parallelize dyad census category counting on a ComputePool

• Adds parallel execution for the dyad census category-counting phase when compute_threads > 1, a parallel compute pool is available, and present dyad count is ≥ DYAD_CENSUS_PARALLEL_CROSSOVER_PAIRS (32,768).
• Introduces select_dyad_census_path to choose between Serial and Parallel { threads, chunks } execution modes, and separate count_dyads_serial / count_dyads_parallel helpers that implement each path.
• Parallel work runs on the instance-owned Rayon pool via run_on_pool, which catches worker panics and returns a structured AlgorithmError instead of unwinding.
• Adds dyad_chunks to split work into contiguous ranges across threads, with chunk-local DyadCounts merged after pool completion.
• Risk: parallel path requires an instance-owned compute pool; if none is present at runtime, count_dyads_parallel returns an error.

^{Macroscope summarized 8d47e8b.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4f83fb3e-e74c-4226-81cb-fc5e4690f99f

📥 Commits

Reviewing files that changed from the base of the PR and between c9ea4ad and 8d47e8b.

⛔ Files ignored due to path filters (1)

• docs/development/execution-resource-policy.md is excluded by !**/*.md, !**/docs/**

📒 Files selected for processing (2)

• crates/graphforge-exec/src/algorithm_analyze.rs
• crates/graphforge-exec/src/algorithm_analyze_dyad_census.rs

---

_{Comment @coderabbitai help to get the list of available commands.}