chore(ci): update gemini templates from runtime_ci_tooling v0.23.10

[tsavo-at-pieces]

Summary

• Add read_file, glob, grep_search, list_directory to .gemini/settings.json tools.core — fixes autodoc review passes unable to read source files
• Update autodoc-safety.toml policy template

Generated by manage_cicd update --templates --force

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates CI/Gemini template artifacts generated from runtime_ci_tooling, primarily to unblock Gemini autodoc/review runs from reading repository sources and to refresh the autodoc safety policy template.

Changes:

• Expand .gemini/settings.json core tool allowlist to include file read/glob/grep/list operations (and related file-edit tools).
• Update the autodoc safety policy template to match the newer tool set and wording.
• Add git config --global core.longpaths true in multiple workflow git-config steps.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
.runtime_ci/template_versions.json	Updates recorded template hashes/updated timestamps and the declared tooling version.
.github/workflows/release.yaml	Adds core.longpaths git config in repeated “Configure Git for HTTPS with Token” steps.
.github/workflows/issue-triage.yaml	Adds core.longpaths git config in the git configuration step.
.gemini/settings.json	Extends Gemini core tools with file read/search/list capabilities; reformats Sentry MCP args.
.gemini/policies/autodoc-safety.toml	Refreshes docs-only policy text and explicitly allows read tools while restricting writes to .md.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

tooling_version was changed to 0.23.8, but the PR title/description and the workflows in this repo still reference runtime_ci_tooling v0.23.10. This mismatch will likely cause confusing drift (future manage_cicd update runs may continually try to “fix” template versions) and may misrepresent which template set is actually in use. Align tooling_version here with the version used to generate/sync templates (or update the PR metadata/workflow refs if the intent is a downgrade).