The reading CLI surface test fixture commits without pinning a git identity, relying on an ambient system-level user.name/user.email that a CI runner does not have, so eleven tests fail with 'Author identity unknown' on CI while passing on any developer machine; gittest.Env deliberately does not pin an identity and its doc says callers must supply their own, which lint_surface_test.go does and reading_surface_test.go does not

The reading CLI surface test fixture commits without pinning a git identity, relying on an ambient system-level user.name/user.email that a CI runner does not have, so eleven tests fail with 'Author identity unknown' on CI while passing on any developer machine; gittest.Env deliberately does not pin an identity and its doc says callers must supply their own, which lint_surface_test.go does and reading_surface_test.go does not

Grounds

• pursued: a test fixture that resolves its commit identity from whatever the machine happens to supply is green everywhere it is written and red only where it is verified, which is the worst place to learn it. What would show this wrong is a runner that legitimately needs the developer's own identity in a fixture commit, which no test here does.