Link the GitHub branch now that it is pushed

README.md

@@ -15,7 +15,7 @@ size_categories:
 # Pricing AutoPipeline — outer-loop ablations (v2r, v4, v5, v6)
 
 Full run artifacts for four component ablations of the pricing AutoPipeline described in
-[`MikeDeng2002/from-survey-histories-to-interpretable-digital-twins`](https://github.com/MikeDeng2002/from-survey-histories-to-interpretable-digital-twins).
+[`MikeDeng2002/from-survey-histories-to-interpretable-digital-twins`](https://github.com/MikeDeng2002/from-survey-histories-to-interpretable-digital-twins), branch [`outer-loop-ablations`](https://github.com/MikeDeng2002/from-survey-histories-to-interpretable-digital-twins/tree/outer-loop-ablations).
 
 Each version freezes the entire procedure, changes exactly **one** component, and measures the
 effect on the same endpoint. The question is which part of an "interpretable mechanism" pipeline
@@ -118,8 +118,9 @@ v6/         requests.jsonl  sidecar.json  cells_v6.csv     batch_output.jsonl  b
 
 ## Reproducing
 
-Code, protocol, per-version hypothesis cards, freeze specifications and ledgers live on the
-GitHub branch. The builders are deterministic — `runs/RUNNING.md` records the expected
+Code, protocol, per-version hypothesis cards, freeze specifications and ledgers live on branch
+[`outer-loop-ablations`](https://github.com/MikeDeng2002/from-survey-histories-to-interpretable-digital-twins/tree/outer-loop-ablations); start from
+[`runs/RUNNING.md`](https://github.com/MikeDeng2002/from-survey-histories-to-interpretable-digital-twins/tree/outer-loop-ablations/runs/RUNNING.md). The builders are deterministic — it records the expected
 `input_sha256` for each version, so a fresh checkout can be verified before spending anything on
 the API.