fix(report): surface qps/tps/seeds after git_sha; track package git_sha

[nvzhihanj]

Summary

Two fixes to the benchmark report (Report / result_summary.json).

1. qps/tps/seeds surfaced after git_sha

They previously serialized at the bottom of result_summary.json (msgspec serializes in field-definition order and defaulted fields must come last). Report.to_json now reorders the serialized mapping so the head reads version, git_sha, qps, tps, seeds, …, with the long metric dicts trailing. Reordered at serialization time (not the struct), so no impact on the existing direct-Report(...) construction tests.

2. git_sha now reflects the endpoints package, not the caller's cwd

get_git_sha() ran git rev-parse in the process cwd, so a benchmark launched from an unrelated git repo (e.g. a mounted workdir) recorded that repo's SHA. Now:

• anchored to the package directory — dev/editable checkouts report the endpoints HEAD regardless of cwd;
• reads _git_archival.txt, substituted by git archive export-subst (sdist/container builds carry no .git) — verified the substitution works;
• resolution order: baked archival SHA → package-anchored git rev-parse → None (never a wrong cwd SHA).

Tests

• to_json key order (qps/tps right after git_sha).
• git_sha: archival substitution, placeholder-never-leaks, cwd-independence.
• 27 unit tests pass; ruff format clean.

Based on main (PR #372 still open; whoever merges it has a trivial to_json/report.py resolution).

🤖 Generated with Claude Code

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[gemini-code-assist]

Code Review

This pull request introduces a mechanism to resolve the package's git commit SHA using git archive's export-subst feature via a new _git_archival.txt file, falling back to running git rev-parse anchored to the package directory. It also reorders the serialized JSON output of metrics reports to surface key throughput and run identity fields first. Feedback is provided regarding a potential issue where git rev-parse could traverse up to a parent repository if the package is installed in a virtual environment within an unrelated git repository, along with a suggestion to check for the existence of the .git directory first.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If the package is installed as a standard non-editable package (e.g., from a wheel or sdist) inside a virtual environment, and that virtual environment is located within an unrelated git repository, running git rev-parse with cwd=_GIT_ARCHIVAL.parent will traverse up the directory tree and find the parent project's .git directory. This will cause get_git_sha() to incorrectly return the host project's git SHA instead of None.

To prevent this, we should verify that the package's own repository root contains a .git directory/file before attempting to run git rev-parse.

Suggested change

	try:
	result = subprocess.run(
	["git", "rev-parse", "--short=7", "HEAD"],
	if not (_GIT_ARCHIVAL.parent.parent.parent / ".git").exists():
	return None
	try:
	result = subprocess.run(
	["git", "rev-parse", "--short=7", "HEAD"],