ADR 0285: say in every condition's message which issue tracks it and where it stands (issue 400)

The operator could not tell from a notification whether its cause was
known, tracked and being fixed. An issue tracks a condition by its key;
the tracker answers which issues track which conditions, and the router
says it in every message about the condition. Amends to-be 53 and 45,
playbook 03 and the glossary, and points ADR 0253 at the new line.

00-META/process/03-issues.md

@@ -70,6 +70,11 @@ import read, which every imported issue names (`imported.commit` in `issue-track
    `replay:` or `replay-none:` in any report, because the tracker holds them and two places holding one fact
    drift.
 
+   **An issue about a condition** links the condition's key at once: `issue-tracker.link` with kind `condition` and
+   the key `mesh-controller.conditions` gives. Every message about that condition then names the issue and where it
+   stands; one no issue links says "No issue tracks this yet." An agent that silences a condition because an issue
+   tracks it links that issue first ([ADR 0285](../../02-DECISIONS/0285-an-issue-tracks-a-condition-by-its-key-and-every-message-about-the-condition-says-the-issue-and-where-it-stands.md)).
+
    **An issue wholly in the tracker** is done at this step.
 2. Investigate. **Before you start, move the issue to `diagnosing` with `by`**: who works on it and its node, as
    who@node (`fix-399@laptop`, `operator@workstation`). The tracker keeps you as the issue's **worker**, and `get` and `list`