Rebuild dotfiles as one branch with per-host layers

Replaces the previous repo, which had split into two histories that never
met (mainframe on a dead GitLab remote, the laptops on Gitea) with 146
dirty files across three machines and the NAS never enrolled at all.

Branch-per-machine is gone. One main, with host differences expressed as
small files under hosts/<hostname>/ rather than as branches, so there is
nothing to merge. The reconciled zsh layer reduces 15-33 line forks to
1-7 effective lines per host; distro differences (oh-my-zsh prefix,
syntax-highlighting path, fd vs fdfind) are probed in common/ instead.

Fresh history: the old one carried six plaintext credentials, 45 MB of
mail caches, browser caches and vendored binaries. 5,096 tracked files
and 144 MB become 462 files and 2.6 MB. The .gitignore is now an
allowlist, which is what keeps that true.

Root cause of the rot: ~/.local/bin was a symlink to scripts/ with GOPATH
inside it, so every go install wrote into version control (2.2 GB on the
work laptop). PATH now points at the repo instead of the reverse.

Also: Hyprland replaces sway and is sourced in two halves so $browser is
defined before use; singleton automations carry ConditionHost= alongside
host-layer-only placement; ddns moves from cron to a guarded timer;
package manifests and pkg-snapshot/pkg-restore replace the X11-era
install_scripts/; networkmanager-dmenu added to system76 (the binding
always existed, the package never did).
This commit is contained in:
connor committed 2026-09-14 14:24:37 -04:00
commit e6644d0616
462 files changed
+23524

No files matched your search

@@ -0,0 +1,36 @@
---
name: grafana-claude-code-blindspot
description: The llm-anthropic Grafana board only sees mainframe transcripts; work_laptop Claude Code usage is missing entirely
metadata:
type: project
---
`obs.claude_code_usage` is filled by `~/config/grafana/collect-claude-code.py`
(llm-claude-code.timer, every 15 min), which walks **mainframe's**
`~/.claude/projects` only. It has no remote source.
Connor also runs Claude Code on `work_laptop` (10.0.0.8, host `SCTFW004`, user
`connorjohnstone`) — reachable by `ssh work_laptop` with BatchMode keys.
**Why:** flat spots on the llm-anthropic board read as "the dashboard is
broken" but are real gaps in *mainframe* activity. Verified 2026-09-10: the DB
matched mainframe transcripts day-for-day exactly, while the laptop held 758
requests on 2026-09-04 (a day mainframe shows zero) plus 364 on 09-09 and 228
on 09-10 — roughly 40% of recent traffic invisible.
**Status as of 2026-09-10:** the *quota* half is solved — `obs.claude_quota`
plus panels 291-297 on llm-anthropic now show real account-wide 5h/weekly
utilisation, fed by `claude-quota-statusline.py` on both machines and harvested
by `llm-claude-quota.timer`. See robots.md §18 and [[claude-code-quota-source]].
**Also done (same day):** the token panels are multi-host too.
`obs.claude_code_usage` has a `host` column; `collect-claude-code.py` rsyncs
each host in `CLAUDE_HOSTS` into `~/.claude-mirror/<host>/` and walks it like a
local tree. 5,184 laptop rows backfilled to 2026-08-11. Panels 305 and 307 split
by machine. See robots.md §18.7.
**How to apply:** this blind spot is closed — don't re-diagnose it. The live
trap now is the opposite one: tokens (`claude_code_usage`) sum across hosts,
quota (`claude_quota`) is account-wide and must never be summed, and they sit on
the same board. Adding a machine is one entry in `CLAUDE_HOSTS` plus the
statusLine from [[claude-code-quota-source]].