mesh-issues: read merged from the pull request, not the state, so a closed one is withdrawn (hq issue 483)

mesh-delivery says stopped for a pull request closed unmerged too; read as
merged, it was said stuck to the operator for good. Cite ADR 0284 for the
worker rules, which the comments gave as 0283.

modules/mesh-issues/cmd/mesh-issues/issue.go

@@ -21,9 +21,9 @@ const (
 	IssueCounter = "issue"
 )
 
-// The six statuses of an issue, as the development cycle names them (hq playbook 03, ADR 0275, ADR 0283).
+// The six statuses of an issue, as the development cycle names them (hq playbook 03, ADR 0275, ADR 0284).
 // Fixing is the status an agent or person moves an issue to when they start its fix; resolved is reached
-// only from it (ADR 0283 §3).
+// only from it (ADR 0284 §5).
 const (
 	StatusOpen       = "open"
 	StatusDiagnosing = "diagnosing"
@@ -110,7 +110,7 @@ type Issue struct {
 	ReadyFor []uint64 `json:"ready-for,omitempty"`
 	// Triage is the triage's judgement as it was made, kept before it is applied.
 	Triage *Verdict `json:"triage,omitempty"`
-	// Worker is who works on it, while it is diagnosing or fixing (ADR 0283); nil at every other status.
+	// Worker is who works on it, while it is diagnosing or fixing (ADR 0284); nil at every other status.
 	Worker *Worker `json:"worker,omitempty"`
 	// Opening is the id of the call that opened it, so a write whose answer was lost is known as its own.
 	Opening string `json:"opening"`