memory-refreshlisted

# memory-refresh — the recurring loop, user-triggered The verb the user invokes whenever they want their vault up to date. Could be daily, weekly, ad-hoc. The skill orchestrates ingest + heal + coverage + soft eval in one continuous run, interactively in the user's own session so permissions are granted in-context. ## Pre-conditions (fail loudly if missing) - Vault exists at `$MEMORYVAULT_ROOT` (default `~/MemoryVault`) with a `.mvkit/bootstrap_state.md` that shows setup completed. If not: tell the user "no vault found, run /memory-setup first" and stop. - The kit's MCP server is registered (you should see `mcp__plugin_memoryvault-kit_memoryvault__memory_*` tools available). If either is missing, surface the exact gap. Don't try to be clever about partial setups, point at /memory-setup. ## Step 1 — Read vault state (5-10 seconds, before any change) ```bash VAULT=${MEMORYVAULT_ROOT:-$HOME/MemoryVault} cat $VAULT/.mvkit/bootstrap_state.md cat $VAULT/.mvkit/connected_sources.json cat $VAULT/.mvkit/refresh_state.json 2>/dev/null || echo "(no prior refresh — first run)" cat $VAULT/.mvkit/active_retriever.json 2>/dev/null || echo "(default retriever: combined_graph)" ls -t $VAULT/.mvkit/eval-history/ 2>/dev/null | head -3 head -30 $VAULT/.mvkit/mature_entities.md 2>/dev/null ``` Read `last_refresh_at` from `refresh_state.json`. This is the authoritative "when did /memory-refresh last run" timestamp — separate from `last_ingest_per_source` (which tracks scheduled-or-man