feat(memory): opt-in persistent memory scaffold for providers#2745
Merged
Conversation
Adds a provider capability (usesMemoryScaffold) and a container-side boot scaffold that materializes a persistent memory/ tree for providers that opt in. Dormant for the default provider — the scaffold is only built when a provider declares the capability, so existing installs are byte-identical (asserted by a boot-gate wiring test). Co-Authored-By: Claude Opus 4.8 <[email protected]>
gavrielc
approved these changes
Jun 13, 2026
This was referenced Jun 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
(Core source seam — none of the above fit cleanly; not a skill.)
Description
What — Adds a provider capability (
usesMemoryScaffold) and a container-side boot scaffold that materializes a persistentmemory/tree for providers that declare it.Why — Some providers keep their own memory store (e.g. server-side conversation history) and need a persistent on-disk memory tree rather than the default project-doc surface. This adds the seam without touching the default path.
How it works — A capability flag on the provider type. At container boot the runner checks it and, only when set, materializes the
memory/tree from templates. The default provider never triggers it.How it was tested — Host (458) and container (105) suites green, both typechecks clean. A boot-gate wiring test asserts the default path is unchanged — it goes red if the wiring is removed. Existing installs are byte-identical.
Usage — None directly; dormant until a provider opts in.