docs: file three findings from the winvm and home handoffs

winvm's link-integrity pass found that protocols.org links references/calendar-reference.org, which the rsync never copies, so the link is dead in every consuming project. Filed [#B]. It also found an org-table violation in the retrospectives template and a pile of misplaced-heading lint noise in protocols.org from Markdown bold, both [#C].

home found that sentry.org calls one loop cycle a "fire", which reads as an emergency in the morning digest. Filed [#C] with "cycle" as the agreed replacement. home proposed "pass", but sentry.org already uses that as a numbered noun for the eleven hygiene passes, so "Pass 11" would have collided with a referent that already exists.

Each task records the severity and frequency behind its grade, so a wrong read can be argued with rather than just overridden.

1 files changed, 50 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 893ca6e..1dac9d7 100644
--- a/todo.org
+++ b/todo.org
@@ -39,6 +39,56 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 
 * Rulesets Open Work
 
+** TODO [#C] sentry.org calls one loop cycle a "fire" :chore:solo:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-07-28
+:END:
+Craig read home's "nine fires" as nine emergencies and went looking for what was burning (2026-07-28): "I assume you mean nine crises, not nine loop cycles and I begin to get scared." The term reaches him directly — digest headings render as =** Fire 11 — 08:32 CDT= in the anchor he reads every morning. 35 instances in =sentry.org=.
+
+Grading: Minor severity (a user-facing artifact that miscommunicates, no data loss) x most users frequently (every digest, on every project running sentry) = P3 = [#C].
+
+*Take the problem, not home's proposed term.* home proposed "pass", reasoning that it already lives in the file's vocabulary. That is exactly what disqualifies it. =sentry.org= already uses "pass" as a precise numbered noun: "the pass list", "the Pass Runner", "eleven finding/hygiene passes", "pass 12" for the implementation pass. There are exactly eleven hygiene passes, so home's proposed digest heading =** Pass 11= collides with an existing real referent. Renaming would trade a term Craig misreads as urgent for one that is genuinely ambiguous.
+
+Counter-proposal: *cycle*. It appears zero times in =sentry.org=, so there is nothing to collide with. It is also Craig's own word from the very quote that surfaced this ("not nine loop cycles"). =** Cycle 11 — 08:32 CDT= reads cleanly. Checked and rejected: "sweep" (already used for hygiene and property sweeps) and "run" (already used as a noun, "first live run").
+
+Keep the verb sense of fire throughout ("the notify fires", "the path never fires") — only the noun meaning one loop cycle changes. Past session anchors are historical records and stay as written.
+
+Craig approved "cycle" on 2026-07-28. That settles the only judgment the task carried, so it is =:solo:= now: the surface is the 35 noun-sense instances in =sentry.org=, and the completion check is objective — zero noun-sense "fire" left, verb sense untouched, lint clean, suite green, canonical and mirror in sync.
+
+Source: home handoff, 2026-07-28.
+
+** TODO [#B] references/ is linked from protocols.org but never synced :bug:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-07-28
+:END:
+=protocols.org:273= links to =references/calendar-reference.org=, but startup.org's rsync copies only =protocols.org=, =workflows/=, and =scripts/=. So the link is dead in every consuming project. Confirmed: the file exists at =claude-templates/.ai/references/=, and neither home nor =.emacs.d= has a =.ai/references/= at all.
+
+Grading: Minor severity (a documented reference an agent can't follow, workaround is to search or ask) x every user every time (every consuming project, every sync) = P2 = [#B].
+
+Two ways out: add =references/= to the rsync set, or drop the link and keep the file rulesets-only. My read is add it to the sync, because the link exists precisely so a session in another project can reach the calendar recipes.
+
+The =--delete= hazard I expected is not there. work is the only project with a =.ai/references/=, and its copy is byte-identical to the source (=diff -rq= clean), so nothing project-owned would be destroyed. Any *new* project-owned file under =references/= would be, which is the same tradeoff =workflows/= and =scripts/= already carry.
+
+Not =:solo:= — it changes a synced template, which needs Craig's approval by the inbox rule, and the sync-vs-drop choice is his.
+
+Source: winvm link-integrity pass, 2026-07-28.
+
+** TODO [#C] Two lint defects at the template source :chore:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-07-28
+:END:
+Both verified at the rulesets source, so every project seeded from them inherits the defect.
+
+=retrospectives/PRINCIPLES.org:38= violates the org-table standard (no closing rule). =lint-org= flags it as =org-table-standard=, and =wrap-org-table.el= reflows it mechanically. This half is purely tool-driven.
+
+=protocols.org= lints at 8 mechanical + 19 judgment =misplaced-heading= hits, all from Markdown =**bold**= in an org file, which org reads as a level-2 heading when it starts a line. 48 bold spans total, 14 of them line-initial. This half is not mechanical: converting to org =*bold*= is 48 edits, and =lint-org --fix= would rewrite the line-initial ones without knowing they are emphasis rather than headings.
+
+Grading: Cosmetic severity x every user every time = P3 = [#C]. It is most of the linter's noise on protocols.org, which is the real cost — noise that trains the reader to skip the report.
+
+Not =:solo:= — both files are synced templates.
+
+Source: winvm link-integrity pass, 2026-07-28.
+
 ** DOING [#B] Finish context-engineering rightsizing :refactor:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-07-27