Greptile Summary

This PR fixes a bug where the registered memoryCapability was not being persisted to or restored from the plugin registry cache. On a cache hit, listActiveMemoryPublicArtifacts would return empty because memoryPluginState.capability was never repopulated. The fix adds memoryCapability to CachedPluginState, saves it via getMemoryCapabilityRegistration() when caching, and passes it through restoreMemoryPluginState on a cache hit — consistent with how all other memory state fields (corpusSupplements, memoryRuntime, etc.) are already handled.

Confidence Score: 5/5

Safe to merge — targeted one-field fix consistent with existing cache patterns, backed by a direct regression test.

The change is a minimal, well-scoped addition of one previously omitted field to the plugin registry cache save/restore cycle. It mirrors exactly how every other memory state field is handled. The afterEach hook calls clearPluginLoaderCache() → clearMemoryPluginState(), so test isolation is preserved. No P0 or P1 findings.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(plugins): restore cached memory capa..." | Re-trigger Greptile}

I checked the current CI on April 12, 2026 and the failures here appear to match failures already showing up on recent main runs as well (for example CI runs 24302117102 and 24302181980).

The red jobs I inspected are failing in areas outside this diff, including:

• existing extension boundary failures around extensions/memory-core/src/dreaming-narrative.ts
• an existing web-fetch boundary failure in src/secrets/runtime.test-support.ts
• generated schema drift in src/config/schema.base.generated.test.ts
• unrelated msteams logging expectation failures
• unrelated provider-family contract coverage failures for opencode / opencode-go

This PR only changes src/plugins/loader.ts and src/plugins/loader.test.ts to persist/restore cached memoryCapability, and I do not see a CI failure pointing at that path.

Focused validation for this change passed locally:

• pnpm exec vitest run --config vitest.config.ts src/plugins/loader.test.ts src/plugins/memory-state.test.ts --maxWorkers=1

Happy to rebase/rerun once main is green again, or adjust if anyone sees a direct coupling I missed.