mesh-issues: call an issue its worker left abandoned, not a stale claim (hq ADR 0294)
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered

The glossary keeps claim for a module's on a seat.
This commit is contained in:
2026-10-11 12:26:57 +02:00
parent 3aaccba4e2
commit d6148a5ba7
8 changed files with 54 additions and 54 deletions
+5 -5
View File
@@ -19,7 +19,7 @@ what it refuses.
|---|---|---|
| `open` | `title`, `report`, optionally `located-in`, `record` | checks the issue, then takes the next number and keeps it under that number; answers the number |
| `get` | `number` | the issue whole: fields, notes, links |
| `list` | optionally `status`, `owner`, `phrase`, `limit`, `severity`, `needs`, `ready`, `flag` (`delivered-not-resolved` or `stale-claim`) | short rows, newest first: number, status, owner, title, and each flag that holds |
| `list` | optionally `status`, `owner`, `phrase`, `limit`, `severity`, `needs`, `ready`, `flag` (`delivered-not-resolved` or `abandoned`) | short rows, newest first: number, status, owner, title, and each flag that holds |
| `move` | `number`, `status`, and what that status needs (`by` for `diagnosing` and `fixing`, optionally `take-over`) | changes the status under the development cycle's rules |
| `note` | `number`, `text` | appends a note; a note is never edited |
| `link` | `number`, `kind`, `target`, optionally `remove` | adds or removes a typed link |
@@ -128,11 +128,11 @@ delivery, the sweep says it once as a warning on the operator's channel, key
`issue-tracker.delivered-not-resolved.<number>`, "issue N: fixed and delivered, not resolved; <worker> works on it",
cleared there when the issue leaves fixing or names a fix not delivered yet (at its `moved`, or the next sweep).
**A stale claim** (hq issue 483). An issue in diagnosing or fixing whose worker did nothing on it for
**Abandoned** (hq issue 483). An issue in diagnosing or fixing whose worker did nothing on it for
`worker-stale-after` (default `24h`) and that names no pull request still open (not merged, or never heard of)
carries `stale-claim` on `get` and its `list` row, beside its `worker`. A move by someone else takes it over without
`take-over`'s reason, as any stale worker; the answer, the note and the `moved` event say the claim was stale
(`stale-claim`).
carries `abandoned` on `get` and its `list` row, beside its `worker`. A move by someone else takes it over without
`take-over`'s reason, as any stale worker; the answer, the note and the `moved` event say it was abandoned
(`abandoned`).
Every five minutes the module looks for a fix merged and not delivered after `stuck-after` (default `2h`): it is
said once — a note on the issue and a warning on the operator's channel (`seat:operator-channel.notify`, key