Which AI runtime should Memory Vault support next?

[qh-work]

v0.21 introduces one taskless Vault shared through reference integrations for Codex, Claude Code, Gemini CLI, and generic local runtimes.

We are looking for contributors to add privacy-safe synthetic conformance fixtures and reference adapters for other hosts.

Good contributions include:

• a new lifecycle mapping using only documented visible input and final output;
• interruption and acknowledgement-loss fixtures;
• hostile-memory fixtures proving memory cannot become instruction or authority;
• content-free platform smoke reports;
• packaging improvements that reduce setup friction.

Do not post real memories, transcripts, credentials, account identifiers, native session IDs, local paths, or live Vault data.

Start with issues #3 through #7. AI-assisted pull requests are welcome when the contributor can reproduce and explain the lifecycle mapping.

Release: https://github.com/qh-work/memory-vault-sync/releases/tag/v0.21.0