Read a Nest patch manifest before replaying it

A patch directory is not the complete replay specification. Read the ordered manifest and exact importer source before a history-changing operation.

Pin the inspected source

This example uses Nest revision 0f521ed9d85cf4f03bd5cd68a32b21528d1a5ace. Its tools/lib/patches.py reads filenames from .patches in file order, reads each file and concatenates their contents. It does not alphabetically discover every file in the directory.

Compare manifest, available files and intended base separately. A file present but absent from the manifest is not evidence this importer applies it. A missing listed file prevents reading the stated series.

Inspect without replay

1. Record Nest and patch repository revisions.
2. Read the manifest line by line, preserving order.
3. Check each listed file exists, is readable and has the intended content.
4. Flag blank entries, repeats and unlisted files for review.
5. Inspect base revision and local changes.
6. Read importer arguments and Git operations before planning a replay.

Synthetic series
.patches:
  010-focus.patch
  020-empty-state.patch

Available files:
  010-focus.patch
  020-empty-state.patch
  030-experiment.patch

Observation:
Two files are listed, in that order.
The experiment is unlisted.
No replay or behavioural success is established.

Use source-defined arguments

At this revision the importer defines -p / --patches-dir, -f / --flutter and optional -3 / --3way. The exporter also uses -p / --patches-dir; the old website’s -o patches does not match its parser.

The archived positional tools/git-import-patches patches also differs from the inspected importer. These are source observations, not an executed replay. Check your revision before using commands. A three-way option does not guarantee conflict resolution.

Track the second repository

The assembly action checks out a separate patch repository and ref. Record it alongside Nest and the Flutter base. A moving ref can resolve differently later, even when manifest text looks familiar.

For each entry retain filename, digest, inclusion reason and dependency on preceding entries. Reordering can affect applicability or meaning. Do not alphabetically tidy a series without reviewing those dependencies.

Before replay, preserve work and establish ownership of local changes. On failure retain stderr and Git state. Manifest review is preparation, not proof that patches apply, tests pass or an engine binary exists. Use the source links to inspect implementation details rather than substituting a remembered command from a historical article.

Visual procedure

Pin Nest + patch checkout; then Read ordered manifest; then Check files + arguments; then Replay is a separate gate. This is an explanatory illustration, not a test result.

Next useful step

• Investigate conflicts
• Trace the workflow