docs: digest 2026 research-landscape survey + record LLM-layer position#41
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA new research notes file ChangesResearch Landscape 2026 Notes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/notes/research-landscape-2026.md`:
- Around line 142-145: The reference to `consolidation-and-positioning.md` in
the notes section cannot be verified because the file does not exist in the
repository. Search the repository for any existing consolidation or
positioning-related documentation files with similar names. If found, correct
the filename reference to match the actual file name. If no such file exists and
the deduplication claim is unverifiable, either remove the reference to the
non-existent file entirely, or update the text to explicitly state that the
consolidation decision ownership needs to be clarified or established in a
document that should be created.
- Around line 50-62: The research-landscape-2026.md document claims completed
3-way oracle work (Own.NET vs Infer# vs CodeQL) on WalletWasabi and references a
non-existent consolidation-and-positioning.md file. Either document the
WalletWasabi oracle results in oracle.md and real-world-mining.md with
supporting details about the subscription-leak findings, create the missing
consolidation-and-positioning.md file, or revise the claims in the
research-landscape-2026.md document to clearly indicate whether this work is
completed or planned rather than asserting it as accomplished fact.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 5aa4f09f-40f2-41f0-a480-5924694d10c2
📒 Files selected for processing (1)
docs/notes/research-landscape-2026.md
Add docs/notes/research-landscape-2026.md, a companion to the consolidation-and-positioning note: that one covers form (naming, schema, splits); this one covers research positioning (landscape, gaps, LLM role). Captures the external survey's thesis (external static contracts for .NET resource/lifetime bugs; resource-leak / specify-and-check family; hybrid LLM+static keeping the deterministic checker as decider; the missing public .NET lifetime/resource benchmark as the opening), then records the three places our reading diverges: - We already have a *deterministic* spec miner (contract-inference / _infer_param_effect), which the survey files under far-horizon LLM work. - Differentiation is already demonstrated (3-way oracle on WalletWasabi), so the benchmark ask is "formalize what we did", not net-new. - The LLM layer must be a falsifiable fix/refactor assistant downstream of the verifier, never a trusted spec source: an LLM fix is locally falsifiable (re-run checker + tests), an LLM spec is trusted-base and fails silently. Any spec miner must be validator-gated, not trust-the-source. Records the implied backlog (SARIF exporter, benchmark corpus as first-class artifact, metamorphic robustness harness, validator-gated boundary-API spec miner) without scheduling it, and explicitly de-duplicates the SUB/DIS rename against the already-logged WPFxxx rename decision. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED
…cle run CodeRabbit (PR #41) correctly flagged that the note cited oracle.md / real-world-mining.md as evidence for a WalletWasabi 3-way oracle run, but those files document the ScreenToGif and Dapper runs — WalletWasabi is not written up anywhere in docs/. The WalletWasabi mining/oracle happened in CI but its result was never distilled into the repo, so the citation was broken. Retarget the "differentiation is already demonstrated" claim to the *documented* ScreenToGif oracle result (SystemEvents error + VideoSource warnings, own-only; CodeQL has no "subscribed-never-unsubscribed" query, Infer# misses it too — all in real-world-mining.md "Cross-tool validation"), and label the larger WalletWasabi run honestly as "exercised in CI, not yet distilled into a committed corpus artifact" — which is precisely the benchmark-corpus backlog item, not a result to lean on. Same fix in the backlog bullet. The other flagged reference (consolidation-and-positioning.md) was a merge-timing artifact: it lives in #38, which merged ~3 min after the review; the branch is now rebased onto main, so the file is present. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED
c227fac to
a3476d6
Compare
Add docs/notes/research-landscape-2026.md, a companion to the consolidation-and-positioning note: that one covers form (naming, schema, splits); this one covers research positioning (landscape, gaps, LLM role).
Captures the external survey's thesis (external static contracts for .NET resource/lifetime bugs; resource-leak / specify-and-check family; hybrid LLM+static keeping the deterministic checker as decider; the missing public .NET lifetime/resource benchmark as the opening), then records the three places our reading diverges:
Records the implied backlog (SARIF exporter, benchmark corpus as first-class artifact, metamorphic robustness harness, validator-gated boundary-API spec miner) without scheduling it, and explicitly de-duplicates the SUB/DIS rename against the already-logged WPFxxx rename decision.
Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED
Summary by CodeRabbit