aboutsummaryrefslogtreecommitdiff
path: root/.ai/scripts
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-28 19:53:45 -0500
committerCraig Jennings <c@cjennings.net>2026-07-28 19:53:45 -0500
commitf3f5bfd651962934b230785d5a3449b738ce44ed (patch)
treeafc906ed12ab286e4fef914b89a4fc4f21796ae0 /.ai/scripts
parentca508a1fbc1e71af07fd77281b3fd67cd6486e22 (diff)
downloadrulesets-f3f5bfd651962934b230785d5a3449b738ce44ed.tar.gz
rulesets-f3f5bfd651962934b230785d5a3449b738ce44ed.zip
refactor(sentry): call one loop cycle a cycle, not a fire
I read "nine fires" as nine emergencies and went looking for what was burning. The word reaches me directly, since digest headings render as Fire 11 in the anchor I read every morning. 72 noun-sense instances in sentry.org become "cycle". The four verb-sense uses stay, because firing is the right word for a trigger. home proposed "pass" and I turned it down. sentry.org already uses that as a numbered noun for the eleven hygiene passes, so "Pass 11" would have collided with a referent in the same file. home confirmed it by walking into exactly that: its anchor ended up carrying "Pass 11" three lines from "pass 12". "Cycle" appears nowhere in the file, and it is the word I reached for myself when I flagged the problem. Three more instances lived outside sentry.org: wrap-it-up.org, todo-cleanup.el, and its test. All three named a sentry cycle, so they move too and the vocabulary stays consistent across files.
Diffstat (limited to '.ai/scripts')
-rw-r--r--.ai/scripts/tests/test-todo-cleanup.el2
-rw-r--r--.ai/scripts/todo-cleanup.el2
2 files changed, 2 insertions, 2 deletions
diff --git a/.ai/scripts/tests/test-todo-cleanup.el b/.ai/scripts/tests/test-todo-cleanup.el
index a92d238..1e964b3 100644
--- a/.ai/scripts/tests/test-todo-cleanup.el
+++ b/.ai/scripts/tests/test-todo-cleanup.el
@@ -1086,7 +1086,7 @@ line) is left untouched — the strip stops at the first non-planning line."
;;
;; todo-cleanup rewrites todo.org in place and left no copy behind, while both
;; sibling org-mutators back up to /tmp first. It is also the one that runs most
-;; often (every wrap, every sentry fire). Emacs's own backup does not fire under
+;; often (every wrap, every sentry cycle). Emacs's own backup does not fire under
;; --batch -q, so there was genuinely no undo short of git.
(ert-deftest tc-backup-written-before-a-real-mutation ()
diff --git a/.ai/scripts/todo-cleanup.el b/.ai/scripts/todo-cleanup.el
index cb333e2..516e9b1 100644
--- a/.ai/scripts/todo-cleanup.el
+++ b/.ai/scripts/todo-cleanup.el
@@ -843,7 +843,7 @@ event-log entry, pulling the timestamp from its CLOSED cookie. Honors
Matches `lint-org.el' and `wrap-org-table.el', the other tools that rewrite
these org files. todo-cleanup runs the most often of the three (every wrap,
-every sentry fire), and Emacs's own backup does not fire under --batch -q, so
+every sentry cycle), and Emacs's own backup does not fire under --batch -q, so
without this a mechanical rewrite has no undo short of git — which recovers
only to the last commit and loses intra-session work."
(let* ((base (format "%s%s.before-todo-cleanup.%s"