v0.1.0-alpha.32 — Keep history scans running past excluded paths

Git history containing protected paths could abort a scan with
PATH_OUT_OF_SCOPE: Select a relative path within this project. Collection now
skips those candidates and continues. Explicit out-of-scope queries remain rejected.
Renamed changes with a protected old path are also excluded before content capture.

Update and retry

codememory.cmd update --version v0.1.0-alpha.32

On macOS/Linux use codememory update --version v0.1.0-alpha.32.
Reconnect open Codex/Claude MCP clients. From the selected project directory:

codememory history scan --all
codememory history status

Use codememory.cmd on Windows. Existing captured history is retained; do not
remove the database, project registration or API profile. No new migration or
code reindex is required for this fix. Provider selection and credentials are unchanged.

Validation and limits

Local frozen installation, lint, typecheck, build and all 229 tests across 43 files
passed before tagging (full test duration: 91.70 seconds). All 15 package manifests
match the release version.

The regression reproduces the original exception without the fix and passes with
it. It uses a real temporary Git repository with protected files and a rename,
checks that excluded content is not captured, and keeps explicit path rejection.
Release publication requires the tagged Linux, Windows and macOS checks to pass.
The reported Windows log did not identify its triggering file; this fixes the
reproduced failure mechanism, not a claim of testing that private repository.

Installation ·
Changes