timothyandClaude Opus 5 d44d9eb55f fix(836): the guard's git fixtures must not inherit an identity from the machine ...

CI red: `git commit -q -m docs on the PR head failed: Author identity unknown`.
The fixtures set `user.email`/`user.name` on the ORIGIN repos, but the PR-arm test
commits in a CLONE, which inherited nothing. A developer checkout has a global
identity and the CI container has none, so the file was green here and red there.

Fixed at the boundary rather than the site: `_GIT_CONF` is passed to EVERY git
invocation in the file, so no repository it creates can depend on ambient config.
It also disarms a global `core.hooksPath` (which would fire this repo's husky hooks
against throwaway fixtures) and `commit.gpgsign` (which would block on a pinentry
prompt no pytest timeout is watching). The now-redundant per-fixture `git config`
calls are removed.

`_env()` additionally points `GIT_CONFIG_GLOBAL`/`GIT_CONFIG_SYSTEM` at os.devnull,
so the ambient configuration is UNAVAILABLE rather than merely overridden.

That alone did NOT reproduce CI, and the first version of this commit claimed it did:
with the identity flags removed the suite still passed here, because a Mac invents an
identity from the OS user and hostname. `user.useConfigOnly=true` is what closes it.
Verified by removing the identity pair and watching the file go red locally with the
same `Author identity unknown` CI produced — so a local run now catches this class
instead of deferring it to the runner.

Gate: ruff check + format --check pass over all 51 tracked files with the CI-pinned
0.12.11; suite 1237 passed, 2 skipped.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HETQK67q1bEpDZpHLZNsp9

2026-08-30 00:46:49 +02:00

..

fixtures

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

__init__.py

feat(521): decision-record parser (decisions_lib)

2026-07-21 02:58:58 +02:00

conftest.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

hook_fire_isolation.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

mutation_harness_lib.py

feat(790): execute every MUTATION grade instead of asserting it (#815)

2026-08-22 13:12:15 +00:00

mutation_manifest.py

fix(836): never pass --depth to a checkout that may already be complete

2026-08-30 00:46:49 +02:00

test_bom_guard_detection.py

feat(780): commit a ruff config and enforce it in CI (#813)

2026-08-22 00:33:18 +00:00

test_build_catalog_check_path.py

test(785): mutation proofs for the three unproven ranked guards (#810)

2026-08-21 20:10:01 +00:00

test_build_catalog.py

fix(603): close four defects found in adversarial review of the stale-after fields

2026-07-25 15:22:50 +02:00

test_check_doc_narrative.py

fix(812): classify the narrative sites by who-benefits; keep the detector's reach (#882)

2026-08-29 20:28:14 +00:00

test_check_required_contexts.py

fix(787): derive the dropped-step guard's scope, and reconcile its snapshot against the server (#861)

2026-08-27 22:37:02 +00:00

test_check_review_verdict.py

fix(788): one declarative H10 verdict vocabulary, derived by both sides (#846)

2026-08-26 20:58:09 +00:00

test_ci_dropped_step_guard.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

test_ci_image_pin_population.py

fix(786,789): workflows declare their own per-job metadata; guard populations derive from it (#872)

2026-08-28 20:54:53 +00:00

test_ci_release_path_scan_job.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

test_ci_status_context_uniqueness.py

fix(787): derive the dropped-step guard's scope, and reconcile its snapshot against the server (#861)

2026-08-27 22:37:02 +00:00

test_ci_toolchain_image_resolves.py

docs(772): correct the twins of two claims this branch already fixed

2026-08-23 00:23:44 +02:00

test_complete_annotation_dispositions.py

fix(820): derive where Complete<T> is APPLIED, not just what it means (#883)

2026-08-29 22:06:38 +00:00

test_decisions_lib.py

fix(688): make the n oracle dynamic; correct a tense that asserted false history

2026-08-04 22:35:00 +02:00

test_decisions_validate.py

feat(780): commit a ruff config and enforce it in CI (#813)

2026-08-22 00:33:18 +00:00

test_docs_only_detector_clone_depth.py

fix(836): the guard's git fixtures must not inherit an identity from the machine

2026-08-30 00:46:49 +02:00

test_guard_inventory.py

fix(786,789): workflows declare their own per-job metadata; guard populations derive from it (#872)

2026-08-28 20:54:53 +00:00

test_guard_populations_derive_from_git.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

test_hook_fire_log.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

test_jq_preflight.py

feat(780): commit a ruff config and enforce it in CI (#813)

2026-08-22 00:33:18 +00:00

test_mcp_smoke.py

docs(796): verification code is code under test, and the proof it was claiming an exemption from (#871)

2026-08-28 20:06:45 +00:00

test_merge_consent_base_change.py

feat(780): commit a ruff config and enforce it in CI (#813)

2026-08-22 00:33:18 +00:00

test_merge_consent_exemption.py

docs(747): re-verify the Gitea 1.25.4-pinned CI claims on 1.27.1, and measure the merge-gate semantics that were source-attested (#867)

2026-08-28 16:51:13 +00:00

test_merge_consent_head_change.py

fix(803,664): fence the HEAD alias on the PR timeline's pull_push count (#873)

2026-08-28 23:29:47 +00:00

test_merge_consent_required_check.py

fix(787): derive the dropped-step guard's scope, and reconcile its snapshot against the server (#861)

2026-08-27 22:37:02 +00:00

test_migration_equivalence.py

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

test_mutation_harness.py

feat(790): execute every MUTATION grade instead of asserting it (#815)

2026-08-22 13:12:15 +00:00

test_optional_request_members.py

fix(820): derive where Complete<T> is APPLIED, not just what it means (#883)

2026-08-29 22:06:38 +00:00

test_post_review_verdict.py

fix(772,792): address both cold reviews — an unverified pin is no longer a green job

2026-08-22 23:25:26 +02:00

test_pr_changed_files.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

test_prepush_rebase_check_tag_exemption.py

fix(743): re-tense the third stale site, and pin the two surviving mutants

2026-08-06 00:10:45 +02:00

test_prepush_unsets_git_env.py

test(785): mutation proofs for the three unproven ranked guards (#810)

2026-08-21 20:10:01 +00:00

test_prove_fix.py

feat(780): commit a ruff config and enforce it in CI (#813)

2026-08-22 00:33:18 +00:00

test_remote_state_inventory.py

fix(787): derive the dropped-step guard's scope, and reconcile its snapshot against the server (#861)

2026-08-27 22:37:02 +00:00

test_review_verdict_vocabulary.py

fix(788): one declarative H10 verdict vocabulary, derived by both sides (#846)

2026-08-26 20:58:09 +00:00

test_workflow_job_guards.py

fix(786,789): workflows declare their own per-job metadata; guard populations derive from it (#872)

2026-08-28 20:54:53 +00:00

test_workflow_persist_credentials.py

fix(744,835): ci-image.yml publishes from main only; guard persist-credentials with no exemption (#857)

2026-08-27 20:44:44 +00:00

test_worktree_ownership_guard.py

fix(809,822): isolate the suite from the production hook-fire log by construction (#874)

2026-08-29 02:32:26 +00:00

tracked_files.py

fix(806): guard populations over FILES derive from the git index, not a filesystem walk (#818)

2026-08-22 16:07:58 +00:00