Merge origin/master into beta to reconcile history

Brings master's three post-divergence commits (700a1b4 truncation fix,
85fc036 v2.1.10 release, 96f528b #14 group-picker+pin fix) into beta's
ancestry so future merges don't repeat the same conflicts.

Content-wise a near-no-op: the truncation fix's patch-id already matched
1a8b909 on beta, the v2.1.10/v2.1.11 release chores are superseded by
beta's 2.3.0, and the #14 code fix is already on beta via b960e62 (and
the pin-picker at index.js line 8562). Resolutions:

- manifest.json: kept beta's 2.3.0 + i18n block (master would regress to
  2.1.11 without i18n).
- index.js: kept beta's picker refactor (master's version still uses the
  old callGenericPopup inline pattern).
- CHANGELOG.md: kept beta's 2.3.0 section; folded the two missing bullets
  from master's 2.1.11 section (#14 picker fix + Pin fix) into 2.3.0
  Bug Fixes since the code is already on beta but the release notes
  weren't documenting it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

CHANGELOG.md

@@ -20,6 +20,8 @@
 - **Translate diagnostic report**: The diagnostic report (Troubleshooter → Diagnostic Report) now uses `t`-tagged strings for all section headings, field labels, and status text, so it renders fully in the active language instead of mixing translated health check content with English scaffolding.
 - **Fix extraction script generating incomplete translation templates**: `extract-strings.js --missing-json` without `--locale` was comparing against `zh-tw.json` by default, outputting only the keys missing from that locale instead of all translatable strings. New translations started from this template would be missing every key that zh-tw already had. Now `--missing-json` without `--locale` outputs all keys as a complete template; use `--missing-json --locale <file>` to find gaps in a specific locale.
 - **Group chats: fixed destructive extraction-pointer reset and silent partial-member lists**: In group chats with many members, `getGroupMembers()` silently dropped any member whose avatar hadn't finished loading into SillyTavern's character array — usually a load-order race during startup. That partial list caused two visible failures: extraction and consolidation only ran for a subset of members, and the stale-metadata self-heal in `onChatChanged` would sometimes conclude "no memories anywhere" and reset `lastExtractedIndex = -1`, forcing a full re-extraction from message 0 (expensive and duplicate-producing on long chats). Three fixes: (1) guard the destructive reset when member resolution is incomplete — the pointer is preserved; (2) new yellow health check *"N of M group members could not be loaded"* with the unresolved avatar list; (3) one automatic retry 2 seconds after each chat change, which clears the warning silently for the common race case. Fixes [#17](https://github.com/bal-spec/sillytavern-character-memory/issues/17) (see [#18](https://github.com/bal-spec/sillytavern-character-memory/issues/18) for root-cause analysis).
+- **Fix group chat character pickers always selecting first character**: In group chats, the Consolidate, Reformat, and Memory Manager character pickers silently ignored the user's selection and always operated on the first character. The selected radio button was read after `callGenericPopup` closed and destroyed the popup DOM, so the selector always returned `undefined`, which coerced to index `0`. Fixed by tracking the selection via a delegated `change` listener before the popup closes. Fixes [#14](https://github.com/bal-spec/sillytavern-character-memory/issues/14).
+- **Fix Pin always saving to first character in group chats**: The pin handler tried to auto-match the message sender by name, but silently fell back to the first group member whenever the match failed (user messages, name discrepancies, disabled members). Pin now shows an explicit character picker in group chats, pre-selected to the message sender when a match is found. Fixes [#14](https://github.com/bal-spec/sillytavern-character-memory/issues/14).
 
 ## 2.1.10