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
I0818
The command registry is read in one pass
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Replace the per-index, per-field awk lookups in mj_cmdreg_public, mj_cmdreg_ids and the event registry with one awk pass each, and read them once per process.
- Why
- Command coverage costs three seconds because mj_cmdreg_public runs dozens of awk processes and is called inside a loop over declared commands.
- Now
- mj_cmdreg is one awk per key; mj_cmdreg_public loops it; mj_validate_command_coverage calls mj_cmdreg_public per declared command.
- Wanted
- Each registry is flattened once and its public ids and dispatch table are derived with one awk; the coverage validator reads every case header with one pass.
- Done when
- unknown: the record declares no `completion`
- Risk
- A batch read must produce exactly the per-key results; the cases that mutate the registry are the proof.
Acceptance
- validate:command_coverage and validate:command_surface each under 200 ms on this repository
- Cases 30, 31, 35 and 36 pass unchanged
- yaml_flatten count for doctor does not grow
- Validation
MJ_TIMING=1 bin/majordomus doctorbash test/run.sh 31_command_coverage- Evidence required
batch_reads- Evidence present
batch_reads
Scope
- Touches
lib/commands.shlib/common.shtest/cases/30_command_registry.shtest/cases/31_command_coverage.sh- Not
A change to share/commands.yaml- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-05
- Updated
- 2026-09-05
- Started
- 2026-09-05T01:50:00Z
- Verified
- 2026-09-05T02:05:00Z
- Completed
- 2026-09-05T02:05:00Z
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.