[inth3shadows]

Fixes #3007.

codegraph status now recommends a re-index when a framework comes or goes through package.json alone, with no source file changed.

The bug

#2941 (the #2516 fix, unreleased) has a sync detect frameworks again when what detection read changed. It records the difference from the last full index, and status recommends a re-index. But a sync detects again only when it extracts a file:

// src/extraction/index.ts
const detectedFrameworks = filesToIndex.length === 0 ? undefined : this.refreshFrameworkDetection(...)

So adding express or @sveltejs/kit to package.json with no source file edited records nothing. Status stays silent while the files indexed before the edit lack the framework:

• an unchanged Express app's routes stay missing;
• an unchanged +layout.svelte's goto('/login') stays unlinked.

Repro (Express): index with {"dependencies":{}} and an app.get('/hello', …) server, add express to package.json, run codegraph sync, then codegraph status --json. Before: frameworksChangedSinceIndex: null, reindexRecommended: false. With this change: { added: ['express'] }, true.

I found it with a differential harness that replays a repo's git history and compares each sync against a fresh index. It came up on a SvelteKit app.

The fix

The status hint gets a second source:

• A full index also stamps the resolver's framework set (resolver_frameworks_at_index).
• getFrameworkChangesSinceIndex() merges what syncs recorded, as before, with a comparison of that stamp against the set the resolver detects now. The resolver already detects on every open (createResolver → initialize), so status pays nothing extra.

Since status is a fresh process, it sees a manifest-only change whether or not a sync ran.

Known limits

• A long-running process (the MCP server's watcher) still doesn't pick up the framework. After a manifest-only edit, that process's resolver keeps the old set until a source file is extracted, because the gate above skips detection. This PR only fixes what status reports. Removing the gate would fix the process too, but every no-op sync would then pay a detection, which fix(sync): a long-running session picks up a framework added while it runs #2941 measured at about 300 ms on excalidraw for a full one. I'll open that separately so you can weigh the cost.
• Indexes built before this change have no resolver_frameworks_at_index. The new half of the hint starts after their next full index.

Tests

__tests__/framework-hint-resolver-only.test.ts has 4 cases:

• SvelteKit added, then status, then a re-index clears it and links the goto;
• SvelteKit removed;
• Express added with no source change;
• an unchanged project stays silent.

On main: 3 failed, 1 passed (the silent case). With this change: 4/4. sync-framework-detection.test.ts: 8/8. tsc --noEmit is clean. Full suite: Tests 8768 passed | 417 skipped, 0 failed.

False positives (a hint right after a full index):

• 25 framework fixtures, each checked through index, reopen, sync and a read-only open: none. They cover Next, Express, Nest, Laravel, Django, Flask, React Native, Expo, UIKit/SwiftUI, Nuxt, SvelteKit, Rails, Spring, gin, ASP.NET, Astro, Angular, Drupal, TanStack, Play, COBOL/CICS and an empty project.
• 11 real repositories: none.