Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2601

majordomus evidence reaches record, stamp and show

Where it stands

devtask.issue
Readiness
review implementation is declared finished and completion is not recorded
Status
VERIFY
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
0
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
1 of 1
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2601

majordomus plan verify I2601

majordomus plan done I2601

What it is

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.
Now
bin/majordomus:162 routes `evidence` to lib/evidence.sh, which parses options only and dies on the word `record`.
Wanted
The shell command hands the subcommands the executable owns to it, keeps --covers and --gate, and its help lists both.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • `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 validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>
Evidence required
evidence_subcommands_through_launcher_case
Evidence present
evidence_subcommands_through_launcher_case

Scope

Touches
lib/evidence.shbin/majordomusshare/commands.yamldocs/EVIDENCE.mddocs/CLI.mdtest/cases
Not
unknown: the record declares no `non_scope`
Depends on
none
Priority
p1
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-13
Updated
2026-10-13T17:54:58Z
Started
2026-10-13T11:36:41Z
Verified
2026-10-13T17:54:58Z
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.