Configure the engineering skills against this repo and this KB

The Matt Pocock engineering skills (triage, to-tickets, to-spec, research,
implement) assume per-repo config for three things: where work items live, what
the triage label vocabulary is, and where domain docs sit. Nothing here declared
any of them, so every skill run re-guessed.

Frank's decisions, 2026-10-20: Gitea on Dankclaw as the tracker (no gh, no tea on
any box, so it is recorded as prose — auth via a 600 curl config, the endpoint
table, the 404-on-empty-token / form-encoded-merge / empty-200-on-merge traps,
and the AGENTS.md laws a skill must not renegotiate); the canonical triage label
vocabulary kept as-is, with the five labels created on the tracker (the repo had
zero, so nothing collides); single-context domain docs.

The configuration moved out of the skill's default docs/agents/ and into the one
knowledge base this repo allows: three pages under omp-docs/skills/, an empty
omp-docs/decisions/ carrying the ADR format rule, an "## Agent skills" pointer
block in AGENTS.md, index entries, and a log entry. The glossary is deliberately
not created — every candidate term already has an owner in system/, core/ or
skills/, and a term list that paraphrases them is a second owner of facts already
written down. Known cost: re-running setup-matt-pocock-skills will not recognise
omp-docs/skills/* and will offer to recreate docs/agents/; the AGENTS.md pointer
is what stops that.

Also closes a verification gap found on the way: kb-lint.bats only ever points
the linter at fixtures, so a page with no frontmatter or an index that stops
listing a file passes the suite silently. Two tests now run the linter and the
coverage checker against the shipped omp-docs/ tree.

Refs #18

omp-docs/decisions/index.md

@@ -0,0 +1,26 @@
+# Architecture decision records
+
+Decisions this repo has made and will not silently revisit. One file per
+decision, named `NNN-<slug>.md`, listed here — an unlisted page fails `kb-lint`
+and does not exist as far as any agent is concerned.
+
+**No ADRs yet.** The first one lands the moment a decision stops being
+reversible.
+
+## Format
+
+Same shape as the `dank/dankvoice` decision records, which read well under time
+pressure:
+
+- `# <Decision as a claim> (YYYY-MM-DD)` — a title you can disagree with.
+- **Root** — the situation and the evidence that forced the question, with measured
+  output rather than recollection where measurement exists.
+- **Decision** — what was chosen, and the rule an agent must follow because of it.
+- **Rejected** — the alternatives and the specific reason each was turned down, so
+  nobody spends an afternoon rediscovering them.
+- **Verification** — what was run to prove the decision holds, and where that
+  proof lives.
+
+Frontmatter is required like any other page in this bundle (`type: decision`), and
+an ADR that a code change has superseded gets an amendment section appended rather
+than a rewrite: the point of the record is that the reasoning is still readable.