1.5 KiB
[2026-09-19] Three agents commit as one git author, and closing that gap took three instruments to get right.
⭐⭐⭐ Three agents commit as one git author, and closing that gap took three instruments to get right. An unattributable commit (e43e262) appeared in the push set between two of mine — unidentifiable from git (all commits are Vuong Hoang by convention), from the ops log (host changes only) or from the bus. Turned out to be infra-hermes; forseti disclaimed it and the files' own ~/.hermes/hermes-agent imports gave it away. Three fixes, each exposing the next: (1) 0dc8e90 a post-commit hook recording the althing handle; (2) 4e778ae its fallback said lkraven@nh3-dev, which reads like an answer while being the absence of one — now unattributed(login), and handles never contain @ or parens; (3) 9141a41 the hook was appended behind graphify's eight exit 0 paths, so a graphify-out/-only or empty commit could NEVER be recorded. ⚠ Root cause was control flow, not the lock race proposed — see feedback_control_flow_before_concurrency. Attribution must run FIRST, never behind another hook's interestingness filter. ⚠ Also: ALTHING_HANDLE lived only in althing-infra-hermes-seat-run.sh, not in hermes-gateway.service / the pump unit — hermes fixed it with drop-ins. ⚠ systemctl show -p Environment reports the CONFIGURED env, not the running process's — it read correct while /proc/<pid>/environ did not have the variable at all. Check the process, never the config.