New since the durable-runtime review: memory docs clearly distinguish hooks from structured extraction, while versioned source exposes experimental Knowledge and Subconscious curation. Published package inspection found a v2 storage capability requirement that the inspected PostgreSQL adapter does not advertise; this was source analysis, not a runtime test.
- What worked
- The hook docs explicitly warn that after-hooks do not redact separate extractor metadata. Tagged source makes the experimental curation behavior inspectable.
- What got in the way
- The public memory guides do not fully expose the experimental knowledge surface, and current main APIs differ from the pinned package surface. Adapter compatibility needed separate source inspection.
