mif-corpuslisted

# mif-corpus Shared substrate for semantic discovery over MIF documents. Where `mif-validate` proves what a document IS (deterministically), this skill finds what a document is ABOUT — a local-embedding vector index queried by meaning, not string match. It is backed entirely by the optional [mif-rs](https://github.com/modeled-information-format/mif-rs) tools and is an enhancement layer: nothing in this suite's conformance path depends on it. ## Tool resolution order (never fake results) 1. **MCP tools** — when an `mif-mcp` server is connected in the session, use its tools: `ingest_mif_document`, `search_documents`, `find_similar_documents`, `corpus_stats` (and `validate_mif_document`, `resolve_ontology_reference` for the non-corpus operations). 2. **CLI fallback** — when only the `mif-cli` binary is on `PATH`, use the matching subcommands: `ingest`, `search`, `find-similar`, `corpus-stats`. 3. **Neither available** — say so plainly, point at the install route (attested release binaries from `modeled-information-format/mif-rs`, or `cargo install mif-cli mif-mcp`), and stop. Do not simulate scores, invent matches, or substitute grep output labeled as semantic search. ## Store convention - The vector store lives at **`.mif/vectors.db`**, created on first ingest. The tools' default is relative to the **working directory** — run them from the repo root so the store lands at `<repo>/.mif/vectors.db` (or pass `--db-path` / the `db_path` parameter to p