Hold an insight to the deferrals it speaks about, and name what ADR 0273 left undecided

A review found the check too lenient: an issue cited as context beside a deferral passed it, and one
insight excused every deferral in a record. The tracking issue is now named as tracking it, an insight
covers only its section or what it quotes, and the phrases include "not decided here", "postponed" and
"future work". ADR 0273's four undecided items get issue 357.

02-DECISIONS/0244-the-mesh-is-described-in-domains-and-one-word-names-one-thing.md

@@ -182,9 +182,11 @@ work:
   descriptions call a build request an *ask*;
 - the nftables module's tool `firewall_rules`, which serves the packet filter.
 
-> **Progressive insight — 2026-10-09.** This section deferred the code renames and named no issue, owner or
-> date for them; two days later the operator believed them done, and nothing in this record said otherwise.
-> They are tracked by
+> **Progressive insight — 2026-10-09.** This record deferred the code renames in four places and named no
+> issue, owner or date for them: this section, §2 ("listed in §6 for a later rename and is not renamed here"),
+> §3 ("Code that still carries an old name is named on an *Identifier until renamed* line") and §4's table
+> ("`mesh-host` an identifier until the code rename"). Two days later the operator believed them done, and
+> nothing in this record said otherwise. They are tracked by
 > [issue 354](../04-ISSUES/354-a-decided-rename-was-never-scheduled-and-the-operator-believed-it-live/00-report.md),
 > which holds the inventory of what carries the old names, the risk of renaming the paths of a self-updating
 > daemon on live nodes, and the staged plan; each stage is owned by the repository it names, and the

02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md

@@ -377,6 +377,12 @@ Recording a proposal needs no yes: it writes the register and nothing a session
   for an agent the mesh runs rather than the operator's; and a channel of the operator's own that can
   tell the operator from an agent (issue 340's "once we build a UI"), which would become a third route.
 
+> **Progressive insight — 2026-10-09.** The four things this section leaves undecided — clearing old copies
+> of hand versions, a per-project lesson, lessons for an agent the mesh runs, and a channel of the operator's
+> own — were left with no issue, owner or date, which is how ADR 0244's deferred renames went unnoticed
+> (issue 354). They are tracked by
+> [issue 357](../04-ISSUES/357-what-adr-0273-left-undecided-has-no-owner/00-report.md). The decision stands.
+
 ## How it is checked
 
 | Rule | Checked by |