From 4e7d99064e1ebc5ab088a1968685f8e372c4deb6 Mon Sep 17 00:00:00 2001 From: Tony0410 <47945770+Tony0410@users.noreply.github.com> Date: Wed, 30 Sep 2026 19:55:41 +0800 Subject: [PATCH] wiki: document vault repo git object-permission quirk + 2026-09-30 object recovery --- systems/hermes-agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/systems/hermes-agent.md b/systems/hermes-agent.md index 9682941..470398c 100644 --- a/systems/hermes-agent.md +++ b/systems/hermes-agent.md @@ -130,6 +130,7 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi - Daily Marketing Job Radar pinned to a model its upstream plan rejects (`gpt-5.6-terra` → 403 `MODEL_NOT_IN_PLAN`). See [[systems/scheduled-tasks]]. - Telegram thread delivery failures on `telegram:1793951355` (thread `34795` not found). - **Two wiki trees drift:** `/home/hermes/workspace/agent-estate-wiki` (Gitea + Quartz source, pages at root) and `/home/hermes/wiki/agent-estate-wiki` (Obsidian/Ignis vault, pages under `wiki/`). They are separate git repos with different history. See [[current-state]]. +- **Vault repo git objects can be unwritable:** `/home/hermes/wiki/.git` still holds root-owned object fanout dirs/objects (`04`, `42`, `82`, `91`) left by root-run maintenance commits on 2026-07-22. When a new blob or tree hashes into one of those fanouts, `git commit` dies with `insufficient permission for adding an object to repository database` (even though `git add`/`write-tree` look fine). Workaround that works: build the objects in a writable store via `GIT_OBJECT_DIRECTORY=` + `GIT_ALTERNATE_OBJECT_DIRECTORIES=/home/hermes/wiki/.git/objects`, then `git pack-objects /home/hermes/wiki/.git/objects/pack/pack-` and move the branch with `git update-ref refs/heads/master `. Permanent fix is a root `chown -R hermes:hermes /home/hermes/wiki/.git`. Do **not** run overwrite/rename probes against `.git/objects`: on 2026-09-30 one such probe overwrote loose tree `0d23eba37eb65f5e5021f558a370358f1e394c58` (breaking the 2026-07-22 commit `9141a88`); it was reconstructed byte-exactly from its parent tree `d8185c99` plus the two replaced children (`comparisons` tree `822b90a7`, `log.md` blob `043dc1cd`) and reinserted, and `git fsck` is clean again. - Browser persistence not yet fully verified ## Related