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

I1115

Completion comes from the command model, not from a second list

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
7
Waiting on
I1114
Holds back
I1123
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI1114I1114 is not DONE

Moves

plan.transition
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 I1115

majordomus plan verify I1115

majordomus plan done I1115

What it is

Objective
Derive shell completion from the same command model the CLI and its documentation already come from, so that a new command is completable without anything being listed.
Why
A completion script is the least visible copy of a command list and therefore the one that drifts furthest. It is also the one people notice, because a missing completion reads as a missing feature.
Now
The CLI is declared once and its reference is generated. Completion, where it exists, is not derived from that declaration.
Wanted
Completion is generated from the command model, refreshed as safe cached state, and never enumerated by hand.
Done when
unknown: the record declares no `completion`
Risk
Completion is where a fast path tempts a shortcut list. Deriving it is cheap only if the model is already cached; otherwise the budget decides.

Acceptance

  • Completion data is derived from the command model with no second enumeration
  • A command added to the model is completable after the ordinary generation, with no further edit
  • The refresh is cached state under the control-plane namespace and never a tracked-file mutation
  • Whatever the entry path does for completion stays inside the entry budget
Validation
majordomus generate --checkbash test/run.sh
Evidence required
completion_derived
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/cli.rs.majordomus/generated
Not
A completion script maintained by handRegenerating completion on the environment-entry path if it costs more than the budget allows
Depends on
I1114
Priority
p2
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-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
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.