test(performance): reconcile M4 exit evidence and scale claims (#345)

[DecisionNerd]

Summary

Final M4 exit evidence reconciliation on tree 2b1bfda after #342–#344. No new optimizations. Documents honest scale dispositions and refreshes the #334 evidence emitter + oversize file-backed proof.

Closes #345.

Changes

• Emit docs/development/m4-exit-evidence.json (graphforge-m4-entry-evidence/1) on the final SHA
• Add docs/development/m4-exit-evidence.md ledger (child PRs, dispositions, reproduction)
• Refresh file-backed-oversize-evidence.json on the final SHA
• Update m4-entry-matrix.json known limitations (CSR/kernels shipped; scale-host blockers; GPU OOS)
• Soft-correct scale-limits.md, entry baseline docs, and benchmark methodology

Honest dispositions

• 8M/128M densified public facade: optional scale-host measurement — not a universal product claim (agent hosts keep sparse >2 GiB oversize proof)
• >200M adjacency RSS: accepted pending scale-host evidence; 134M Arrow boundary no longer governs the public build path
• GPU: out of scope for M4
• threads-8: policy-supported; unavailable on hosts under the machine concurrency budget

Test plan

• make m4-entry-matrix-check
• cargo test -p graphforge-api --test m4_entry_baseline -- --test-threads=1
• cargo test -p graphforge-api --test file_backed_graph_generation -- --test-threads=1
• Ignored evidence emitters for exit JSON + oversize proof
• Exact-head CI / CI Gate green
• After merge: post ledger on epic(performance): close M4 embedded performance and scale #335 and close the epic (optional feat(api): workspace GSI profiler (GD/GU/Gx grade) #398 excluded)

  

---

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

Note

Reconcile M4 exit evidence and scale claims across docs and test contracts

• Adds new exit ledger artifacts (m4-exit-evidence.md and m4-exit-evidence.json) documenting M4 milestone disposition, reproduction commands, structural outcomes, and policy normalization for thread configurations.
• Updates scale-limits.md to mark >200M edge scale claims as accepted-pending-scale-host-evidence and clarify that 8M/128M densified reruns are optional, not a CI product maximum.
• Refreshes file-backed-oversize-evidence.json fields (UUID, timestamps, peak RSS, source SHA) to match current recorded state.
• Adds notes fields to m4-entry-matrix.json clarifying unavailable thread-parity cells and GPU/accelerator out-of-scope scope boundary.
• Cross-links entry and exit evidence documents in m4-entry-baseline.md and benchmarks/m4_entry_baseline.md.

^{Macroscope summarized d915820.}

Summary by CodeRabbit

• Documentation
  • Updated runtime configuration guidance for 1-worker and 8-worker setups.
  • Clarified executable support and when host-relative configurations are unavailable.
  • Documented current limitations around fresh CSR indexes, private compute resources, optional large-scale reruns, and GPU support.
  • Removed outdated statements regarding CSR expansion and serial algorithm execution.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 36e586cb-6c50-44de-af0b-346393e38992

📥 Commits

Reviewing files that changed from the base of the PR and between 2b1bfda and d915820.

⛔ Files ignored due to path filters (6)

• benchmarks/m4_entry_baseline.md is excluded by !**/*.md
• docs/development/file-backed-oversize-evidence.json is excluded by !**/docs/**
• docs/development/m4-entry-baseline.md is excluded by !**/*.md, !**/docs/**
• docs/development/m4-exit-evidence.json is excluded by !**/docs/**
• docs/development/m4-exit-evidence.md is excluded by !**/*.md, !**/docs/**
• docs/reference/scale-limits.md is excluded by !**/*.md, !**/docs/**

📒 Files selected for processing (1)

• tests/contracts/m4-entry-matrix.json

---

Walkthrough

The M4 entry matrix now documents worker configuration availability and current evidence limitations. It replaces outdated CSR and serial-kernel statements with notes on CSR index misses, compute pools, qualified scale evidence, and GPU scope.

Changes

M4 runtime contract

Layer / File(s)	Summary
Runtime notes and known limitations tests/contracts/m4-entry-matrix.json	The matrix clarifies executable worker entries, host-relative unavailability, current CSR and compute-pool behavior, qualified large-scale evidence, and GPU exclusion.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

• epic(performance): close M4 embedded performance and scale #335 — The updated matrix supports the M4 performance and scale close plan.

Possibly related PRs

• CurateLabs/graphforge#485 — Updates the same M4 entry matrix contract.
• CurateLabs/graphforge#486 — Updates related M4 runtime contract documentation for resource-policy parity.

Suggested labels: ci-cd, tooling

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/345-m4-exit-evidence-c6a4

---

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