Give the diagnostic events the address they have in this tree, not one on the tracker (#491)

src/artwork/format.rs

@@ -212,18 +212,25 @@ impl DeclaredDimensions {
 /// rather than four. 0055 says as much and says the fit is imperfect: a refused
 /// format is a shape the core recognised and declined on purpose, and the word in
 /// the kind says the opposite. What is here is which check refused, which is what
-/// a diagnostic event under #100 would carry and what a reader of a refusal
-/// wants. THIS SENTENCE SAID THE MAPPING ONTO THE KIND IS NOT MADE ANYWHERE:
-/// the point exists now and is [`crate::failure::Failure`], and no caller in
-/// this tree reaches it from here, because nothing in this tree fetches artwork
-/// and the transport that would is #27.
+/// a diagnostic event under [`crate::diagnostics`] would carry and what a reader
+/// of a refusal wants. THIS SENTENCE SAID THE MAPPING ONTO THE KIND IS NOT MADE
+/// ANYWHERE: the point exists now and is [`crate::failure::Failure`], and no
+/// caller in this tree reaches it from here, because nothing in this tree fetches
+/// artwork and the transport that would is #27.
 ///
 /// IT HANDED THAT ABSENCE TO #49 UNTIL THIS EDIT. #49 closed as completed on
 /// 2026-08-29, the day after the sentence landed, and what it produced is the
 /// address in [`crate::artwork::address`] rather than a fetch. The two other
 /// files of this directory already name #27 for the same absence. #485 is where
 /// it was found.
 ///
+/// IT ALSO GAVE THE DIAGNOSTIC EVENT AN ADDRESS ON THE TRACKER AND SAID #100.
+/// Nothing here emits one, so what such an event WOULD carry is still the mood to
+/// write it in, and where the events live is [`crate::diagnostics`]. #100 closed
+/// as completed on 2026-08-26, the module landed the same evening, and this
+/// sentence landed two days after both, so that half landed refuted rather than
+/// going stale. #491 is where it was found.
+///
 /// A refusal is not the absent answer in #51. One says the server sent something
 /// wrong and the other says the server has no image, and a client that cannot
 /// tell them apart shows a failure sentence over a library that is fine.

src/cache/freshness.rs

@@ -281,9 +281,16 @@ impl WrittenAt {
 ///
 /// Two reasons rather than one because 0102 names two devices, and they are not
 /// the same device: one that came up believing it is 1970, and one that jumped
-/// forward. Collapsed, a diagnostic under #100 could report that a clock is
-/// wrong and never which way, which is the half that says whether anything can
-/// be done about it.
+/// forward. Collapsed, a diagnostic under [`crate::diagnostics`] could report
+/// that a clock is wrong and never which way, which is the half that says
+/// whether anything can be done about it.
+///
+/// THE CONDITIONAL IS RIGHT AND THE ADDRESS WAS NOT: THIS SENTENCE SAID #100.
+/// Nothing in this module emits an event, so what such a diagnostic COULD report
+/// is still the mood to write it in. Where it points is the part that moved:
+/// #100 closed as completed on 2026-08-26, the module carrying the interface
+/// landed the same evening, and this sentence landed two days after both, so it
+/// landed refuted rather than going stale. #491 is where it was found.
 ///
 /// This is not the reason field 0043 refuses. That refusal is about which
 /// THRESHOLD a stale entry passed, on the grounds that a threshold is the core's

src/failure/mod.rs

@@ -108,8 +108,16 @@ pub struct Constructed(());
 /// Which of the fifteen a failure is, without its payload.
 ///
 /// It exists so that a failure can be counted and grouped - which is 0004's own
-/// reversal condition, read off the diagnostic events in #100 - without every
-/// counting site matching fifteen variants and reaching into their fields.
+/// reversal condition, read off the diagnostic events [`crate::diagnostics`]
+/// carries - without every counting site matching fifteen variants and reaching
+/// into their fields.
+///
+/// THIS SENTENCE GAVE THOSE EVENTS AN ADDRESS ON THE TRACKER AND SAID THEY WERE
+/// IN #100. That issue closed as completed on 2026-08-26, the module carrying the
+/// interface landed the same evening, and this sentence landed two days after
+/// both. So it landed refuted rather than going stale, which is the harder of the
+/// two states to defend, and is worth saying in those words. #491 is where it was
+/// found.
 ///
 /// Thread safety, from 0009: a plain value, safe from any thread.
 #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, PartialOrd, Ord)]