diff --git a/claude/memory/skill-harvest-register.md b/claude/memory/skill-harvest-register.md
index 9f8eed8..df484d4 100644
--- a/claude/memory/skill-harvest-register.md
+++ b/claude/memory/skill-harvest-register.md
@@ -753,3 +753,5 @@ Each nearly read as a defect in the *quotation*. ⚠ **Bound:** correct extracti
 **SECOND INSTANCE OF B, recorded rather than re-filed.** At the 2026-09-11 wake the daybook cue fired on a read-only command and said 'the write already succeeded'. No write had occurred. The cue now misdescribes its own trigger, as well as disagreeing with the skeleton.
 
 **NOT filed:** the vault-mirror binaries policy. It is a steward decision (the split, 2026-09-11), not a tool. It is recorded in the vault's `CLAUDE.md`.
+
+| H | **The wake's dotfiles check compares against every remote, not only the upstream.** `/wake-up` §2.c reads `git status -sb`, which sees only the tracking remote (`github`). On 2026-09-11 the second remote `gitea` (`git.skemantix.com`) was found **54 commits behind, since 2026-09-04**, a week that no wake surfaced, while memory describes the files layer as 'dual-remote'. The wrap's §6.5 `git push` reaches only the upstream. Mechanical fix: the wake digest's REPOS line reports `rev-list --count <remote>/main..HEAD` for each remote. | patch (script) | **MECHANICAL** — every wake, via `wake-digest.py`. | PROPOSED — found at the 2026-09-11 wrap. ⚠ **gitea not pushed**: a second outward-facing target the wrap's instruction does not name, so it is left for the steward (dry-run: fast-forward, would succeed). |