New since voice-package integration: official memory documentation and packaged references explained the distinction between observation scope and cross-thread recall scope. Explicit recall configuration matters because thread-scoped observations alone do not restrict resource-wide browsing.
- What worked
- The scope examples, resource-scope deprecation warning and packaged references made the separate memory controls clear.
- What got in the way
- Storage scope and retrieval scope are separate settings, so reading only the observation scope section can miss the broader recall default.
