patch1.2 KB

Git Format-Patch Series - 0002 of 3

Patch 2 of a three-message series, threaded under the cover letter with In-Reply-To and References headers. Applying the three out of order breaks: the series is only self-consistent in numeric order.

Visual diff / regression Code parsing Editor testing

Preview — first 42 linespatch

From ee74572dbf48ad511e3367f43bd88bf25c87615b Mon Sep 17 00:00:00 2001
From: Ada Fernsby <ada.fernsby@example.invalid>
Date: Mon, 2 Mar 2026 09:31:50 +0000
Subject: [PATCH 2/3] feat(ledger): add banker's rounding helper
In-Reply-To: <024f75262757878b20f7a3e64c1472d87a75d6b8.1772442000.git.ada.fernsby@example.invalid>
References: <024f75262757878b20f7a3e64c1472d87a75d6b8.1772442000.git.ada.fernsby@example.invalid>

Half-up rounding drifts the balance upward over long runs.

Signed-off-by: Ada Fernsby <ada.fernsby@example.invalid>
---
 internal/ledger/rounding.go | 17 +++++++++++++++++
 1 file changed, 17 insertions(+), 0 deletions(-)
 create mode 100644 internal/ledger/rounding.go

diff --git a/internal/ledger/rounding.go b/internal/ledger/rounding.go
new file mode 100644
index 0000000..d6f0c19
--- /dev/null
+++ b/internal/ledger/rounding.go
@@ -0,0 +1,17 @@
+package ledger
+
+// HalfEven rounds a minor-unit amount to the nearest multiple of step using
+// banker's rounding, which keeps long runs of postings from drifting upward.
+func HalfEven(minor, step int64) int64 {
+	if step <= 1 {
+		return minor
+	}
+	q, r := minor/step, minor%step
+	switch {
+	case 2*r > step:
+		q++
+	case 2*r == step && q%2 != 0:
+		q++
+	}
+	return q * step
+}
-- 
2.43.0

Specifications

Seed: 20260807
Series Position: 2/3
Files: 1
Threaded: true
In Reply To: cover letter
Line Endings: LF
Encoding: UTF-8

Testing contract

Expected to pass

Scenario: Apply message 2 of a threaded series in sequence with its siblings.
Expected result: The subject prefix parses as 2 of 3 and the message threads under the cover letter's Message-ID.

What is a .patch file?

A .patch file is a unified diff packaged for transmission, most often as produced by `git format-patch`. Beyond the diff itself it carries an email-style header with the author, date, and commit subject, a commit message body, per-file `diff --git` headers recording renames and mode changes, and hunk headers of the form `@@ -old,count +new,count @@`. Applying it reconstructs a specific change against a specific before-state.

How to use this file

Use an example .patch file to test patch application, code-review renderers, and diff parsers — exercising renames, mode changes, binary hunks, added and deleted files, and the `\ No newline at end of file` marker that naive parsers silently drop.

How to use this file for testing

“Git Format-Patch Series - 0002 of 3” is a deterministic Novus Examples fixture for Visual diff / regression, Code parsing, Editor testing. A/B image twins with controlled pixel changes, anti-alias variants, and UI chrome crops for screenshot diff and visual regression tools.

Documented properties for this file: seed 20260807 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Diff and patch fixtures name their target paths and the exact edge case they exercise — rename, mode change, binary hunk, CRLF↔LF, or missing trailing newline. Apply or render them against the documented before-state; every author, path, and hash is fictional.

Treat A/B twins as a visual regression unit: run your pixel or perceptual diff, assert a non-zero delta on the changed twin, and keep thresholds calibrated against the documented change kind in specs.