docs(gptel): add shortlist design doc for additional gptel tools

The Gptel Work project asked for a survey of published gptel tools
with adopt / skip / defer decisions per candidate.  I can't do a
live community-tool survey from this session, so the doc covers
the candidates the task body called out plus a few obvious
adjacents.

Decisions:

- ADOPT (7): `search_in_files`, `git_status` / `git_log` /
  `git_diff` (three tools), `web_fetch`, `search_emacs_help`,
  `find_file_by_name`, `take_screenshot`.  Each gets a sketch in
  the doc -- args, validation posture, implementation outline.
- DEFER (2): `run_shell_command` (huge surface, click-fatigue
  risk; the ADOPT-bucket tools cover most legit use cases),
  `org_capture` (needs UX design for template pre-fill and the
  round-trip).
- SKIP (1): `eval_elisp` (code execution from a model is too
  dangerous even with confirm-each-call).

The doc also lists three follow-ups: the live community survey
that this session couldn't do, per-tool implementation sub-tasks
to be filed under the next iteration of Gptel Work, and a
sandboxing-convention decision for `web_fetch` (allowlist of
outbound URLs vs description-only warning).

Three open questions at the bottom of the doc for review:
build-all-at-once vs paired stages, `fd` as a hard dep vs `find`
fallback, Hyprland-only screenshot vs Wayland-generic via a
portal.

Closes the Gptel Work PROJECT for this iteration -- all 9 in-scope
sub-tasks landed this session.

0 files changed, 0 insertions, 0 deletions