diff --git a/docs/research/2026-08-06-c5c-closeout-handoff.md b/docs/research/2026-08-06-c5c-closeout-handoff.md index 07e5d6f8..f7c52a59 100644 --- a/docs/research/2026-08-06-c5c-closeout-handoff.md +++ b/docs/research/2026-08-06-c5c-closeout-handoff.md @@ -15,13 +15,24 @@ alarm a successor.** The campaign was merged to `main` and pushed the same day: 7b3e2895` lists `main`. **The measurement error, because it will recur.** This repo has TWO remotes. -`github` (`git@github.com:eriknihlen/acdream.git`) is the live one. `origin` -(`https://git.snakedesert.se/erik/acdream.git`) is a second remote whose cached -ref `origin/main` still points at `f6275f45` and whose ref file has not been -written since **April 27** — three months stale. `main` is 412 commits ahead of -that ref, which is where "388+ unpushed" came from. **Never measure push state -against `origin/*` in this repo without checking the ref's age first**; compare -against `github/main`, or check `git branch --contains `. +`github` (`git@github.com:eriknihlen/acdream.git`) is the primary. `origin` +(`https://git.snakedesert.se/erik/acdream.git`) is a second self-hosted mirror +that had simply not been pushed to since `f6275f45` — `main` was 412 commits +ahead of it, which is where "388+ unpushed" came from. + +**A first correction to this correction, since it was itself stated wrongly +once:** the local `origin/main` ref was NOT stale. A fresh `git fetch origin` +returned it unchanged at `f6275f45`, so the *remote* was genuinely behind; the +ref was accurate all along. The error was never a caching artefact — it was +reading a lagging MIRROR as if it were the live remote and concluding the work +was unpushed. + +**The rule:** in this repo, `origin` is a mirror and may lag arbitrarily. +Measure push state against `github/main`, or better, against the question you +actually mean — `git branch --contains `. + +**Both remotes were brought to parity 2026-08-06** by the #333/#334 merge: +`main`, `github/main` and `origin/main` are all `0ce54a5c`. ---