Case study: first bad release change
The duty lead at Willow Dispatch needs evidence, a specific diagnosis and a verified repository repair. All remote and review behavior is simulated. The final conclusion must agree with the supplied history.
Investigate a first bad release change in an original team repository. The duty lead needs a checked conclusion and a narrow repair that preserves the other work. Inspect history before choosing a command. A plausible final file can hide a lost commit or the wrong reference, so the checks include both data and history. Keep evidence in the repository metadata folder to avoid adding it to the product snapshot. Each step carries the prior state, and the final result must retain the records you created earlier. Use the local graph to explain the integration or recovery boundary.
git branch investigation-baseline
Start by preserving or inspecting the original repository state.