patch726 B

Git Format-Patch Series - 0000 Cover Letter

The `--cover-letter` message git writes ahead of a series: a `[PATCH 0/3]` subject, a shortlog of the authors and their subjects, and the combined diffstat — but no diff of its own. Series tooling has to recognise it as metadata and not try to apply it.

Visual diff / regression Code parsing Editor testing

Preview — first 24 linespatch

From 024f75262757878b20f7a3e64c1472d87a75d6b8 Mon Sep 17 00:00:00 2001
From: Ada Fernsby <ada.fernsby@example.invalid>
Date: Mon, 2 Mar 2026 08:59:00 +0000
Subject: [PATCH 0/3] ledger: zero-delta postings and rounding drift

Three small changes from the reconciliation review. Patch 1 is the
behaviour fix; patches 2 and 3 are follow-ups that can be dropped.

Ada Fernsby (2):
  feat(ledger): treat a zero delta as a no-op
  feat(ledger): add banker's rounding helper

Priya Raman (1):
  docs: rename README to guide

 docs/{README.md => guide.md}    |  0
 internal/ledger/apply.go        |  9 +++++++--
 internal/ledger/rounding.go     | 16 ++++++++++++++++
 3 files changed, 23 insertions(+), 2 deletions(-)
---
-- 
2.43.0

Specifications

Seed: 20260807
Series Position: 0/3
Files: 0
Has Diff: false
Shortlog In Body: true
Line Endings: LF
Encoding: UTF-8

Testing contract

Expected to pass

Scenario: Ingest a patch series and identify which message is the cover letter.
Expected result: The 0/3 message is classified as a cover letter and skipped by the applier; the remaining three are applied in numeric order.

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 - 0000 Cover Letter” 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.