fix: enforce zara-memory type isolation #335

Open
nsaspy wants to merge 0 commits from rage/292-memory-type-isolation into main
Owner

Closes #292. Advances #7.

RED first: scope/owner isolation is already enforced, but typed remember/recall can still accept backend records labeled with a different memory type. This hardens the plugin-specific schema boundary without inventing missing symbolic-memory backend capabilities.

Closes #292. Advances #7. RED first: scope/owner isolation is already enforced, but typed remember/recall can still accept backend records labeled with a different memory type. This hardens the plugin-specific schema boundary without inventing missing symbolic-memory backend capabilities.
Some checks failed
CI / test (pull_request) Failing after 17s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/292-memory-type-isolation:rage/292-memory-type-isolation
git switch rage/292-memory-type-isolation

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/292-memory-type-isolation
git switch rage/292-memory-type-isolation
git rebase main
git switch main
git merge --ff-only rage/292-memory-type-isolation
git switch rage/292-memory-type-isolation
git rebase main
git switch main
git merge --no-ff rage/292-memory-type-isolation
git switch main
git merge --squash rage/292-memory-type-isolation
git switch main
git merge --ff-only rage/292-memory-type-isolation
git switch main
git merge rage/292-memory-type-isolation
git push origin main
Sign in to join this conversation.
No description provided.