From bde10f8948d13455d0f23bf0fe1b8c7beb14f358 Mon Sep 17 00:00:00 2001 From: Frank Date: Sun, 18 Oct 2026 17:16:49 -0700 Subject: [PATCH] docs: work-log entry for noctalia bar clobber + dangling-stash recovery Documents the 16:46 layout loss (uncommitted GUI state stashed, stash entry destroyed during trunk sync) and the git-fsck recovery landed in c87b378. Lesson codified in managed skills. --- omp-docs/log.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/omp-docs/log.md b/omp-docs/log.md index db60c72..982e6f3 100644 --- a/omp-docs/log.md +++ b/omp-docs/log.md @@ -11,6 +11,10 @@ timestamp: 2026-08-28 # Bundle Change Log +## 2026-10-18 — Noctalia bar layout clobbered by trunk-sync stash, recovered from dangling objects + +Frank's months of GUI-built bar customizations (cat/clock/clock-utc/weather start, taskbar center, capsule groups g1–g4, control-cheat-sheet, thickness/font-scale/opacity styling) vanished from the live bar at 16:46. Root cause: the layout existed **only in the working tree** — the repo copy of `settings.toml` carried a stale plain layout because GUI edits hadn't been committed inside the hourly heartbeat window — and a trunk-sync session clearing the dirty tree for `origin/main` stashed it; the stash entry was subsequently destroyed (three `WIP on main` stashes within 60 s, all later dropped). Recovery: `git fsck --lost-found` surfaced the destroyed stash as dangling commit `7fe3ed8` (16:46:09); candidate validated in a sandboxed `XDG_*_HOME` before restore, clobbered file preserved to `.AGENTTRASH/`, layout restored through the symlink target and proven by screenshot, committed as `c87b378` — the durable copy the layout never had. Lessons codified into managed skills: trunk-sync must preservation-**commit** every dirty deployment path (never stash, never `stash clear`), and GUI layout edits get committed the same session they're made. + ## 2026-10-18 — Fleet law: issue/PR attribution footers Every agent-opened issue and PR body now ends with a `cwd:` + `session:` footer (session id from `/status`), in AGENTS.md of both `dank/command-center` and `dank/serverAppConfigs` (mirrored PRs). Born from the live-sync review: once the machine starts filing and committing on its own, its artifacts must trace back to the box and session that produced them.