fix(review-evidence): pin attribute case policy

Author: MrScripty

docs/plans/review-evidence-packaging/execution-ledger.md

@@ -179,3 +179,45 @@ Exact-current-source locked CI and independent repair review remain pending; the
 plan is not Accepted. Final structural/generator checks and artifact reconstruction
 are retained with the delivery after record/manifest finalization. No source push
 or user configuration edit is made by this task.
+
+## Residual F4 case-policy repair — 2026-09-28
+
+The user authorized the remaining repair under this existing plan. Admission is
+`verify` from Verifying: the repair stays inside P2's P1-boundary repair allowance.
+The source baseline is `143c8de1706ccf4b82b5c78aeed644c071ed999a`, confirmed as main;
+its Actions source archive and tree were verified in an isolated task checkout.
+No user working tree, production configuration or remote ref is a write target.
+
+Exact write set: `tools/repository_git/repository_git/repository.py`, its existing
+`tests/test_exact_patch.py` and README; the direct builder's existing
+`tools/review_evidence/tests/test_repair_boundaries.py` and README; this plan's
+plan/issues/ledger plus `reports/attribute-case-verification.md`; and the owning
+generated suite-input manifest. No other production owner or public type changes.
+
+The deciding regression uses committed `*.TXT -diff`, a nonmatching `data.txt` and
+an exact-matching `MATCH.TXT`, with the same revision pair under each local case
+setting. Literal text-hunk and binary-marker oracles complement equality of the
+actual CLI's complete packet bytes. Each invocation must preserve source, index,
+refs, request and repository configuration. Both tests are first run against the
+unmodified production method. Required supported-runtime CI and independent review
+remain distinct from local evidence; no broader test-hardening slice is admitted.
+
+### F4 case-policy local verification
+
+The two final baseline regressions failed exactly where a lowercase path became
+binary under `core.ignoreCase=true`; they passed after the command-local override.
+The complete builder/Git/metadata selections and shared Engine selection total
+161 passes and one permission-dependent skip (162 run), with no failures. Both
+source-preservation assertions and positive exact-case binary behavior passed.
+The real routing packet is byte-identical to the prior inspected output, including
+its manifest and two material gaps. A separate stdlib recipient verified all 98
+members, hashes/modes and 96 links without source access or extraction.
+
+The production change remains one Git setting plus its docstring. No normal Git
+behavior, user configuration, Engine interface, packet schema or earlier safety
+repair changed. Final records and generated inputs receive their own freshness and
+structural checks. Supported locked CI, independent narrow review and acceptance
+owner disposition remain P2 gates; source is not marked Accepted. Detailed evidence
+and the initial test-draft failures are preserved in the case-policy report and
+delivery logs. The task-owned branch/workspace is retained for delivery, not pushed
+or represented as a production source commit.

docs/plans/review-evidence-packaging/issues.md

@@ -64,3 +64,18 @@ F4 direct-consumer completion: `cli.py` now exposes only the new Git owner's fix
 arbitrary Git stderr private. The actual CLI test verifies the useful rejection,
 unchanged source configuration and no output creation. This narrow consumer repair
 and its added regression are included in the final 48-test builder pass.
+
+## Residual F4-C1 — committed attribute case matching
+
+The follow-up review of `143c8de1` found that `*.TXT -diff` changes the patch for
+`data.txt` when the same repository is configured with `core.ignoreCase=true`.
+The scoped repair fixes case-sensitive matching in the existing opt-in
+`revision_patch` command, without rewriting configuration, renaming paths, or
+changing ordinary capture/publication. Exact-case matching still selects binary
+patches. The original F1–F3 repairs are unchanged.
+
+Two new real-Git/CLI tests first failed at the intended textual-hunk assertion on
+the unchanged production baseline; the repaired candidate rerun, package checks
+and packet comparison are recorded in [case-policy verification](reports/attribute-case-verification.md).
+F4-C1 is implemented; candidate CI and independent review/owner disposition remain
+required before the packaging slice is Accepted. This adds no new API or mode.

docs/plans/review-evidence-packaging/plan.md

@@ -2,7 +2,7 @@
 
 **Plan status:** `Verifying`
 
-**Current phase:** P1 repairs implemented and locally verified; P2 CI/review acceptance pending
+**Current phase:** P1 repairs including F4 case policy locally verified; P2 CI/review acceptance pending
 
 **Next slice:** **P2 — Offline recipient example and acceptance**
 
