diff options
| author | Craig Jennings <c@cjennings.net> | 2026-09-25 13:05:32 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-09-25 13:05:32 -0400 |
| commit | adab9abae11792eaa17711a63a74efa68885a0be (patch) | |
| tree | 06f158b9c9d6e7f6673418685dbeb4d77b892257 /dotfiles/system/.config/sublime-merge/Local/License.sublime_license | |
| parent | 59760335a1fe7ec692a2a613d6565507de8f9502 (diff) | |
| download | archsetup-adab9abae11792eaa17711a63a74efa68885a0be.tar.gz archsetup-adab9abae11792eaa17711a63a74efa68885a0be.zip | |
chore(tasks): clear passed dates and grade the new bugs
The board drifted over four interrupted sessions. Nine tasks carried dates that had already passed, so the agenda showed them as overdue rather than as work with a week attached.
I re-dated or demoted all nine. I closed the pre-vacation list whose departure has passed and recorded where each of its seven items went, then ran a seven-task review batch alongside it.
I filed nine new tasks. Four are bugs, and each carries its severity times frequency arithmetic in the body so the letter can be argued with by fixing an input rather than overridden:
- velox's USB hub tearing down and rebuilding under the Jabra, near-daily, which takes the call audio with it
- the xhci controller refusing D3hot thousands of times per boot, every boot
- the installer never setting Storage=persistent, so a fresh machine keeps no journal across a reboot
- four closed tasks still pinned to the agenda by a planning line they kept
That last one is the shape worth naming. Closing a task stamps CLOSED: and leaves any SCHEDULED: it already had. My agenda doesn't skip scheduled-if-done, so a finished task renders as overdue forever. The rule strips the planning line from a dated sub-task entry and says nothing about a top-level one, which is how five of these accumulated. One was in this diff and is fixed here. The other four predate it and have their own task.
I also re-graded the telega coredump tell down to [#D]. That moves an input rather than overruling the earlier raise. The raise was correct while the assertion fired across five days. The tell has been quiet on both machines for three weeks, so the frequency row moved and the letter followed it. If it reappears, both move back.
I ticked git-lfs, imv and libreoffice-fresh in the undeclared-packages checklist. The installer now declares all three, so a later walk should skip them.
Diffstat (limited to 'dotfiles/system/.config/sublime-merge/Local/License.sublime_license')
0 files changed, 0 insertions, 0 deletions
