fix: configure git identity before bundled-skill worktree commits

[tend-agent]

Problem

Bundled skills that commit in a fresh /tmp git worktree (and in the main checkout) run git commit without first configuring a git identity. On runners where the harness doesn't pre-seed one, the first commit fails with Author identity unknown, the branch gets pushed with no commit, and gh pr create then fails with No commits between main and <branch>. Sessions self-correct by setting an identity and recommitting, but they burn turns and momentarily push an empty branch. Per #729 this has fired on consecutive committing nightlies, making it structural rather than a one-off.

The gap is systemic — the same git commit-without-identity shape exists across nightly, review-runs, running-in-ci, triage, review, and ci-fix.

Solution

Fix it once at the root and reinforce at the documented failure sites:

• running-in-ci/SKILL.md — new ### Configure git identity before the first commit subsection under PR Creation. Every skill loads running-in-ci first, so this is the canonical rule for all of them. Uses git config --global (covers the main checkout and every worktree in one shot) with the GitHub noreply email form (<id>+<login>@users.noreply.github.com) so commits stay attributed to the bot and pass verified-email push rules. Also annotated the Learning-from-Feedback worktree block to point at it.
• nightly/SKILL.md — inlined the identity config into the Step 7 verbatim ship block (the failure site in nightly: worktree commit fails on runners without a pre-seeded git identity #729). Shell state doesn't persist between bash calls, so it's self-contained there.
• review-runs/SKILL.md — annotated its worktree-commit block to set identity first.

Testing

Skill-text fix — no generator unit test applies. Reproduced the mechanism locally: git commit with no configured identity fails with Author identity unknown both in a fresh repo and a fresh worktree; setting git config --global user.name/user.email lets the same commit succeed. pre-commit (trailing-whitespace, typos, bang-backtick guard, install-tend sync) passes on all three changed files.

---

Closes #729 — automated triage

[tend-agent]

The canonical rule + the Step 7 inline are a solid root fix, and --global over the issue's repo-local git config is the right call (a fresh worktree shares the runner's ~/.gitconfig). One residual gap, though, on a site #729 explicitly named.

The conflict-resolution commits in Step 3 run before any identity is configured. "Resolve conflicts on bot PRs" dispatches parallel subagents that each git add + git commit --no-edit in a fresh git worktree add /tmp/pr-<number> — and that step executes well before Step 7, where the inline git config --global now lives. So at the moment those commits fire:

• The main session hasn't reached Step 7 yet, so no --global identity has been written to ~/.gitconfig.
• The commits run inside dispatched subagents, which are separate agent invocations and don't reliably load running-in-ci, so the new canonical rule isn't guaranteed to reach them.

That leaves the conflict-resolution git commit --no-edit — one of the three sites #729 called out — still exposed to Author identity unknown.

Because git config --global writes to the runner's shared ~/.gitconfig (filesystem state, not shell state — it persists across bash calls and across subagents in the same runner), setting it once, early in the main session — before Step 3 dispatches subagents — would cover every downstream commit site (conflict-resolution subagents, Step 7, and any later worktree dance) in one shot, strictly more robustly than placing it only at Step 7. A natural home is Step 0 right after loading running-in-ci, or just ahead of the Step 3 dispatch.

Not blocking the improvement here — just flagging for a follow-up so the fix reaches the site that was actually observed failing.