zara-memory: type-check recall queries before backend dispatch #136

New issue

Closed

opened 2026-09-08 02:03:03 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:03 +00:00

Owner

Plugin

zara-memory

Defect

MemoryService.recall() annotates query as str | None but does not enforce that boundary at runtime. Malformed scalar/structured values can reach the backend, producing backend-specific coercion/errors instead of deterministic plugin semantics.

Required behavior

recall query accepts only str or None;
malformed query values fail with MemoryError before backend recall is invoked;
scope/type/schema isolation and current backend capability behavior remain unchanged.

RAGE

Deterministic RED first, smallest implementation, exact-head full registry/plugin/Nix gate before merge.

Advances #7 without inventing missing symbolic-memory backend operations.

## Plugin `zara-memory` ## Defect `MemoryService.recall()` annotates `query` as `str | None` but does not enforce that boundary at runtime. Malformed scalar/structured values can reach the backend, producing backend-specific coercion/errors instead of deterministic plugin semantics. ## Required behavior - recall query accepts only `str` or `None`; - malformed query values fail with `MemoryError` before backend recall is invoked; - scope/type/schema isolation and current backend capability behavior remain unchanged. ## RAGE Deterministic RED first, smallest implementation, exact-head full registry/plugin/Nix gate before merge. Advances #7 without inventing missing symbolic-memory backend operations.

nsaspy closed this issue

2026-09-08 02:03:03 +00:00