Dev
532ee1a199
When the default/global state.db is corrupt at gateway startup, SessionStore degrades (_db=None) and record_gateway_session_peer never self-heals. Under multiplexed profile routes the AIAgent's lazy _ensure_db_session was then the ONLY durable write for the session, and it created the row identity-less (session_key/chat_id/chat_type/ thread_id/user_id/origin_json all NULL) — unrecoverable by find_latest_gateway_session_for_peer, so Telegram chats forgot prior turns. Persist the routing identity the agent already carries into create_session; plain CLI sessions keep the old identity-less shape. Salvaged leg 1 of #88804; the transcript-recovery leg is covered by the scope-aware session DB resolution already on main.
Contributor email → GitHub login mappings
This directory replaces appending entries to AUTHOR_MAP in
scripts/release.py. The old dict caused constant merge conflicts when
several salvage PRs landed at once — every PR edited the same lines of the
same file. Here, each mapping is its own file, and file additions never
conflict.
Adding a mapping
One file per commit-author email, under emails/:
python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>
- File name = the exact commit-author email (as shown by
git log --format='%ae'). - File content = the GitHub login on the first non-comment line.
Lines starting with
#are comments (use them for the PR reference).
Example — contributors/emails/jane.doe@example.com:
janedoe
# PR #12345 salvage (gateway: fix session key routing)
Rules
- Do NOT add new entries to
AUTHOR_MAPinscripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates). - GitHub noreply emails (
<id>+<login>@users.noreply.github.comand<login>@users.noreply.github.com) auto-resolve — no file needed. - The
Contributor Attribution CheckCI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.