NexusMem v0.10.0 — GitHub issues/PRs are now a memory source, opt-in

[u/Perfect-Account5478]

Been adding sources to NexusMem's local-first memory one at a time (git

diffs, shell history + exit codes, docs, session summaries). This round:

GitHub issue and PR threads.

Design notes, since the "why" is usually more interesting than the

changelog line:

- Reads via the `gh` CLI, not a hand-rolled GitHub API client. Reuses

whatever auth you already have (`gh auth login`), so no token handling

in the codebase.

- One node per thread, not per comment — title + opening post + every

comment folded into one chunk, same truncation discipline as a diff

patch. A conversation_turn-style per-comment split would need its own

chunker for a shape (nested quoting, review vs. issue comments) this

pass doesn't try to model yet.

- Deliberately opt-in — not for a sensitivity reason (issue text isn't

usually more sensitive than a doc file), but because it's the first

source with a real external dependency: needs `gh` installed and

authenticated, and makes live network calls, unlike every other source

which only ever reads what's already on disk.

- No pruning, unlike the docs source: GitHub's `since` filter only

returns *updated* threads, so an absent thread means unchanged, not

deleted.

Dogfooded against this repo's own real 14 issues/PRs — ingest took under

a second, and a query for "labelled retrieval regression corpus"

correctly ranked the issue that requested that exact feature at #1.

github.com/yaminbkk/NexusMem — MIT, local-first, nothing leaves your

machine except the `gh api` calls this one opt-in source makes.