Summary

Results publishing now uses the configured git identity first instead of writing AgentV Results <agentv@results-repo> into repository config. When git reports that no author or committer identity is configured, AgentV retries only that commit command with its fallback identity through per-command environment variables, leaving the user's local git config unchanged.

The git subprocess environment now keeps noninteractive auth hooks such as GIT_ASKPASS, GIT_USERNAME, GIT_PASSWORD, GIT_TOKEN, and GIT_SSH_COMMAND, while still stripping repo-state variables like GIT_DIR and GIT_WORK_TREE. The deterministic results-branch genesis commit still uses the fixed AgentV identity, but only through per-command env.

Testing

• bunx biome check packages/core/src/evaluation/results-repo.ts packages/core/test/evaluation/results-repo.test.ts
• git diff --check
• bun --filter @agentv/core typecheck
• bun --filter @agentv/core test test/evaluation/results-repo.test.ts (41 pass)

Post-Deploy Monitoring & Validation

No additional production monitoring required; this is local git commit plumbing for result publication. Healthy signals are result commits authored by the configured repo/environment identity when present, fallback AgentV Results <agentv@results-repo> authors only in no-identity environments, and no writes to git config user.name or git config user.email. Failure signals are new result PRs or result branches unexpectedly authored by AgentV despite configured identity, or missing-identity publish failures in clean CI containers. Validation window: next AgentV results-publish run or CI exercise of results-repo.test.ts; owner: AgentV maintainers.