aboutsummaryrefslogtreecommitdiff
path: root/dotfiles/system/.config
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-08-04 00:22:34 -0500
committerCraig Jennings <c@cjennings.net>2026-08-04 00:22:34 -0500
commitfc3a8508561114177a67bbdb6802bdcf1df7683e (patch)
tree2c42e2c16b7b56e9f67dd07e1479ae48c2b82aad /dotfiles/system/.config
parent1e81319c7a41623a8e361ef3cc3898b9a023530b (diff)
downloadarchsetup-fc3a8508561114177a67bbdb6802bdcf1df7683e.tar.gz
archsetup-fc3a8508561114177a67bbdb6802bdcf1df7683e.zip
chore(todo): close a fixed lock-chain bug, re-scope the world face, file twoHEADmain
The idle-commit lock-chain bug was fixed on 2026-07-29 and stayed open at [#A] six days past deadline. Verified against the tree rather than the commit message: the wrapper is in the rendered chain, the live config matches, and the test that used to pin the bug now pins the fix. The evidence the task itself named is that the relaunch log is receiving entries, so the instrument is present rather than silently removed. Recorded a finding that changes the night-watch task's premise. Two relaunches on 2026-07-30 postdate the mitigation, and the watchdog logs the exit code but not the sender, so "the night watch is the only thing killing hyprlock" is now unproven. Instrument before designing the handshake. The world face lost half its premise when the 07-31 rebuild dropped the layout flag, so it re-scopes to the hour-format toggle alone and drops to [#C]. Filed the decaying spine tests and answered the drift audit's open delivery question, which is what let it take :solo:.
Diffstat (limited to 'dotfiles/system/.config')
0 files changed, 0 insertions, 0 deletions