@@ -16,9 +16,11 @@
 
 **Admission:** priority **4** in the user's selected **2 → 4 → 3** sequence.
 Routing-fact ergonomics is Accepted; the earlier six-slice refactor is closed.
-This new plan does not reopen either acceptance. The user has authorized repair of the four demonstrated review findings at this
-exact plan path. The admitted `start` is implemented; `verify` continues its P2 qualification; it does not
-reopen prior acceptance or admit priority 3. This candidate is based on `6be1d7a0`.
+This new plan does not reopen either acceptance. The user authorized the original four repairs and the follow-up F4 case-policy
+correction at this exact plan path. The admitted `start` is implemented; `verify`
+continues P2 qualification without reopening prior acceptance or admitting priority 3.
+The case-policy repair is based on integrated source `143c8de1`; earlier repair
+evidence remains in its original records. See [case-policy verification](reports/attribute-case-verification.md).
 
 ## Implementation scope amendment
 
@@ -158,7 +160,10 @@ commit-to-commit arguments and stable raw/NUL path output. Do not run `git archi
 as the byte oracle because export attributes may omit or rewrite blobs. Never
 fall back to checkout bytes, shallow diffs, text-only excerpts or permission guesses.
 Pin patch attribute lookup to the candidate commit so dirty worktree attributes
-cannot change the representation of the selected committed patch. Disable global,
+cannot change the representation of the selected committed patch. Match those
+patterns case-sensitively over exact committed paths with a command-local
+`core.ignoreCase=false`; preserve the repository's filesystem configuration and
+all ordinary Git operations. Disable global,
 system and configured attributes; reject info attributes and local custom diff
 semantics that would override committed input. Fix ordinary diff formatting at the
 existing Git owner and observe stable configuration before/after the command.

docs/plans/review-evidence-packaging/reports/attribute-case-verification.md

@@ -0,0 +1,147 @@
+# Attribute case-policy repair verification
+
+**Status: locally verified; exact-candidate locked CI and independent review/owner
+acceptance remain pending.** This is residual F4-C1 within the existing packaging
+plan, not a new implementation sequence.
+
+## Baseline, owner and change
+
+The connected repository reports main at
+`143c8de1706ccf4b82b5c78aeed644c071ed999a`, tree
+`bb2876f0251243b1d7d38b7ee1026c080394a08e`. Its mounted Actions source artifact
+`11003765805` was verified against archive SHA-256
+`509e9b6b38904ae388c121326acf4e2040d4e88b91fe50730f55518584f5b6ba` and checked out
+on a task-owned repair branch. The user authorized this remaining repair from the
+follow-up source review. No later or unrelated user working-tree content was used.
+
+Production change is confined to `GitRepository.revision_patch`: add the command-
+local setting `core.ignoreCase=false` and document its meaning. The existing Git
+owner now matches candidate-committed attribute patterns case-sensitively over
+exact Git paths. Neither the repository's filesystem-compatibility setting nor
+ordinary reads, worktree operations, capture or publication defaults are changed.
+
+The complete patch still supports binary data, exact modes and committed attribute
+choices. Case-sensitive matching does not mean disabling attributes: `*.TXT -diff`
+continues to select a binary patch for `MATCH.TXT`, but not for `data.txt`.
+Existing local-only execution, custom-driver rejection, info-attribute admission,
+output bounds and command lifetime remain intact. The prior directory-handle,
+common-Git-root and portable-component repairs were not modified.
+
+No Engine interface, packet format, public signature, schema, metadata key, CLI
+flag, migration or additional abstraction is introduced. Engine interface 45 and
+packet format 1 remain unchanged. There is no source/evidence/provider network
+operation added to the builder.
+
+## Deciding evidence
+
+Two regression methods were added at the existing owners:
+
+- `test_exact_patch.ExactPatchTests.test_attribute_case_policy_is_fixed_without_reconfiguring_repository`
+  invokes the original public Git adapter using real commits under repository
+  settings false and true. It compares the lowercase path's hunk to a literal
+  expectation built from independently observed blob IDs and exact file bytes,
+  and requires the exact-case file's binary patch marker. It checks unchanged
+  source, Git index, refs, HEAD and configuration after each operation.
+- `test_repair_boundaries.ReviewRepairTests.test_cli_packet_case_policy_preserves_material_and_repository_configuration`
+  invokes the actual CLI in replacement processes with the same request and
+  selected commits under both settings. It checks successful outcomes, exact
+  baseline/candidate source members, literal text and positive binary-policy
+  oracles, identical complete ZIP and manifest bytes, no leftover staging files,
+  and unchanged request/source/index/refs/configuration.
+
+Both final regression definitions first failed on the unmodified production code
+at the intended text-versus-binary assertion (two failures, no errors), then passed
+with the one-setting correction. An earlier test draft also emitted secondary list-
+index errors after a failed subtest; the draft was corrected before the final
+baseline rerun. Both original logs remain in the delivery evidence and are not
+counted as successful verification. The existing command-environment test also
+asserts that the case policy is passed only on the owned patch invocation.
+
+An initial task-routing probe supplied an undeclared `console` profile and was
+correctly rejected; it was corrected to the registered `library` profile before
+implementation. The executed Router then selected 21 standards with no unanswered
+facts. This was task setup, not a production failure or acceptance test.
+
+## Executed checks
+
+| Selection | Observed result |
+| --- | --- |
+| Complete review-evidence package | 49 passed |
+| Complete Repository Git package | 40 passed; one permission-dependent skip (41 run) |
+| Complete metadata package | 43 passed |
+| Engine capture-handoff, replacement-stdio and generated-contract selections | 29 passed |
+| Total selected executions | 161 passed, one skipped, no failures (162 run) |
+| New regression methods | Two; included in the totals above |
+| Complete structural checkpoint | 73 suites / 121 checks passed |
+| Generated projection freshness | Passed |
+| Separate offline recipient comparison | All members byte-identical to the previously inspected example |
+
+The full Engine and other supporting-package suites were not rerun. The production
+change is an opt-in patch setting with one builder consumer; the complete affected
+Git/builder packages and existing shared capture/contract cases are the selected
+regression scope. New tests are not added to totals a second time when rerun.
+After final documentation and manifest regeneration, the new regressions, command-
+environment check, freshness and structural checks are repeated; exact final
+outcomes are preserved in `DELIVERY/evidence/final-checks.json`.
+
+## Actual review packet
+
+The committed routing example was rebuilt through the CLI. A separate standard-
+library-only recipient process inspected the ZIP without importing the builder,
+reading the source checkout or extracting files. It checked all inventory member
+names, regular inert modes, lengths, hashes and index targets, and compared every
+member byte with the prior inspected packet.
+
+The result has 98 members, 96 resolving index links, 49 primary changed paths,
+54 selected paths, 5,704,505 payload bytes and the complete 1,083,975-byte primary
+patch. Its manifest is unchanged:
+`sha256:30c2834feb20fa7c3d4efa16b12dae823a4341de4b41aff40fe6a672fef11ff3`.
+The CLI returns `built-with-gaps` and exit 1 as intended: raw CI log missing, CI URL
+referenced. Those gaps were not filled with fabricated results. This compares a
+real packet; it does not reopen routing-fact acceptance or assert CI execution.
+
+The unchanged packet manifest's implementation digest remains explicitly a digest
+of `packet.py`, not of its Git dependency or the whole builder. No stronger origin
+or implementation-authentication claim is made by this comparison.
+
+## Scope, limitations and integration
+
+Only `repository.py` changes production code. The two direct test files, two
+READMEs, plan/ledger/issues, this report and generated suite-input manifest form
+the coordinated delivery. All Engine contracts/runtime, packet schema/source,
+existing normative guidance, dependency locks and CI configuration remain unchanged.
+Fresh-baseline reconstruction checks the entire resulting tracked tree, individual
+file hashes and modes; ZIP integrity and reconstruction results are in DELIVERY.
+
+Handoff execution used Linux x86-64, CPython 3.13.5, Git 2.47.3, jsonschema 4.26.0
+and rpds-py 2026.5.1. No supported Python 3.12 hash-locked environment was installed there.
+The skipped case requires unprivileged POSIX permissions; no case-insensitive
+filesystem or additional operating system was exercised. The fixed policy concerns
+committed-path interpretation, not reconfiguration of filesystem compatibility.
+The tests establish these configured cases, not harmlessness of every Git setting.
+The existing requirement that configuration remain stable during observation and
+the documented local-directory threat limits are unchanged.
+
+Apply the scoped patch after its read-only baseline check, preserving unrelated
+work. No registration or repository Git configuration changes are needed. Fresh
+builder invocations load the corrected code. Keep historical packets and reports
+unchanged. The plan remains Verifying: obtain supported locked-runtime CI for the
+actual integrated candidate, narrow independent repair review and acceptance-owner
+disposition. No remote push, production commit, standards publication, host update,
+provider request or independent external review was performed during handoff preparation.
+
+After integration on the named base, the repository's Python 3.12.3 environment
+passed 49 Review Evidence tests, 41 Repository Git tests, 43 Standards Metadata
+tests and the 29 selected Engine tests. Ruff lint on changed Python, the complete
+structural check and authoring-purpose repository verification (121 checks across
+73 suites) also passed. A separate ZIP inspection found 98 members, 96 resolving
+links, the complete 1,083,975-byte patch, and the same two declared evidence gaps;
+the manifest digest remained `sha256:30c2834feb20fa7c3d4efa16b12dae823a4341de4b41aff40fe6a672fef11ff3`.
+These local results do not replace hosted CI or acceptance-owner disposition.
+
+## Corroborating dependency contract
+
+Git documents command-local configuration precedence and identifies `core.ignoreCase`
+as a filesystem-compatibility setting. The operation-local override intentionally
+does not edit that stored value. Official reference:
+https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreignoreCase

evaluation/standards-effectiveness/generated/suite-inputs.json

@@ -6578,7 +6578,7 @@
       ]
     },
     {
-      "digest": "sha256:4ef1153a4609ba5c1f50d9b2039291b76fafe8b16ca9147ced03eb550a0aac86",
+      "digest": "sha256:95f201111583e2c57988f0cf705b2fdf8ed1e4508b674329adde674494aa9c10",
       "path": "tools/repository_git/repository_git/repository.py",
       "state": "present",
       "uses": [
@@ -13838,7 +13838,7 @@
     "path": "evaluation/standards-effectiveness/suite-registry.toml"
   },
   "repository_index": {
-    "digest": "sha256:0b1e103a4ea4291c6d86d0e0c7cde7a5feace5de5032dc255016455f371176b7",
+    "digest": "sha256:2d9c15d4bb3d841ab46ab68c45edaf0cac663725aa24231f464ecb1c7393756e",
     "uses": [
       {
         "check": "python-package-contract",

tools/repository_git/README.md

@@ -119,6 +119,11 @@ The patch policy fixes algorithm (Myers with indent heuristic), three context
 lines, zero inter-hunk context, `a/`/`b/` prefixes, no line prefix, default line
 indicators, byte-path quoting, raw file ordering, short submodule format and the
 512 MiB Git binary-detection threshold (above the object safety bound). It preserves
-committed attribute choices; it does not replace binary patches with text excerpts.
+committed attribute choices with case-sensitive matching over exact Git paths.
+The owned patch command sets `core.ignoreCase=false` only for that invocation;
+repository filesystem settings remain untouched. Thus `*.TXT -diff` does not match
+`data.txt` but still selects a binary patch for `MATCH.TXT`, regardless of the
+repository's `core.ignoreCase` value. It does not replace binary patches with text
+excerpts or change ordinary reads, worktree operations or publication behavior.
 Different Git implementations may produce different binary encodings; byte identity
 is qualified within the recorded implementation/environment, not across versions.

tools/repository_git/repository_git/repository.py

@@ -386,8 +386,10 @@ def revision_patch(
         info/attributes higher precedence than GIT_ATTR_SOURCE, so that override
         is explicitly unsupported rather than silently trusted or edited.
         Custom local diff-driver semantics are likewise rejected; external and
-        textconv commands are disabled and never invoked. Admission is repeated
-        after the command; configuration must remain stable for the observation.
+        textconv commands are disabled and never invoked. Attribute matching is
+        case-sensitive over committed paths, independent of filesystem case
+        settings. Admission is repeated after the command; configuration must
+        remain stable for the observation.
         """
         if type(max_output_bytes) is not int or max_output_bytes < 1:
             raise invalid("REPOSITORY_GIT.INVALID_BOUND", "patch bound must be positive")
@@ -420,7 +422,7 @@ def admit_configuration() -> None:
                             "GIT_ATTR_NOSYSTEM": "1", "GIT_ATTR_SOURCE": candidate.oid})
         settings = (
             "core.attributesFile=" + os.devnull, "core.quotePath=true",
-            "core.bigFileThreshold=512m", "core.fsmonitor=false",
+            "core.bigFileThreshold=512m", "core.fsmonitor=false", "core.ignoreCase=false",
             "diff.suppressBlankEmpty=false",
         )
         configuration = tuple(part for setting in settings for part in ("-c", setting))