39a234b133
Follow-ups on the salvaged Browser Use CLI integration (PR #66476): - browser_exec runs model-written Python on the host. Strip it at tool-definition time for sessions whose resolved toolsets exclude 'terminal' so terminal-less surfaces (locked-down messaging configs) don't silently regain host code execution through the browser toolset. Session-level gate in model_tools, not a check_fn (check_fn results are TTL-cached process-wide across sessions). - Replace the live 'browser-use skill' schema fetch with a pinned helpers digest: no third-party version-drifting text in the prompt, byte-stable schema across machines. A/B benchmarked (108 runs, opus-4.8 + kimi-k3, 6 multi-step web tasks x 3 arms x 3 reps): pinned digest matches the full skill dump 36/36 vs 36/36 at ~equal tokens; both cut total task tokens ~60% vs the legacy browser_* toolset. - Docs note for the terminal gate; contributor mapping for salvage.
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.