wrap-uplisted

# wrap-up The full closeout, in one pass: what the session learned becomes permanent, what it produced becomes documented, and the result lands on the remote with the tree clean and the branch correct. It runs three existing skills rather than reimplementing them. Each owns its own procedure and its own gates; this skill owns the **order**, the **handoffs**, and the **guards** that only make sense across the whole chain. ``` fetch → reflect → notes → commit → reconcile → push → branch parity (memory) (docs) (repo-device-sync) ``` ## Why this order Each step's output is the next step's input, so the sequence is not arbitrary. 1. **Fetch before anything.** Inbound commits from another machine can change what is true. Reconciling the session against stale state produces memory entries and doc corrections that are wrong on arrival. This is the one place the obvious order (work first, git last) is wrong. 2. **`reflect` before `notes`.** Reflect corrects stale claims wherever they live. Notes then documents the session against a record that is already accurate. Reversed, notes writes up claims reflect is about to overturn. 3. **`notes` before commit.** The docs sweep changes files. Committing first means committing twice or amending. 4. **Commit before push, with a second fetch between.** The fetch from step 1 is stale by now; another machine may have pushed during the session. 5. **Branch parity last**, because it advances