Record an OSS Replay Packet Before Model Dissent

Description and use

An OSS replay packet records the failure context and patch so any reviewer can reproduce the issue and verify the fix before requesting model dissent.

Problem

Open‑source fixes fail when review context lives only in a chat window; later readers cannot replay the bug, diff, or prompt.

Outcome

The workflow produces a reproducible, version‑controlled review packet that allows any reviewer to replay the failure and patch, request only dissent from a model, and score the dissent against a trusted oracle checklist.

Workflow

• Pin the upstream commit on a clean worktree
• Capture the failing command and record stdout, stderr, and exit code
• Apply the minimal human patch and generate a patch file
• Write the manifest.json with project, commit, commands, and patch references
• Replay the failure and patch on a clean server, recording pass/fail outputs
• Ask the model only for dissent notes, providing manifest, patch, and oracle checklist
• Score the dissent notes against the oracle checklist to confirm, reject, or flag untested notes

Evidence

A model review is useful only after a frozen replay packet exists. That packet stores the pinned commit, the failing command, and the patch.

Source

Open-source fixes fail when review context lives only in a chat window. A later reader cannot replay the bug, the diff, or the exact prompt.

Source

The packet stays small enough to copy onto a clean server. It stores inputs, commands, and the expected local result.

Source