Skip to content

fix(cache): invalidate semantic modules by program context - #132

Open
MikeeI wants to merge 1 commit into
codellm-devkit:mainfrom
MikeeI:fix/issue-014
Open

fix(cache): invalidate semantic modules by program context#132
MikeeI wants to merge 1 commit into
codellm-devkit:mainfrom
MikeeI:fix/issue-014

Conversation

@MikeeI

@MikeeI MikeeI commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Make semantic module reuse depend on the compiler program context that produced it.
Prevent resolver provenance from being serialized as reusable source structure.

Evidence

  • Current validity checks only one source file and analyzer version.
  • A warm run can retain an old callee after its path alias stops resolving.

Changes

  • Remove per-run callee provenance from persisted modules.
  • Invalidate a program's cached modules when its semantic inputs change.

Risks and boundaries

  • Correctness takes precedence over partial per-file reuse within a changed program.
  • Persistent compiler state and summary reuse remain out of scope.

Verification

  • bun test test/l1-body-cache-shape.test.ts
  • bun test
  • bun run typecheck

I checked the relevant issues, comments, pull requests, and discussions; this pull request is not a duplicate.

Disclosure

Investigated thoroughly with GPT-5.6 at extra-high reasoning effort.
I used Oh My Pi as the agent framework.
This report is not generic or unreviewed AI-generated output.
Its claims were checked against the cited evidence.
It includes the relevant detail intended to help maintainers resolve the issue.
If reports like this are not useful to the project, please let me know.
I will refrain from submitting similar reports.
My intent is to help without wasting maintainer time or energy or discouraging their work.
Thank you for your work.

@rahlk rahlk self-assigned this Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants