feat(provider): split memory search scope_filter → scope_all + scope_any (bifrost 0.8.0/wire v0.6)

Repin bifrost 0.7.0→0.8.0 and reimplement the memory store's search scope
filter to the v0.6 split (#11): scope_all (AND/intersection) + scope_any
(OR/union over a list of conjunctive scopes), at parity with the v0.6
reference _matches_scope / _validate_scope. No-compat: scope_filter removed.

scope_any is the union-visibility primitive that resolves the #295/#297
silent-zero AND foot-gun — a subset-scoped chunk now recalls via an OR
member. End-to-end cold recall now gated only on Worldtree emitting
scope_any on its recall path (#297, upstream).

- store: search(scope_all, scope_any); _scope_subset + _matches_scope + _validate_scope
- contract v1.2: search FN sig, INV-005 recomposed, PRE-003 both fields, scope_any_union test
- tests: scope_any union, scope_all∧scope_any compose, both-empty match-all; parity vs real 0.8.0 dispatch (433 green)
- #17 contract: sync stale scope_filter/_scope_matches-AND refs to scope_all/scope_any
- runbook + persistent-memory updated; provider bounced onto 0.8.0 (fresh empty db)

v0.17.6

persistent-memory.md

@@ -43,6 +43,22 @@ model output is untrusted); upstream API key stays server-side (INV-003).
 
 _As of 2026-06-16:_
 
+**LATEST (2026-06-16 PM) — BIFROST REPINNED 0.7.0→0.8.0 (wire v0.5→v0.6).** The
+memory `search` scope filter was split into `scope_all` (AND/intersection) +
+`scope_any` (OR/union over a LIST of conjunctive scopes) — bifrost #11, the canonical
+fix for the #295/#297 silent-zero AND foot-gun. Our store + contract (v1.2) + tests
+reimplemented to parity with the v0.6 reference `_matches_scope`/`_validate_scope`
+(no-compat: `scope_filter` REMOVED). 433 tests green incl. the new `scope_any` union
+test + the parity-vs-reference test through the real 0.8.0 `dispatch_memory_call`.
+Memory provider BOUNCED onto 0.8.0 (`:8391`, fresh empty `memory.db` — the prior
+5-chunk #296 corpus was WIPED, operator confirmed "nothing of value", SUPERSEDES the
+"KEEP PINNED" note below). **End-to-end cold recall now waits only on Worldtree
+EMITTING `scope_any` on its recall path (#297, upstream).** Affect plane untouched
+(split is memory-only); affect provider still on its 0.7.0-loaded process (bounce
+optional — affect wire unchanged at 0.8.0). NOT yet committed; patch bump v0.17.6
+pending operator commit approval. **#17 contract carries stale `scope_filter` /
+`_scope_matches`-AND references — fix when #17 TDD starts.**
+
 **Ratatoskr now has a SECOND identity: the v1 Bifrost Tier-3 consumer** — the
 durable persistence provider Worldtree writes Tier-3 agent affect/persona +
 memory into — alongside the original debug-observability TUI/web. The
@@ -193,6 +209,8 @@ decision. Captures rationale that won't be obvious from code alone.
 - `[2026-06-16]` **agent_self lattice SHIPPED both sides → our axis-validation gap CLOSED (v0.17.5).** bifrost 0.7.0 / wire v0.5 adds agent_self to the scope lattice `{end_user,group,tenant,agent_self}` (#10, driven by our foot-gun flag via bifrost-dev); Worldtree pinned 0.7.0 + canonical-synced the v0.5 spec (v0.35.11, `c860fb0`). **SUPERSEDES the prior "HELD, do NOT add axis-validation" note** — we DID add `_validate_scope_filter` (4-axis) to match the reference (bifrost-dev's recommendation, purely additive; out-of-lattice → InvalidFilter). #297 union build unblocked. Memory provider restarted on 0.7.0.
 - `[2026-06-16]` **#17 contract reviewed + the debug-assist arc fully closed.** `/heid` design consult + `/heid-contract-review` panel both run on `docs/contracts/issues/17.contract.md` (validates OK). The #295 debug-assist that opened the session is closed end-to-end: root cause (scope-axis asymmetry) → #296/#297 research issues + corpus → a shipped bifrost protocol change (agent_self canonical) → our store at parity. NEXT durable step: #17 TDD (tracked: Gitea #17 + the contract).
 
+- `[2026-06-16]` **Repinned bifrost 0.7.0→0.8.0 + reimplemented memory `search` to the v0.6 scope split (operator-directed).** `scope_filter` → `scope_all` (AND) + `scope_any` (OR/union over a list of conjunctive scopes), bifrost #11 — the canonical resolution of the #295/#297 silent-zero. **SUPERSEDES the "Provider stores byte-faithful to AND reference / Do NOT flip `_scope_matches` to OR" entry above**: the reference itself now does OR via `scope_any` (a NEW field — `scope_all` keeps the old AND semantics; this is an additive split, not a flip of the AND predicate). Store / contract (v1.2) / tests at parity with the v0.6 reference; provider bounced onto 0.8.0 with a wiped DB (operator: "nothing of value"). Cold recall now gated only on Worldtree emitting `scope_any` (#297). **#17's contract has stale `scope_filter`/`_scope_matches`-AND references (its `assumptions`, INV-004, and the op-feed `search → req {scope_filter}` summary shape) — update those to `scope_all`/`scope_any` when #17 TDD starts; INV-004's intent (observe must not alter scope semantics) still holds.**
+
 _For per-issue TDD implementation notes, Volva findings, and contract amendments, see the git log — every per-issue commit carries a structured message capturing the trail._
 
 ## Tried and abandoned