mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

mesh-issues keeps each design's milestone in the state milestones (history 5), says milestone-set and
milestone-moved, and serves milestones, milestone-set and milestone-move. An issue's milestone is its own link
of kind milestone, so at most one milestone per issue is checked inside the issue's own write; kind commit
links a fixing commit. The triage links no milestone, pull request or commit. import with milestones=N seeds
a design's table once. mesh-knowledge's progress reads issue-tracker.milestones and its table parse is gone.

Squashed from four commits so the branch history does not carry a compiled bundle that was committed by
mistake (6 MB); the path is now in .gitignore.

modules/mesh-issues/README.md

@@ -22,8 +22,11 @@ what it refuses.
 | `list` | optionally `status`, `owner`, `phrase`, `limit`, `severity`, `needs`, `ready`, `flag` (`delivered-not-resolved` or `abandoned`), `search` (words, ranked), `before` (a number, the cursor), `numbers` (only these issues, in the order given, naming any not an issue in `missing`), `worker` (only that worker's held issues), `linked` (only the issues with that link, as `kind:target`, such as `decision:0493`) | short rows, newest first, or best first for a `search`, or in the order given for `numbers`: number, status, owner, title, `moved` (when the issue last changed: opened, moved, noted, linked, worked on, or its fix's delivery said a new state), and each flag that holds; `next`, the `before` that reads on, when more match |
 | `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 |
-| `import` | optionally `dry-run`, `commit` | hq's issue folders, read through the records module, each written as an issue under its own number; see below |
+| `link` | `number`, `kind`, `target`, optionally `remove` | adds or removes a typed link; kind `milestone` (design/id, such as 47/R6) at most once per issue and only to an open milestone, kind `commit` as repository@full sha (ADR 0493 §2 to §4) |
+| `milestones` | optionally `design`, `status`, or `one` (design/id) | the milestones, in their design's table order, each with its issues and how many are done; one with its history |
+| `milestone-set` | `design`, `id`, and `outcome` to make one; optionally `order`, `announce` | makes a milestone (state `milestones`, event `milestone-set`), changes its outcome or order, or says it again |
+| `milestone-move` | `milestone`, `status` (`open` or `closed`), `reason` | opens or closes it (event `milestone-moved`); closing is refused while a linked issue is neither resolved nor wontfix |
+| `import` | optionally `dry-run`, `commit`; or `milestones` (a design's number) | hq's issue folders, read through the records module, each written as an issue under its own number; see below. With `milestones`, seeds that design's milestone records from its table once (issue 1781): an issue two rows name, or that another milestone holds, is refused and named; a milestone whose issues are all done is closed; run again, it changes nothing |
 | `set` | `number`, any of `severity`, `needs`, `suggested-owner` | changes them as a person decides |
 | `groom` | optionally `pass`, `confirm` | the triage over the backlog: without arguments a dry run in the background, answering its pass id; with `pass` its progress and findings; with `confirm` and `pass` exactly that pass's findings applied, each checked again; see below |
 | `tracking` | optionally `conditions` (condition keys) | for every condition key an issue links (link kind `condition`), the issues that link it, those not closed first: status, severity, needs, worker with since, active and stale, and where the fix is (`fix`); the operator's channel says it in a condition's message (hq ADR 0285) |