Remove the decision records and research efforts, which the knowledge base now holds whole (issue 426)

ADR 0290 rule 9: once the import is checked record by record, hq keeps no copy.
The records and efforts are removed; every link or path to them reads "ADR NNNN" or
"research NNN"; a design's decisions: lists "ADR NNNN". 02-DECISIONS keeps a pointer
README with the reading order's six topics, which the knowledge base reads through the
records module; 01-RESEARCH keeps a pointer README. The checks drop the rules that
judged records (the knowledge base holds each at propose; checks/README.md says where)
and refuse a record written here again. Playbooks 01 and 02 and the skills write and
read records with the knowledge base's verbs.

00-META/process/03-issues.md

@@ -22,7 +22,7 @@ incident someone must **clear**.
 ## The issue tracker holds the number and the status
 
 Every issue is opened in the **issue tracker**, the module `mesh-issues` holding the seat `issue-tracker` on the
-control-node ([ADR 0275](../../02-DECISIONS/0275-the-mesh-numbers-and-tracks-its-issues-in-a-module-of-its-own-and-hq-keeps-only-the-narrative-of-a-design-or-governance-issue.md),
+control-node (ADR 0275,
 [to-be 53](../../03-DESIGN/01-to-be/53-the-issue-tracker.md)). Its number comes from one counter advanced by
 compare-and-set, so two authors opening at the same moment never get the same one. **A number is never taken by
 reading `main` or the open pull requests** — that is how numbers collided (issue 155: two records sharing a number
@@ -73,7 +73,7 @@ import read, which every imported issue names (`imported.commit` in `issue-track
    **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)).
+   tracks it links that issue first (ADR 0285).
 
    **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
@@ -87,14 +87,14 @@ import read, which every imported issue names (`imported.commit` in `issue-track
    `take-over` saying why, which is noted on the issue. A stale worker may be taken over from without a reason.
    Name the fix in `fixed-by` when it merges, with a move to `fixing` that gives `by` again; the issue stays
    `fixing` until the acceptance is proven live
-   ([ADR 0284](../../02-DECISIONS/0284-an-agent-moves-an-issue-to-fixing-under-its-own-name-and-an-issue-is-resolved-only-from-fixing.md),
-   [ADR 0281](../../02-DECISIONS/0281-an-issue-knows-whether-its-fix-is-delivered-and-a-fix-stuck-after-its-merge-is-loud.md)).
+   (ADR 0284,
+   ADR 0281).
 4. Resolve. `issue-tracker.move` to `resolved`, which the tracker takes only from `fixing`, with `fixed-by`, and, if the root cause was a design gap,
    run playbook [02](02-graduation.md) and give `amended-design`. **A core issue** — its `located-in`
    names the controller, the node-engine, the tool runner, the SDK, or the catalogue's bus, forge or build
    agent — resolves with `replay`, the id of its replay in mesh-lab's replays register, proved to fail on
    the commit before the fix and pass on it, or with `replay-none` saying why none is possible
-   ([ADR 0237](../../02-DECISIONS/0237-a-change-is-judged-against-the-mesh-that-runs-before-it-merges-on-the-build-seat.md));
+   (ADR 0237);
    `issue-tracker.move` refuses the move without it. `wontfix` needs a `reason`.
 
 ## Rules