v1.6.4 — Windows fix + contributor docs
Closes #23 (Windows stack overflow) and ships the developer-facing scaffolding.
Issue #23 — Windows stack overflow
tokio::main runs block_on on the process's main thread, which uses the OS default stack budget. Windows defaults to 1 MB; the v1.5 background re-test loop's futures overflow it.
Fix: re-launch main on std::thread::Builder with 8 MB stack + tokio runtime with thread_stack_size(8 * 1024 * 1024).
All six CI jobs go green:
- ✅ Linux fmt/clippy/test
- ✅ Windows fmt/clippy/test
- ✅ macOS fmt/clippy/test
- ✅ Linux integration (real Qdrant)
- ✅ Windows integration (bundled Qdrant)
- ✅ cargo-audit
mgimind doctor detects pending cardinality proposals
After extraction lands hundreds of predicate cardinality proposals, the user had to remember to register them. doctor now surfaces the count + --fix bulk-registers via the same path migrate-v14 cardinality --apply uses.
Project documentation
- CONTRIBUTING.md — project layout, three architecture rules, branch model.
- CODE_OF_CONDUCT.md — Contributor Covenant 2.1 compression.
- SECURITY.md — vulnerability disclosure policy.
- .github/ISSUE_TEMPLATE/ — bug + feature + Discussions routing.
- docs/design/adr/ — four ADRs (Cardinality enum, Mechanism 1 invariant, §10 q5 guarantees, install-mode anchors).
- benchmarks/v0.14.3-gpu/ — R@5 = 99.2% baseline committed for STALE comparison.
- docs/blog/2026-06-04-validity-model.md — draft technical post.
- .editorconfig — consistent indent / EOL.
Tests
290 unit + 6 integration tests pass on every platform (Linux, Windows, macOS).
Migration
None. Only Windows fix + scaffolding; no semantic changes.