diff --git a/claude/memory/skill-harvest-register.md b/claude/memory/skill-harvest-register.md
index b1d1333..29497b4 100644
--- a/claude/memory/skill-harvest-register.md
+++ b/claude/memory/skill-harvest-register.md
@@ -372,3 +372,12 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **`mempalace-diagnose` — RETIRE the proposal** | retire | AUTHORIZED 2026-06-05 (build-on-need). Now **decorative**: the steward decided (evidenced) to **wind down** palace-memory MemPalace. Building a MemPalace diagnostic skill for a substrate we're leaving is the inverse of proportionate. Retire on decommission. (The reusable, substrate-agnostic instruments from tonight — measure-ETA, from-sqlite-rebuilds-only-chroma, verify-install-isn't-standard-before-upgrade — are captured as the ladder/flag entries above, not tied to MemPalace.) | skill-harvest register | **PROPOSED (retire)** |
 
 *(Three, all earned in the MemPalace session. The first two are substrate-agnostic instruments that outlive MemPalace; the third is honest housekeeping — don't build tooling for what we're decommissioning. None autonomous. Also fulfilled-not-proposed: the standing `/wrap-up §5` "mirror KG to files → palace disposable" proposal was **realized** this session as the `knowledge-graph.jsonl` export — mark it done when the decommission wires wake to read it.)*
+
+### Harvest 2026-07-08 (Fable-window allocation → V2 charter; MemPalace decommission)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **`/model-handoff` (premium-model scope charter)** | **RE-FLAG — strongly reinforced** | Proposed 2026-06-12; this session *built* a full scope charter with the discipline (charter-on-Opus → Fable spends premium tokens only on design; artifacts-not-chat; **NO /wake-up on the premium model — the charter IS the wake**) and it pays off the very next session (the bare Fable-on-V2 run). The steward-directive "next session = no wake/wrap, just the charter" is the discipline in action. Earns building. | new `/model-handoff` skill | **PROPOSED (reinforced)** |
+| **cross-volume verify-before-delete move** | verification-ladder note | Moving data across filesystems (internal→external cold archive): `rsync -a` → verify **exact file-count match + `du`** (NOT a byte-sum — mine computed 0=0 vacuously) + rsync rc=0 → only then `rm` the source. Isolate flaky-remote pushes so a hang can't block. And **check git's real exit, not a pipe's** (`… | tail` masks push failure — bit me on the dotfiles→gitea push this wrap). Proven twice today (MemPalace cold-archive). | `reference-verification-ladder.md` | **PROPOSED** |
+
+*(Both genuine — /model-handoff is load-bearing: it just proved itself and will again next session. The byte-sum-vacuous + pipe-masks-exit catches are also logged as KG drift-patterns; not manufactured.)*