GraphRAG Notes 0.1.0-rc.2 macOS Apple Silicon candidate

GraphRAG Notes 0.1.0-rc.2 brings the daily-use features from issues #57–#64 into one versioned candidate: provider-free keyword search, result inspection and source opening, resumable folder sync, multiline capture and guarded editing, cited raw context, connection review/undo, and the terminal workspace.

This prerelease provides a native macOS Apple Silicon archive, declaring macOS 15.0+, tested on macOS 27.0.1. Linux and Intel macOS native acceptance remain in #66; authenticated network/MCP access for OpenClaw and Hermes remains in #56. Windows is outside scope.

For a new installation, use the version-pinned script (review it before running):

curl -fsSL https://raw.githubusercontent.com/mateu/graphrag-notes/v0.1.0-rc.2/scripts/install.sh -o /tmp/graphrag-install.sh
bash /tmp/graphrag-install.sh --version 0.1.0-rc.2
export PATH="$HOME/.local/bin:$PATH"
graphrag --version
graphrag init --backend ollama

For an existing installation, first create and verify a portable backup, then install to a separate --bin-dir or deliberately add --force. Use plain graphrag init to inspect an existing configuration; --backend ollama selects a backend for a new configuration.

The installer verifies the archive checksum, refuses an existing binary without --force, and preserves edited starter notes. Configuration is written only by an explicit init --write. Back up before upgrading an existing corpus: this binary supports schema 15, whereas rc.1 supports schema 14; downgrade requires a compatible pre-upgrade backup restored into a fresh database.

Only three assets are published: the native archive, SHA256SUMS, and BUILDINFO.json. The latter distinguishes the final release commit from the original native build commit, identifies their shared compiled inputs, and records exact hashes, native dependencies, and completed preparation gates. The archive contains only the executable and fictional starter notes.

Before publication, 576 Rust tests passed (five existing ignored), all six PR CI gates passed, release/evidence/installer regressions passed, and the native binary passed all nine combined daily-workflow scenarios with deterministic providers and existing live Ollama models. Checks include provider-failure draft recovery, revision guards, explicit review/undo, and actual SIGINT checkpoint/resume. Local archive installation passed independently. Metrics are automated local observations, with human time/copies unmeasured; unequal baseline/candidate totals are not speedup claims.

Publication verification passed on 2026-10-03 UTC (2026-10-02 America/Denver). The public tag resolves to the reviewed merge commit; the tag-pinned HTTPS installer equals its reviewed Git blob. All three downloaded assets match the local sealed files byte-for-byte. Fresh actual HTTPS installation passed in 1.313 seconds (one fresh invocation; three total for fresh/refusal/force), including checksum, exact version/help, unchanged installation after refusal, and preservation of edited starter notes during force reinstall.

The downloaded installed executable passed all nine daily-workflow scenarios offline (1.934 seconds) and with existing live Ollama models (8.851 seconds), including provider-failure recovery and actual SIGINT checkpoint/resume. Each candidate workflow used 37 CLI processes, six workspace input lines, and 16 automated canonical-ID transfers. Available rc.1 equivalents also passed in separate private corpora. Human time/copies remain unmeasured; these unequal capabilities and local automated timings do not establish a speedup.

BUILDINFO.json was sealed before publication and retains its truthful preparation-time published_asset_install: not_run state. The results above supplement that record; the tag and all three sealed assets remain unchanged.

Full walkthrough and evidence: daily workflow, validation, release policy.

Release source: 7a8deb859037e396e3314976aa57ea4b58de6e39 (tree 64b01927f10096e4723eef636a3d19c40b9dcce0). Native build source: 4028e129829cf7cf225406b787fec03820de07c7. Their compiled-input identity matches; the binary SHA-256 is 5c5045d0f6106949bcd367e3de59a594897b0dfb09bc53aee9572937f21390d4. Archive SHA-256: e88a426c0f140aa364ff1b56bb5dbc9a30fd77021f6e232894e8255e596064d6.