Add a tie-in for a Knowledge Vault separate from memory systems so that it can be used across all harnesses.

Update: complete. OpenCoven now has a shared Knowledge Vault available across harness sessions, separate from evolving familiar memory. Semantic recall remains a distinct local layer, so curated shared reference knowledge and learned memory do not collapse into one store.

Filed and on the roadmap. A cross-harness knowledge layer is a natural extension of the familiar identity work — context that travels with the project, not just the familiar. Appreciate the suggestion!