The rubric introduced in this PR taught the agent to use
`{"metadata.type": "decision"}` filters, but the v2 search
contract (docs/platform/features/v2-memory-filters.mdx) requires:
1. The root must be a logical operator (`AND`/`OR`/`NOT`) with an array.
A bare `{"user_id": "..."}` is rejected.
2. Metadata uses a nested object — `{"metadata": {"type": "..."}}` —
not a dotted key. Only top-level metadata keys are filterable.
Without this fix, agents following the rubric produce filter calls
the platform either ignores or rejects.
Also replaces the literal `"alice"` in the worked example with a
clearly-marked `<your_user_id>` placeholder so agents don't copy
verbatim, and adds a one-line "substitute the active user_id"
instruction.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Mgeeeek
1dcf842635