Vault-for-LLM v0.7.24

Highlights

• Adds safer Obsidian mirror conflict detection: when both the source note and Vault raw copy changed, Vault preserves both sides and records a metadata-only conflict for review.
• Adds generated Vault Remote Server hardening materials, including env-file templates and a deployment checklist for token handling, TLS, backups, audit review, and candidate-first remote writes.
• Adds a compact multi-agent Activity Health surface for connected agents, pending candidates, sync conflicts, Obsidian mirror conflicts, and daily human-review pressure.
• Bumps the release version from v0.7.23 because v0.7.23 was already published before these pre-release hardening changes landed.

Validation

• Release Readiness CI passed on PR #282 and PR #283, including Python 3.10/3.11/3.12 tests, build/wheel smoke, README smoke, module size gate, privacy scans, Search QA regression gate, and uv workflow smoke.
• Local full test suite passed before the version bump: 2356 passed, 10 skipped.
• Local targeted release tests passed after the version bump: release parity, CLI JSON contracts, setup-agent, gateway, Obsidian import, and GUI tests.
• Clean wheel install verified v0.7.24 metadata.
• Setup-agent generated Remote Server, Supabase realtime, Obsidian, n8n/Coze, and validation templates successfully.
• Generated local smoke test passed.
• Vault Remote Server was started locally and validated through the generated client: health, OpenAPI, search, and candidate-first memory submission passed.
• Twine package checks passed for wheel and sdist.

Notes

• Optional semantic dependencies remain optional; doctor may warn when ONNX/transformers are not installed.
• vault init and vault compile are functional but not yet part of the stable --json command contract; that remains a follow-up for stricter agent-first automation.