[joyful-ii-V-I]

--pr-context rebuilt the static include-coupling table once per changed file, and again on every pass of its trim ladder. The table depends only on the ingest, so this was loop-invariant work: about 87% of --pr-context's time. Found while profiling legendcoveragecheck (#394).

The change: a lazily built CoCouplingCache in src/gitmine.h, keyed on the ingest, with an EXPECTS that it is only used with that ingest. writePrContext, writeSituation and computeSituationFacts share one cache per call; single-probe callers behave as before. Not changed: multi-root --pr-context still builds once per root.

Output: byte-identical on all 49 argv:

• 29 in-scope CLI runs: --pr-context at HEAD~1/~5/~30 on four repos (ripwire, hono, tmux, textual), budget variants, --situ, --cochange;
• 6 MCP calls;
• 3 dirty-tree runs: --handoff, bare --situ, bare --pr-context;
• 11 out-of-scope runs.

Speed: --pr-context=HEAD~30 on this repository went from 49.5/45.8 s to 8.7/7.7 s, two interleaved runs each, about 5.8× faster.

Checks:

• 22 targeted gates pass.
• ASan (llvm@22): 10 gates and the HEAD~30 run show zero sanitizer reports, and the output still matches base.
• --quality-delta gates 0; prereview passes.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Performance
  • Pull request context and situation reports now reuse coupling analysis across related checks, reducing repeated calculations.
  • Co-change partner classifications remain unchanged, so these performance improvements do not alter the reported results.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: redhat-et/ripwire/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5414b561-3172-498e-b49e-5fb4e4ba27ee

📥 Commits

Reviewing files that changed from the base of the PR and between a88f03d and 82cd0bd.

📒 Files selected for processing (3)

• src/gitmine.h
• src/prcontext.h
• src/situ.h

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📝 Walkthrough

The precomputed co-change partner lookup now supports a reusable, lazy StaticIncludeCoupling cache. Context and situation operations create a cache and pass it to their co-change probes.

Changes: Co-Change Coupling Cache

Layer / File(s)	Summary
Cache-backed co-change lookup src/gitmine.h	CoCouplingCache lazily constructs and reuses StaticIncludeCoupling for its IngestResult. The precomputed-sets cochangePartners overload accepts an optional cache and creates a local cache when none is supplied.
Reuse cache across context and situation probes src/prcontext.h, src/situ.h	writePrContext, writeSituation, and computeSituationFacts create and pass a shared cache to their cochangePartners probes.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Refactor

Suggested reviewers: barefootski

Merge Risk: ⚪ Minimal · up to 82cd0

Context and situation probes now reuse a coupling table without changing their ingest source. No concrete correctness or availability risk is evident, so the change is mergeable.

Pre-merge checks · 4

Passed checks (4 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly identifies the performance change: reusing the include-coupling table once per call instead of rebuilding it for each changed file, with the reported speedup.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

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