perf(exec): serial disposition for minimum_k_spanning_tree (#581)

[DecisionNerd]

Implements #581: serial disposition for minimum_k_spanning_tree.

Closes #581

  

---

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

Note

Add serial disposition for minimum_k_spanning_tree to the M4 baseline harness

• Adds a new run_analyze_minimum_k_spanning_tree workload to the M4 entry baseline that calls GraphForge::analyze with MinimumKSpanningTree, verifies determinism, and records timing, memory, and a result fingerprint.
• Documents that minimum_k_spanning_tree runs serially across all compute_threads policies due to contention on shared top-k state in execution-resource-policy.md.
• Registers analyze-minimum-k-spanning-tree in the CI matrix validation set and the m4-entry-matrix.json contract with gates for schema, row count, ordering, fingerprint, CSR projection, bounded Arrow sink, and serial disposition.

^{Macroscope summarized f5580ca.}

[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: 38 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: b77c96f3-9521-4129-98e2-28b671994c74

📥 Commits

Reviewing files that changed from the base of the PR and between 5fb870f and f5580ca.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• crates/graphforge-api/tests/m4_entry_baseline.rs
• crates/graphforge-exec/src/algorithm_analyze_minimum_k_spanning_tree.rs
• scripts/ci/m4-entry-matrix.py
• tests/contracts/m4-entry-matrix.json

---

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