I2601 — majordomus evidence reaches record, stamp and show

✓DONE wave 0 · p1 · implementation profile · parallel safe

Part of a-second-adopter-is-served — A second adopter is served: what a foreign repository met on its first day is fixed in the tool.

Objective

Make the documented `majordomus evidence record|stamp|show` work from the launcher.

Why

Observed on 2026-10-13 adopting 0.21.0 and 0.22.0 in a pnpm/TypeScript repository (docs/ADOPTION_SECOND_RUN.md, G17); read again on master e506c041a4. docs/EVIDENCE.md documents `majordomus evidence record --suite …`; the installed launcher answers `evidence: unknown option record`, and the executable that does it is not on PATH.

Current state

bin/majordomus:162 routes `evidence` to lib/evidence.sh, which parses options only and dies on the word `record`.

Desired state

The shell command hands the subcommands the executable owns to it, keeps --covers and --gate, and its help lists both.

Scope

• lib/evidence.sh
• bin/majordomus
• share/commands.yaml
• docs/EVIDENCE.md
• docs/CLI.md
• test/cases

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• `majordomus evidence show`, `record --help` and `stamp --help` answer through the launcher
• `majordomus evidence --covers` behaves as before
• The documented-command check runs the EVIDENCE.md lines it names

Validation

• bin/majordomus plan validate
• MJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>

Evidence required

• evidence_subcommands_through_launcher_case

Evidence

Timeline

started

2026-10-13T11:36:41Z

verified

2026-10-13T17:54:58Z

completed

2026-10-17T21:35:40Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I2601.yaml. Read it back with majordomus plan show I2601.